Learn & Understand

When Velocity Becomes a Target, It Stops Being a Measure

The velocity calculator averages story points across recent sprints and turns a backlog into a forecast. Used that way, as a quiet planning tool, it is genuinely useful. But velocity is also one of the most abused numbers in software project management, because the moment a manager starts treating it as a performance target, it quietly corrupts. The reason is a principle sharp enough to deserve its own name: Goodhart's law.

Goodhart's Law

Goodhart's law states, in its popular form, that when a measure becomes a target, it ceases to be a good measure. A metric works as an honest signal only as long as no one is being rewarded or punished for the number itself. Start pressuring a team to raise its velocity, and the team will oblige, but not necessarily by doing more work. They will do the one thing that reliably moves the number: estimate the same work as more points.

Why Story Points Are So Easy to Inflate

Story points are deliberately abstract, a relative measure of effort and complexity, not hours. That abstraction is a strength for planning, because it sidesteps the false precision of time estimates, but it is a fatal weakness once points become a target. There is no external anchor. If a team decides that yesterday's three-point story is today's five-point story, velocity rises with no extra output whatsoever. The currency inflates, and the forecast built on it silently loses meaning.

Velocity Is Not Comparable Between Teams

A related error is comparing velocities across teams, as if a team scoring forty points is twice as productive as one scoring twenty. Because each team calibrates its own point scale independently, the numbers are in different currencies. Cross-team velocity comparison is not just unfair; it is meaningless, and it invites exactly the inflation Goodhart warns of, as teams learn to score generously to look good. Velocity is a private ruler, useful only for measuring one team against its own past.

Protecting the Signal

The way to keep velocity honest is to keep it boring: a team's own planning input, used to answer "how much can we realistically commit to next sprint" and "roughly how many sprints until the backlog clears." Feeding those figures into the calculator gives a defensible forecast precisely because no one is gaming the inputs. The instant the number appears on a leaderboard, treat every forecast built on it with suspicion.

To turn a trustworthy velocity into a projected date, use the Release Date Forecast Calculator; to check the team actually has the hours behind that velocity, see the Team Capacity Calculator.