Velocity Misuse and Performance Pressure: Rethinking Agile Metrics
From the The Agile Enterprise Blog
by Stelian ROMAN
"The Agile Enterprise" explores Agility at the Enterprise level, examining how Agile principles can be implemented throughout the organization beyond IT. The blog is inspired by the concept of an Agile Enterprise, introduced by the Agile Manufacturing Forum (1991) and the Manifesto for Agile Software Development (2001). Agility is examined from a Project Management perspective with a focus on areas not covered by frameworks that emerged from the work of small software development teams, such as Risk Management, Ethics, Organisational Change Management and Financial Management.
Recent Posts
The Hidden Risk of AI in Agile: The Illusion of Velocity
An Ethical Reflection on Using AI in Hiring: Respect, Responsibility, Fairness, and Honesty
The Ethics of Externalising Risk: Rethinking “Fail Fast” and MVP in Product Development
Quantum Physics for Year 3: Agile success as a foundation for AI. An Ethical reflection
The Tribe Agile Coach role and the spirit and values of the Agile Manifesto. An ethical reflection
Categories
Agile,
Artificial Intelligence,
Benefits Realization,
Change Management,
Communications Management,
Complexity,
Consulting,
Decision Making,
Disciplined Agile,
Diversity,
Earned Value Management,
Estimating,
Ethics,
General,
Governance,
History,
Innovation,
Knowledge Management,
Leadership,
Lessons Learned,
Metrics,
Organizational Culture,
Product Management,
Risk Management,
Scope Management,
Scrum,
Social Impact,
Stakeholder Management,
Teams,
Testing/Test Management,
Using PMI Standards
Date
Categories:
Agile,
Benefits Realization,
Complexity,
Decision Making,
Disciplined Agile,
Estimating,
Ethics,
Governance,
Metrics,
Organizational Culture,
Product Management,
Scope Management,
Scrum,
Teams
Agile introduced velocity as a simple tool: a way for teams to estimate how much work they can deliver in a sprint, supporting better planning and realistic forecasting. Yet, over time, velocity has been repurposed—and sometimes misused—as a performance metric, leading to unintended consequences for teams and organizations.
The Problem: Planning Tool or Performance Benchmark?
Velocity was never meant to be a Key Performance Indicator (KPI) or a tool for comparing teams. However, it’s common to see organizations:
- Setting targets based on velocity numbers
- Using velocity to compare teams or individuals
- Tying incentives or recognition to velocity increases
This shift puts pressure on teams to "hit the numbers," which can lead to:
- 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
When velocity becomes the yardstick for performance, teams face a fundamental question:
- Are we incentivized to deliver real value—or just to hit metrics?
If the focus is on numbers, the true spirit of Agile—delivering customer value, learning from feedback, and adapting—gets lost. Teams may spend more time managing perceptions than solving real problems.
A New Direction: Value and Outcomes Over Output
The hottest trend in Agile metrics is a move away from output-based measurements like velocity toward value-driven and outcomes-based approaches. This shift means:
- 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
Organizations embracing this mindset are seeing healthier team cultures, more honest communication, and better results for stakeholders.
The Bottom Line:Velocity is a useful planning tool—but it’s not a measure of team worth. The future of Agile metrics lies in focusing on value, outcomes, and ethical practices that support both team wellbeing and organizational goals.
How is your team measuring success? Are your metrics driving value—or just numbers?
Posted on: May 11, 2026 10:31 PM |
Permalink
Comments (1)
Please login or join to subscribe to this item
Luis Branco
CEO| Business Insight, Consultores de Gestão, Ldª
Carcavelos, Lisboa, Portugal
An important and very necessary reflection.
One of the biggest misconceptions in Agile environments is treating velocity as a measure of team worth rather than as a contextual planning aid. Once velocity becomes a target tied to pressure, comparison, or incentives, the metric often stops reflecting reality and starts shaping defensive behaviour.
What makes this especially important is that metrics are never neutral. They influence decisions, priorities, reporting behaviour, psychological safety, and even organizational culture.
I would add one critical point: the real issue is often not the metric itself, but the management logic surrounding it. When organizations reward numbers over learning, value, quality, and sustainable delivery, teams naturally optimize for perception rather than outcomes.
Strong and highly relevant contribution to an important Agile discussion.
Please Login/Register to leave a comment.
|
"The secret to creativity is knowing how to hide your sources."
- Albert Einstein
|
