Introduction
Agile frameworks like Scrum and XP have brought a wealth of transparency and data-driven insights to software delivery. Metrics such as velocity, burndown rates, and throughput are tools for teams to self-assess, plan, and improve. However, these metrics are increasingly being used in ways that were never intended—most notably, as weapons in performance reviews and appraisals. One of the most contentious practices is the comparison of velocity across entirely different teams, a topic that has sparked heated debates in forums and communities worldwide. This blog post explores why comparing the velocity of different Agile teams during performance appraisals is unfair, the damage it causes, and what organizations should do instead.
Understanding Velocity: Its Purpose and Limits
Velocity is a measure of how much work a team completes in a given iteration, typically using story points or work items. Its original intent is clear: it is a planning tool, not a productivity scorecard. Velocity helps teams forecast how much they can deliver in future sprints, making commitments realistic and sustainable.
Key characteristics of velocity include:
- Team-Relative Calibration: Each team assigns story points differently. A 5-point story to Team A might be a 3-point story to Team B.
- Dynamic and Evolving: Velocity changes as teams form, storm, norm and even when they perform, or as project complexity and team composition shift.
- Contextual Meaning: It reflects a team’s unique circumstances: skill sets, domain knowledge, technical debt, and even tooling.
Weaponization: How Metrics Go Astray
Metrics as Performance Weapons
The moment metrics are tied to performance reviews, pay, or promotions, their meaning and utility change. Instead of being used for learning and improvement, they become targets to be gamed or dreaded numbers looming over every retrospective.
Comparing Apples and Oranges
Many organizations, seeking objectivity, start comparing velocity across teams: “Why is Team X delivering 50 story points per sprint, but Team Y only 27?” The question of “How many story points should a team deliver in a Sprint is often asked in Agile forums. This approach fails to recognize:
- Different Calibration: Each team defines story points differently.
- Varying Challenges: Teams may be working on fundamentally different problems with distinct complexity and risk.
- Resource and Skill Disparities: Team makeup, experience, and even available tools differ.
- Maturity and Stability: Newly formed teams naturally have lower velocity; mature teams may have optimized their workflow.
The Fallout
Forum discussions on platforms like LinkedIn, Reddit, Stack Overflow, and Agile community boards are rife with stories of demoralized teams, manipulated metrics, and toxic work environments resulting from these practices. Teams inflate story points or sandbag their estimates to protect themselves. Collaboration suffers as teams start competing instead of cooperating. Honest reporting is replaced by metric gaming.
Real-World Voices: What the Community Is Saying
- “Our leadership compares velocity across teams in every review. It’s demotivating, and we spend more time debating points than building software.”
- “We had two teams, one working on legacy code and one on greenfield. Of course, their velocities were different! But HR didn’t get it.”
- “After velocity became a performance metric, our estimates doubled overnight.”
These voices echo a fundamental truth: Weaponizing Agile metrics undermines the very principles on which Agile was founded—trust, transparency, and respect for people.
The Ethical Dimension: Fairness and Respect
When velocity is used as a comparative tool for performance appraisals, it violates the ethical principle of fairness. It disregards context and treats complex, multifaceted work as a simple number. This approach not only demoralizes teams but also pushes them towards practices that degrade the quality of data and outcomes.
Agile values, as articulated in the Manifesto for Agile Software Development and in codes of ethics for IT and management professionals, call for:
- Respect for Individuals and Teams: Recognizing unique strengths, challenges, and contexts.
- Honesty and Transparency: Reporting reality, not just numbers.
- Collaboration Over Competition: Fostering environments where teams help each other grow.
What Organizations Should Do Instead
- Educate Leaders and HR: Help decision-makers understand what velocity means (and doesn’t mean).
- Ban Cross-Team Comparisons: Make it a policy to never compare velocity or story points across teams.
- Use Metrics for Improvement, Not Judgment: Focus on trends within a team over time and use metrics to facilitate conversations about process—not as performance weapons.
- Prioritize Qualitative Feedback: Incorporate peer reviews, 360-degree feedback, and self-assessment into appraisals.
- Encourage Safe Reporting: Create cultures where honest communication is rewarded, not punished.
The bottom line
Velocity is a valuable tool in Agile, but only when used as intended: for team-level planning, reflection, and growth. Comparing the velocities of different teams for performance reviews is not just mathematically flawed—it’s ethically indefensible. Organizations that weaponize Agile metrics risk losing trust, degrading data quality, and ultimately harming their ability to deliver value. By respecting the limits of metrics and putting people first, companies can foster healthier, more successful Agile cultures.
Question for Readers:
-Have you witnessed or experienced the weaponization of Agile metrics—like cross-team velocity comparisons—in performance reviews?
-How did it impact your team’s culture, motivation, or reporting practices?
Share your thoughts and stories in the comments below.
