Velocity Is a Planning Tool, Not a Performance Metric
Velocity was designed to answer one question: given what this team has delivered in recent sprints, how much should we expect it to deliver in the next one? It is a forecasting input, calibrated to a specific team’s specific definition of a story point. It is not a measure of productivity, engineering quality, team health, or business value delivered. Using it as any of those things produces outcomes that are reliably bad.
The most common misuse is comparison. Management compares velocity across teams. Teams compare their velocity to their own historical peaks. Both comparisons are meaningless because story points are not a universal unit. Team A’s five-point story and Team B’s five-point story share only a number. The underlying work, context, and complexity may have nothing in common. A team with a velocity of sixty is not more productive than a team with a velocity of thirty. They have made different calibration decisions.
The second misuse is target-setting. When velocity becomes a goal rather than a measurement, teams optimize for the metric rather than the outcome. Stories get inflated. Done gets defined down. The sprint looks successful on paper while the actual increment deteriorates. This is not a cynical act by a dysfunctional team — it is the predictable response of any system to being evaluated on a proxy metric that can be gamed.
The correct use of velocity is as a trailing average that informs sprint capacity decisions. Three to five sprints of data, averaged, gives a reasonable basis for how much to pull into the next sprint. When velocity drops, the right question is whether something has changed in the team’s circumstances — complexity, interruptions, process overhead — not whether the team is working hard enough. When velocity increases, the right question is whether the quality and scope of work is being maintained, not whether the team can be pushed further.
Velocity tells you one thing well: whether a team’s output is stable and predictable. Stability is valuable. It is not the same as performance, and treating it as such is one of the more reliable ways to destroy a functioning team.