The Agile Enterprise

• The intervals between points are not consistent or meaningful.
• The results can be misleading, producing averages that do not correspond to any real scenario (e.g., an average story size of 4.2 points).
• It gives a false sense of precision and objectivity.

• Deceive stakeholders about team performance or project predictability.
• Lead to unfair evaluations of teams or individuals based on invalid data.
• Undermine psychological safety, as teams feel pressured to "hit the numbers."

1. Recognize the Limits: Treat story points and other ordinal metrics as relative rankings, not precise measurements.
2. Avoid Arithmetic Operations: Don’t calculate averages or run regressions on ordinal data. Instead, look at frequency counts, medians, or modes.
3. Educate Stakeholders: Ensure that everyone understands what ordinal metrics mean and how they should (and should not) be used.
4. Report with Integrity: Be transparent about the limitations of your data and the methods used to analyse it.
5. Focus on Conversation: Use ordinal metrics to drive discussion and consensus, not to produce misleading statistics.

Understanding Metric Integrity
Metric integrity refers to the accuracy, consistency, and appropriate use of quantitative and qualitative indicators within an organization. High-integrity metrics serve as reliable guides for decision-making, while low-integrity metrics can mislead, distort, and erode trust. In Agile environments, story points and velocity are designed as tools for internal estimation and forecasting—not for external comparison or performance evaluation.
Yet, the pressure to deliver, combined with a desire for accountability and transparency, often leads to these semiquantitative metrics being misused as hard measures of productivity. The result is a distortion of their intended purpose and the risk of unethical practices—either intentional or accidental.

The Semiquantitative Trap: Story Points and Velocity
Story Points & Velocity: Designed for Relative Measurement
Story points are a relative measure of effort, complexity, and uncertainty that a team assigns to pieces of work (user stories). Velocity, typically calculated as the sum of story points completed in a sprint, is meant to help teams forecast what they can accomplish in the future based on their own historical performance.
Key characteristics:

• Team-specific: Each team calibrates story points differently. What’s a “3” for one team might be a “5” for another.
• Non-absolute: Story points have no universal or external meaning.
• For planning, not judging: Velocity is meant for a team’s internal use, not for comparing teams or individuals.

1. False Comparisons: Comparing velocities across teams or over time without context leads to misleading conclusions.
2. Metric Gaming: Teams may inflate story point estimates to appear more productive, undermining the very value of the metric.
3. Loss of Trust: Stakeholders lose faith in the metrics when they see them manipulated or misunderstood.
4. Distorted Incentives: Teams focus on increasing velocity rather than delivering customer value.

Ethics in Data Reporting: The Pillar of Honesty
Honesty is a foundational ethical principle in any form of reporting, including data and metrics. Most Codes of Ethics states that professionals should be "honest and trustworthy" and "avoid harm" in their work. Misrepresenting or misunderstanding metrics like velocity can violate this principle in several ways:
1. Misrepresentation
Presenting velocity as a literal measure of productivity—especially to external stakeholders or executives—misrepresents what the metric means. This can lead to flawed decisions and unfair judgments about team performance.
2. Omission of Context
Failing to clarify that story points and velocity are team-relative, not absolute, is a form of dishonesty by omission. Ethical reporting requires transparency about the limitations and appropriate interpretations of data.
3. Encouraging Unethical Behaviour
When teams are pressured to "improve" their velocity, they may consciously or unconsciously inflate estimates or manipulate the process, further eroding integrity and trust.
4. Data Integrity Violations
The misuse of semiquantitative metrics can result in data that does not reflect reality, violating both the letter and spirit of honest reporting.

Real-World Consequences
The consequences of violating honesty in metric reporting are not abstract. Teams and organizations have experienced:

• Erosion of psychological safety: Team members feel pressured to meet arbitrary targets, stifling innovation and open communication.
• Decision-making based on flawed data: Leaders make resourcing or performance decisions that are not grounded in reality.
• Loss of credibility: Once stakeholders discover that metrics have been gamed or misrepresented, trust is difficult to rebuild.

Best Practices: Upholding Metric Integrity & Ethical Reporting

1. Educate Stakeholders: Ensure everyone—from team members to executives—understands what story points and velocity are (and are not).
2. Use Metrics for Their Intended Purpose: Keep story points and velocity as internal planning tools, not external performance measures.
3. Report with Transparency: Always include context, limitations, and appropriate caveats when presenting semiquantitative data.
4. Watch for Unintended Incentives: Regularly review how metrics are used and ensure they are not creating perverse incentives.
5. Promote a Culture of Honesty: Encourage open discussions about metrics, limitations, and the importance of data integrity.

The bottom line
Metrics are powerful tools, but with great power comes great responsibility. The fallacy of treating velocity as an absolute measure of productivity is more than just a technical error—it is an ethical one. By understanding the limits of semiquantitative metrics, committing to transparency, and upholding the ethical pillar of honesty, organizations can foster trust, make better decisions, and ultimately deliver more value to their customers.
Let velocity remain what it was meant to be: a guide for teams, not a yardstick for judgment.
How have you seen velocity or story points used (or misused) in your organization, and what impact did it have on team morale, transparency, or trust?
Share your experiences and perspectives below.

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.

1. Loss of Predictive Value: Inflated points mean that velocity no longer reflects capacity. Forecasts become unreliable.
2. Broken Trust: Stakeholders realize the numbers are being gamed, eroding confidence in both the process and the people.
3. Misaligned Incentives: Teams focus on maximizing metrics, not customer value or quality.
4. 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.

