Delivery
Only 18% measure flow. The rest still steer delivery with project and velocity proxies.
Digital.ai's 17th State of Agile report finds that flow metrics remain rare: most organisations still steer delivery with individual project metrics or velocity, neither of which shows where work waits.
Mid-market bridge: Already size-relevant: the same report shows medium organisations are less satisfied with enterprise Agile than small ones. See the medium-organisation scale-barriers signal for that separate size split.
Outcome we help: Stop vanity activity metrics; install flow visibility.
What the report found
18%
of organisations measure flow metrics
17th State of Agile press release and report
39%
still rely on individual project metrics
17th State of Agile press release and report
36%
still rely on velocity as a primary measure
17th State of Agile press release and report
What it means for leaders
- Velocity and project proxies hide where work waits; flow measures show it.
- A local p85 cycle time is more useful to a team than any industry benchmark.
What to do on Monday
Start here: Count the WIP on one board; cap new starts at WIP minus one; record start and finish dates for the next five done items and read the median cycle time by Friday.
- Ask which measure the team is currently managed to, and whether it shows waiting work.
Try it in an open workspace
Free tools with sample data. No account.
Source
17th State of Agile Report, Digital.ai, 2024. Read the original report