Introduction
The Agile Enterprise, defined in manufacturing in the last decades of the 20th century, is now not only a reality but most likely the norm. In Agile environments using frameworks inspired by the Manifesto for Agile Software Development, velocity is a widely used metric. It measures the amount of work a team completes during a Sprint, typically quantified in story points or similar units. Created as a Team practice to plan and track their work, some organizations often use velocity to track progress, forecast outcomes, and sometimes to compare teams. Comparing teams based on their velocity can lead to serious ethical challenges. This blog post explores these concerns, drawing on respected sources such as the PMI Code of Ethics and Professional Conduct, the Agile Practice Guide, ISO 31000, and the PMBOK. The post highlights some challenges and provides recommendations.
Challenges
1. Misrepresentation of Performance
According to the PMI Code of Ethics and Professional Conduct, practitioners are expected to be honest and accurate in their representations. Velocity is a relative measure unique to each team. Comparing Team A’s velocity to Team B’s can misrepresent both teams’ true performance, as each team’s story points are calibrated differently. Ron Jeffries, one of the creators of Extreme Programming, emphasizes that velocity is a tool for a single team’s planning, not a scoreboard for competition.
2. Context Ignorance
Agile practitioners' discussions on Agile forums highlight that team context, such as domain complexity, team maturity, and technical debt, affects velocity. Ignoring these variables violates the PMI value of Responsibility, which calls for decision-making based on proper understanding. Comparing teams without considering context can lead to unfair judgments and demotivation.
3. Pressure to Manipulate Metrics
When velocity becomes a benchmark for comparison, teams may inflate estimates or under-commit to boost their numbers. The Agile Practice Guide warns that such behaviour undermines both transparency and trust, two of the core Agile values. This is also contrary to the PMI principle of Fairness, which requires practitioners to make decisions impartially and objectively.
4. Erosion of Collaboration
Inappropriate measurements create competition instead of collaboration. When teams are pitted against each other, the culture shifts from shared learning to rivalry. This not only damages morale but also hinders organizational learning and innovation.
5. Risk Amplification
ISO 31000, the international standard for risk management, stresses the importance of recognizing and addressing risks in organizational practices. Comparing velocities without understanding underlying risks can create blind spots, leading to poor decision-making and increased project risk.
6. Violation of Professional Conduct
The PMBOK emphasizes respect, honesty, and responsibility. Using velocity comparisons to make personnel decisions (such as promotions or layoffs) can lead to ethical breaches if the metric is misunderstood or misapplied. Such practices may also create a toxic work environment.
Recommendations
1. Educate Stakeholders
PMI and the Agile Practice Guide recommend ongoing education about metrics. Make sure all stakeholders understand that velocity is a planning tool for individual teams, not a comparative performance metric. Establish a culture where velocity is used for improvement, not competition.
2. Focus on Outcomes, Not Metrics
Measure what matters: customer value, product quality, and team satisfaction. Shift the conversation from “how fast are you going?” to “what value are you delivering?” This aligns with the PMI’s focus on delivering value and meeting stakeholder needs.
3. Consider Qualitative Factors
Take into consideration qualitative factors such as team morale, innovation, and adaptability. Incorporate regular retrospectives and feedback loops to assess these dimensions alongside quantitative metrics.
4. Promote Transparency and Trust
The Agile Practice Guide highlights the importance of transparency in Agile teams. Encourage teams to be open about their progress, challenges, and context. This fosters trust and discourages metric manipulation.
5. Use ISO 31000 Principles for Risk Management
Apply ISO 31000 guidelines to assess risks associated with metric misuse. Identify potential unintended consequences and address them proactively. This can involve scenario planning, training, and open dialogue about ethical risks.
6. Align With Professional Ethics
Reinforce PMI’s Code of Ethics and Professional Conduct through regular training and leadership modelling. Ensure that performance assessments and recognition are based on a holistic view of contribution, not a single metric.
The Bottom Line
Comparing teams using velocity is not just a technical mistake; it’s an ethical one. Velocity is a local, team-specific planning tool. Misusing it for inter-team comparison can lead to misrepresentation, demotivation, metric manipulation, and ethical violations. By focusing on value delivery, transparency, and responsible risk management, organizations can foster a healthier and more ethical Agile culture. Teams and organisations must honour professional codes and uphold the spirit of Agile by using metrics wisely and ethically.
Questions for Readers
1. Have you experienced negative ethical consequences from velocity comparisons in your organization? How were they addressed?
2. What alternative metrics or approaches have you found effective for assessing team performance ethically?
3. How does your organization ensure that metrics are used ethically to foster growth rather than unhealthy competition?
