The Agile Enterprise
by Stelian ROMAN
This blog will explore agility at the enterprise level, examining how agile principles can be implemented throughout the organization—and in departments other than IT.
Recent Posts
Seven at One Blow: Lessons for Agile Teams and the Pitfalls of Story Points Misunderstanding
Lessons from the Emperor’s New Clothes: Rethinking Agile Transformation
Transparency in Backlog Prioritisation for AI Features
Balancing Model Complexity vs Interpretability, Finding the Sweet Spot in Machine Learning
Fairness vs Performance Trade-Offs in Agile Delivery
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
Date
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 DilemmaWhen 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 OutputThe 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)
|
"Too many pieces of music finish too long after the end."
- Igor Stravinsky
|
