Why Sprint Velocity Is the Wrong Metric to Obsess Over
Your team just hit 80 story points. Congratulations — you may have just optimized your way to delivering the wrong thing faster.
Velocity started as an internal forecasting tool. A way for teams to say: "Based on what we've done, here's roughly what we can do next sprint." That's it. It was never meant to be a performance indicator, a target, or a measure of team health. And yet, in countless organizations, velocity has become exactly that — a number that managers track, compare, and pressure teams to grow quarter after quarter.
The gamification problem
When velocity becomes a target, teams respond rationally. Story points inflate. Small tasks get padded. Risky exploratory work gets avoided in favor of well-understood tickets that carry predictable point values. The number goes up. The actual delivery of customer value may not. You've created a metric that measures itself.
What to track instead
The metrics that actually correlate with agile health are outcome-oriented: customer cycle time (how long from idea to value in the customer's hands), deployment frequency, change failure rate, and mean time to recovery. These are the DORA metrics — and unlike velocity, they can't easily be gamed because they're grounded in real operational events, not estimation abstractions. Velocity is a planning tool. Use it as one. The moment you put it on a dashboard visible to leadership, you've changed what it measures.
The conversation you need to have
If your stakeholders are asking about velocity, the right response isn't to show them a better velocity chart. It's to introduce them to the questions velocity can't answer: Are customers getting value? Is the system getting healthier? Is the team learning? Those questions take more courage to ask — and they're the only ones worth answering.
Ready to put this into practice?
Join a SAFe certification course and master agile at scale.
Browse Courses →
