Introduction
In the pursuit of productivity and predictability, organizations often turn to metrics to track progress and drive improvement. In Agile software delivery, measures like story points and velocity have become ubiquitous tools for estimation and forecasting. Yet, as the British economist Charles Goodhart famously observed, “When a measure becomes a target, it ceases to be a good measure.” This principle—known as Goodhart’s Law—captures a dangerous dynamic: when management fixates on metrics as ends in themselves, teams adapt their behaviour to meet the numbers, often at the expense of genuine progress and transparency. This blog post explores how Goodhart’s Law manifests in Agile delivery, why it leads teams to inflate point sizing, and what organizations can do to foster healthier measurement cultures.
Understanding Goodhart’s Law
Goodhart’s Law originated in the context of economic policy, but its implications are universal. The law warns that when a metric is singled out as a performance target, people will inevitably find ways to game the system. The measure stops reflecting the underlying reality and instead becomes a distorted proxy, undermining its original intent.
In Agile software development, common metrics like story points, velocity, and burndown charts are intended to provide insight into team capacity, help with forecasting, and support continuous improvement. But when these metrics become management’s primary focus—tied to rewards, recognition, or even job security—they lose their power as objective indicators.
The Role of Metrics in Agile Delivery
Agile methodologies encourage self-organizing teams to estimate and plan their own work. Story points are assigned to user stories to reflect relative complexity, effort, and uncertainty. Velocity tracks how many points a team completes per iteration, informing future planning.
These metrics were created for internal use only:
- Story points: Calibrated by and for the team, not meant for external comparison.
- Velocity: A tool for the team to understand its own rhythm, not a performance metric.
How Goodhart’s Law Plays Out: Inflating Point Sizing
The Pressure to Perform
When management starts using story points or velocity as benchmarks for productivity, teams feel pressure to “keep up.” This is especially acute when:
- Velocity is shared in dashboards visible to leadership or clients.
- Team performance is compared across organisation(s).
- Rewards, bonuses, or advancement are tied to hitting certain metrics.
Rather than working faster or delivering more value, teams may unconsciously or deliberately inflate story point estimates to make their velocity appear higher. The logic is simple: if a 3-point story is now estimated as a 5, the same work results in a higher velocity. Over time, the relative calibration that made story points useful is lost.
The Consequences
- Loss of Predictive Value: Inflated points mean that velocity no longer reflects capacity. Forecasts become unreliable.
- Broken Trust: Stakeholders realize the numbers are being gamed, eroding confidence in both the process and the people.
- Misaligned Incentives: Teams focus on maximizing metrics, not customer value or quality.
- Metric Fatigue: Teams become cynical about measurement, seeing it as a hoop to jump through rather than a tool for improvement.
Real-World Examples
Consider a software organization where leadership sets a target: "Every team must increase its velocity by 20% this quarter." Teams, facing pressure and knowing that points are subjective, simply start assigning higher numbers to similar user stories. Management sees rising velocity, but actual delivery speed and product value remain unchanged—or even decline as teams cut corners to hit the numbers.
In another case, two teams are compared on velocity. One team, with more senior members, estimates conservatively; the other inflates points to look productive. Leadership, unaware of the calibration differences, rewards the second team, sending a clear signal that gaming the numbers is more valuable than honest reporting.
Breaking the Cycle: Healthy Metric Cultures
1. Metrics as Tools, Not Targets
Reframe metrics as aids for learning and planning, not as goals to achieve. Use them to spark conversations, not drive competition.
2. Focus on Outcomes, Not Outputs
Prioritize customer value, quality, and team health over raw throughput. Ask: Are we building the right thing? Are we improving?
3. Educate Stakeholders
Train managers, clients, and teams on what metrics can and cannot tell you. Demystify story points and velocity—make it clear they are metrics for the team, not universal currencies. Remind managers that story points originated from “ideal” days and should not be used as an obfuscation of time/cost estimation.
4. Guard Against Comparisons
Avoid comparing teams by their story points or velocity. Every team’s calibration is unique. Recognize and respect those differences.
5. Encourage Transparency
Promote psychological safety so teams can be honest about their estimates, blockers, and progress—without fear of punishment for “low” numbers.
The bottom line
Goodhart’s Law offers a cautionary tale for all organizations seeking to improve through measurement. In Agile delivery, turning metrics like story points and velocity into targets invites gaming and undermines the very insights those measures were meant to provide. To avoid falling into this trap, leaders must foster a culture where metrics are used for learning, not judgment, and where the ultimate focus remains on customer value, sustainable pace, and team trust.
Question for Readers:
Have you witnessed or experienced the effects of Goodhart’s Law in Agile delivery—such as point inflation or metric gaming—in your own teams or organizations? How did it impact trust, planning, or outcomes? Share your stories and insights in the comments below.
