Which delivery metrics would you actually track for a team, and why does velocity stop working the moment you set a target for it?
Answer
Short answer
Track throughput, cycle-time distribution and flow efficiency, because they describe the system rather than the estimate. Velocity is denominated in a unit the team defines, so making it a target lets the number rise without any change in delivered output, and it stops measuring anything.
Flow metrics are valuable because they describe work moving through a system rather than people being busy. Good flow metrics answer where work waits, how much is ageing, and whether completed work is becoming more predictable. Weak flow metrics become a scorecard; strong flow metrics start a conversation about the constraint the team can change.
Was this answer helpful?
Likely follow-ups
- Two teams report velocities of 20 and 55. What can you conclude?
- Your cycle-time median is 4 days and your 85th percentile is 26. What is going on?
- A director wants team-by-team velocity on a quarterly dashboard. What do you say?
- How would you forecast a fixed-scope regulatory deadline eleven weeks away?
Related questions
- There are forty items left before the release and over the last twelve weeks the team has finished between four and nine a week. The sponsor wants a date. What do you tell them?hardAlso on forecasting and throughput6 min
- Why do we estimate in story points at all, and what would you do if the team's estimates were consistently wrong?mediumAlso on velocity and forecasting7 min
- Why does a random train-test split ruin a forecasting model?mediumAlso on forecasting5 min
- Leadership has asked for 20 per cent growth in activations next quarter. How do you decide whether that is the right target?hardAlso on forecasting5 min