Introduction
Agile delivery is based on trust; “Individuals and interactions over processes and tools” and “Working software over comprehensive documentation” are two of the core values, often misinterpreted as a replacement of traditional ‘rigid’ governance. Initially, a challenge to the success of Lean Six Sigma, Agile, intentionally or not, didn’t provide specific metrics, seen as a sign of risk-averse organisations. However, in the quest for higher performance, and without clear and specific Agile metrics, organizations often turn to metrics from Lean Six Sigma—such as cycle time, throughput, defect rates, and process efficiency—to measure the success of Agile projects. These metrics seem objective and actionable, promising to optimize the flow of work. However, a deep ethical debate simmers beneath the surface: Are we measuring what truly matters? Are we rewarding teams for activity, or for genuine customer value? This blog post explores the ethical dilemma of measuring output versus measuring value in Agile environments, from an ethical perspective.
Challenges
The core challenge lies in the tension between what is easy to measure and what is truly meaningful. Lean Six Sigma metrics—cycle time, throughput, defect rates, and process efficiency—offer quantitative data that can be tracked and improved. In Agile projects, these metrics frequently become KPIs. In the true Agile mindset, the intent is to foster transparency and continuous improvement. However, many Agile practitioners argue that such metrics are against the Agile principles and risk shifting team focus from customer outcomes to productivity statistics.
For example, a team may prioritize closing more tickets or delivering more story points each sprint, believing that these numbers reflect success. But what if those tickets represent features that customers don’t use, or story points accrue for technical tasks disconnected from business value? As Ron Jeffries, one of the authors of the Agile Manifesto, has cautioned, “Delivering more stories faster does not ensure delivering more value.”. Moreover, there are teams assigning story points to defects and adding them to ‘velocity’. Sizing defects is useful only for planning and for calculating the percentage of rework, another Lean Six Sigma metric, but not to improve the team’s ‘performance’
Teams can, intentionally or not, game the system—maximizing throughput and activity without a corresponding increase in value delivered. The Agile Practice Guide and PMBOK both highlight the danger of “vanity metrics” that reward teams for busywork rather than outcomes.
This brings us to an ethical crossroads. According to the PMI Code of Ethics and Professional Conduct, project practitioners are obligated to act with responsibility, respect, fairness, and honesty. Is it fair or honest to reward a team for high throughput if their work has little impact on customer satisfaction? ISO 31000, the international standard for risk management, reminds us that risk is not just a matter of likelihood and impact but also of values and perceptions. If measurement systems promote the wrong behaviours, they introduce ethical risk into the organization.
Recommendations
How can teams and organizations resolve this ethical tension? The answer lies in re-balancing what we measure. Activity metrics have their place—they help identify bottlenecks and waste. However, they must be complemented by value-based metrics that reflect customer outcomes and business impact.
Here are five recommendations for ethically sound measurement:
- Prioritize Outcome Metrics: Include metrics such as customer satisfaction, feature adoption, Net Promoter Score (NPS), and business impact. These offer a direct line to customer value.
- Use Activity Metrics as Diagnostic Tools, Not Rewards: Cycle time and throughput help teams identify inefficiencies, but they should not be the sole basis for recognition or incentives.
- Align Metrics with Agile Principles: As the Agile Manifesto states, the highest priority is “to satisfy the customer through early and continuous delivery of valuable software.” Measurement systems should reinforce this, not undermine it.
- Encourage Transparency and Integrity: Make metric goals and their rationale clear to all stakeholders. Use data to foster honest conversations about improvement, not as a weapon.
- Review Metrics Regularly: Collaborate with teams and customers to ensure that what you’re measuring remains relevant and ethical as business needs evolve.
The PMBOK and Agile Practice Guide both advocate for a balanced approach to measurement, highlighting the importance of systems thinking, optimizing for the whole, not just the parts.
The Bottom Line
The ethical debate over measuring output versus value is not a theoretical exercise. It has real consequences for team behaviour, customer satisfaction, and organizational integrity. Rewarding teams solely for higher output can unintentionally incentivize waste, undermine Agile principles, and erode trust. Lean Six Sigma metrics are powerful when applied judiciously, but organizations must ensure their measurement systems are ethically aligned to deliver meaningful value to customers.
Questions for reflection:
- How does your organization balance output metrics with value-based outcomes in Agile projects?
- Have you ever seen (or experienced) negative behaviours arising from an overemphasis on productivity metrics?
- What ethical guidelines should leaders use when designing measurement systems for Agile teams?
