Why Scrum Velocity Is Not a Performance Metric: The "Goodhart's Law" Trap

The Most Dangerous Metric in Agile

Is your manager obsessed with "speed"?

If your leadership team is asking how to increase velocity, they are asking the wrong question.

This deep dive is part of our extensive guide on Agile Metrics and Forecasting Guide: Beyond Velocity to Real Value.

The fundamental misunderstanding in most organizations is treating Story Points like hours and Velocity like speed.

You need to understand why scrum velocity is not a performance metric before it destroys your team's culture.

When you treat a planning tool as a performance target, you trigger "Goodhart's Law":

"When a measure becomes a target, it ceases to be a good measure."

Why Velocity is Volatile (And Why That’s Okay)

Most organizations are drowning in data but starving for insight.

They track "Velocity" obsessively, believing that if the number goes up, the team is doing better.

But Velocity is volatile. It depends on:

• Team composition changes.
• Vacations and holidays.
• Estimation bias.
• Even the mood of the room during Sprint Planning.

Because it is a relative measure unique to the specific team at that specific moment, it was never designed to be a static KPI.

The "Gaming" of the System

When management weaponizes this metric, teams learn to game the system.

If you tell a developer that their performance review depends on completing 20 points per sprint instead of 15, they won't code faster.

They will simply estimate a 3-point story as a 5-point story.

The result? Velocity goes up. Productivity stays the same (or drops due to stress).

This is why using it for performance encourages inflation, not improvement.

Moving From "How Much?" to "How Fast?"

If you want to track true performance, you must stop looking at Story Points.

Story points represent what you planned to do. They are a guess.

Instead, elite teams focus on Flow Metrics.

To get a real picture of efficiency, you should replace velocity with flow metrics like Cycle Time and Throughput.

These metrics measure the reality of work getting done, not the fantasy of sprint planning.

We may earn a commission if you buy through this link. (This does not increase the price for you)

Frequently Asked Questions (FAQ)

Q: Is high velocity always good in Agile?

No. High velocity can actually indicate "point inflation" or a team cutting corners on quality. It does not necessarily mean high value is being delivered.

Q: Why shouldn't you compare velocity between teams?

Velocity is a relative measure unique to each team's estimation baseline. Team A's "5 points" might be equal to Team B's "13 points." Comparing them is like comparing Fahrenheit to Celsius without a conversion formula.

Q: How does focusing on velocity hurt quality?

When speed (points) is the primary goal, developers may rush through testing or ignore technical debt to "make the sprint commitment." This increases the defect rate.

Q: What happens when velocity becomes a target?

According to Goodhart's Law, the metric loses its value. Teams will unconsciously (or consciously) inflate estimates to meet the target, rendering the data useless for forecasting.

Q: How to explain velocity volatility to stakeholders?

Explain that velocity is a capacity tool for planning, not a productivity tool for judging. Use the analogy of a car's gas tank (capacity) vs. its speedometer (speed).

Conclusion

It is time to stop chasing vanity numbers.

As long as you treat velocity as a goal, you will receive inflated estimates and burn out your best engineers.

Understanding why scrum velocity is not a performance metric is the first step toward Agile maturity.

The future of Agile management isn't about intuition or point-chasing; it's about evidence.