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.
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.
Blog post: The Ethical Aspect of Comparing Teams Using Velocity: A Deep Dive
ProjectManagement.com - The Agile Enterprise