Introduction
In the world of project management and software delivery, estimates are more than just numbers—they are perceived as commitments, foundations for trust, and often the basis for critical business decisions. Yet, anyone who has worked in an organization with aggressive growth targets or ambitious transformation agendas knows the following scenario all too well: leadership arrives with a predefined budget or timeline, and suddenly, the estimation process becomes less about honest forecasting and more about making the numbers fit. This blog post explores the ethical dilemma of "adjusting" estimation models under executive pressure, the consequences for teams and organizations, and how to handle these situations with integrity.

The Anatomy of Estimation
Estimation, whether in hours, story points, or financial terms, is fundamentally an exercise in professional judgment. Its purpose is to inform planning, resource allocation, and risk management. Good estimates:

• Reflect reality as closely as possible
• Are based on historical data and experience
• Include assumptions and uncertainty

Executive Pressure: When Numbers Become Political
The Scenario
A new strategic initiative is announced. Executives declare, “We have $500,000 and three months to deliver this project.” The team’s initial estimates, based on sound engineering judgment, suggest the work will take six months and $1 million. Leadership asks for the numbers to be “revisited.” The message is clear: adjust the model until it fits the budget, or the project won’t get approved.
Why Does This Happen?

• Budget-Driven Planning: Organizations often set budgets based on business needs, not technical reality.
• Optimism Bias: Leaders may believe teams can "do more with less" if sufficiently motivated.
• Political Incentives: Middle managers may fear pushback or lost opportunities if they surface the real risks.
• Short-Term Wins: There is pressure to show quick ROI or meet shareholder expectations.

The Ethical Dilemma
The Temptation to “Adjust”
“Adjusting” estimation models under pressure can take many forms:

• Redefining scope without clear communication
• Compressing schedules and quietly assuming overtime
• Reclassifying work to less visible categories
• Omitting risk factors or historical overruns

• Erosion of Trust: Stakeholders make decisions based on unreliable data. When reality catches up, blame—and mistrust—follow.
• Moral Distress: Team members and managers caught in the middle suffer stress, disengagement, and a sense of complicity.
• Downstream Harm: Projects fail, quality suffers, and customer value is compromised.
• Violation of Professional Codes: Most engineering and project management codes of ethics mandate honesty, transparency, and duty to report risks.

Real-World Consequences

• Project Failure: The most common result of fabricated estimates is missed deadlines, cost overruns, and failed deliveries.
• Team Burnout: Unrealistic expectations lead to excessive overtime, low morale, and attrition.
• Blame and Cover-Ups: When the truth surfaces, the focus shifts to blame rather than learning.
• Reputational Damage: Organizations with a pattern of "magical thinking" lose credibility with clients, investors, and employees.

Navigating the Pressure: Acting with Integrity

1. Document Assumptions: Be explicit about what is and isn’t included in the estimate. Make risks and uncertainties visible.
2. Communicate Early and Often: Don’t wait until the project is in crisis to reveal the gap between estimates and budgets. Share concerns with leadership as early as possible.
3. Offer Alternatives: Instead of simply adjusting numbers, propose options: “With this budget, we can deliver X features by this date. For full scope, we need Y.”
4. Use Ranges and confidence levels: Instead of $500,000 use between 400,000 and 600,000 and instead of 6 months say between 5 and 8 months. Indicate how confident the team is in the estimations provided.
5. Stand by Professional Principles: Reference industry codes of ethics and best practices to support your position. This frames honesty as a professional responsibility, not a personal disagreement.
6. Escalate When Necessary: If ethical concerns are ignored, use formal escalation channels or seek guidance from mentors, professional organizations, or HR.

Building a Culture of Honest Estimation

• Leadership Accountability: Executives must set the tone by rewarding honesty and realism, not just optimism.
• Safe Environments: Teams should feel safe surfacing risks and bad news without fear of retribution.
• Continuous Learning: Treat estimate overruns as learning opportunities, not failures to be punished or hidden.
• Transparency in Reporting: Regularly review actuals versus estimates and discuss gaps openly.

The bottom line
Fabricating estimates to fit a predefined budget may feel like an expedient solution, but it is a breach of professional ethics with real consequences. The path to sustainable, successful delivery is paved with honesty, transparency, and the courage to speak truth to power. By holding the line on ethical estimation, teams and organizations can build trust, deliver better outcomes, and foster a culture where reality is respected—not adjusted away.

Question for Readers:
Have you been asked to "adjust" estimates to fit a budget or timeline? How did you handle the ethical dilemma, and what impact did it have on your team or organization? Share your stories and insights in the comments below.

The Problem: Planning Tool or Performance Benchmark?

• Setting targets based on velocity numbers
• Using velocity to compare teams or individuals
• Tying incentives or recognition to velocity increases

• Gaming the system (inflating story points or splitting work unnaturally)
• Burnout and stress from relentless demands
• Dishonest reporting to avoid negative scrutiny

The Ethical Dilemma

• Are we incentivized to deliver real value—or just to hit metrics?

A New Direction: Value and Outcomes Over Output

• Prioritizing customer impact over story point accumulation
• Measuring success by outcomes (e.g., user satisfaction, business goals achieved)
• Rewarding learning and adaptation, not just speed