AgileKoc ToolsVelocity Went Up, But Nobody's Celebrating: Goodhart's Law in Scrum
The sprint ended, velocity hit a record — but the team is silent. This familiar scene marks the moment a metric becomes a target. How does Goodhart's Law play out in Scrum, and how can a Scrum Master break the cycle?
A Sprint Review Scene
The sprint ended. Velocity hit 60 — the highest ever. The Scrum Master pulled up the stats, walked into the retrospective. A moment of celebration was expected. But the team is strangely quiet.
Nobody's cheering. No proud smiles. Just exhaustion, and the weight of the next sprint waiting.
What Is Goodhart's Law?
In 1975, British economist Charles Goodhart observed: 'When a measure becomes a target, it ceases to be a good measure.'
The core idea: you measure something because it matters. Then you make it a target. The team optimizes for hitting that target. And eventually, what you're measuring no longer reflects what you actually care about.
With velocity in Scrum, that's exactly what happens.
How Velocity Gets Corrupted
Velocity starts out as a useful tool — a rough estimate of team capacity, a way to keep sprint planning realistic. But ask yourself: how many of these are happening on your team?
- Story point estimation debates drag on in Sprint Planning
- When a story turns out bigger than expected, the team panics
- When velocity falls short of a sprint target, management asks for an explanation
- In the final days of a sprint, the team cuts quality corners to hit the point count
3 Signs the Metric Has Become the Target
Velocity pressure usually starts quietly. Scrum Masters often notice too late.
These three signals are early warnings:
- Story point estimates keep creeping up. The same work that was small last sprint is now medium. The team has started calibrating estimates against the velocity target.
- The Definition of Done is quietly softening. Manual tests get skipped, code reviews get shorter, it's a small thing it'll be done this sprint becomes a bug in the next sprint.
- In the final sprint days, the team talks about points, not quality. How many points left overtakes Are we doing this right?
Practice with Mastery
What would you do coaching a team under velocity pressure? The full version of this scenario is available in Mastery. The AI coach uses the Socratic method — it won't give you the right answer, it will ask the right question.
Explore Mastery →What Can a Scrum Master Do?
The solution isn't to remove velocity or pretend it doesn't exist — it's to change how velocity is talked about.
Here are three concrete steps that work in practice:
- Use velocity as forecast language, not target language. Instead of we have a 60-point goal this sprint, say we typically deliver 50–65 points, let's plan with that in mind. A small wording shift creates a big mindset shift.
- Remove velocity from retrospective agendas. Focus on outcome quality, learning, and value delivered to the customer. Save velocity discussions for capacity planning only.
- Name the management pressure and break the cycle. Velocity looks low this sprint, but we held the Definition of Done and the customer received the feature they'd been waiting for — which matters more? Ask that question out loud.
From Metrics to Conversations
The antidote to Goodhart's Law isn't changing the metric — it's growing the conversation.
Velocity tells you what got built. It doesn't tell you why the team went quiet. What was learned in the sprint. How the customer feels after it ended.
A Scrum Master's real job isn't to track numbers — it's to keep the conversations behind those numbers alive. If velocity drops, you ask why. If velocity goes up — just like that silent sprint-end scene — you ask how does it feel?
Back to That Sprint
Why was the team silent at the end of that 60-point sprint?
Maybe they'd worked late nights for the last three days. Maybe four stories were marked done with incomplete tests. Maybe the product owner didn't show up to sprint review.
60 points looked like a success. But when velocity becomes the target, the numbers lie — only the team knows the truth. And if the Scrum Master isn't asking about that truth, nobody is.
Try the Related Tool
Discover agile patterns through real cases and Socratic AI. No judgment, at your own pace.
Start exploring->Make your Scrum Master impact visible + free PDF
Get short, practical tips each week. Your first email includes the “Scrum Master Impact Dashboard” PDF to help make your contribution visible.
How do you prove your impact as a Scrum Master?
Without obsessing over velocity: 5 metrics + a 6-week plan for a clear impact story.
- 5-metric impact dashboard
- 6-week execution plan
- Manager-ready talk track
We respect your privacy. We only use your email to send the PDF and weekly tips.
No spam. Unsubscribe anytime.