Introduction
Agile frameworks that inspired the Manifesto for Agile Software Development, especially Scrum, place the Product Owner at the centre of value delivery, often focusing on maximizing outcomes for customers and users. But who exactly defines “value”? Should the Product Owner optimize for paying customers, or should they balance competing interests of other stakeholders such as employees, communities, regulators, and vulnerable users? This debate is more than academic; it shapes the ethical foundation of modern product development. This blog post examines the challenges and recommendations for reconciling customer and stakeholder value in Agile environments.
Challenges
Defining “Value”Within Agile, “value” is often interpreted as what delivers the most benefit to customers; usually those paying for the product or project. However, the PMI Code of Ethics urges practitioners to consider responsibility, respect, fairness, and honesty, which can mean weighing impacts beyond the immediate customer. Ron Jeffries, the co-creator of XP and the person credited with inventing Story Points, has also argued that short-term customer outcomes can sometimes undermine broader social good.
Conflicting Interests
A common scenario: a product feature increases sales but encourages addictive user behaviour. While the Product Owner might celebrate a surge in revenue, is it ethical if the feature harms vulnerable users? Project Management and Risk Management standards warn against focusing solely on one stakeholder group, as negative externalities can affect brand reputation, employee morale, and provoke regulatory backlash.
Who Gets a Voice?
Stakeholders include employees, suppliers, communities, regulators, and society at large—not just customers. PMBOK and the Agile Practice Guide both emphasize stakeholder engagement as core to project success. Value is context-dependent and multi-dimensional, requiring ongoing dialogue and compromise. Yet, Agile teams often lack systematic processes for surfacing and integrating diverse stakeholder perspectives.
Ethical Dilemmas
What should Agile teams do when maximizing customer value means disregarding employee well-being (e.g., through crunch periods), or when community or environmental harms are foreseeable but not immediately “visible” to customers? The PMI Code and ISO 31000 urge proactive risk identification and ethical decision-making, but real-world pressures can incentivize short-term gains over long-term responsibility.
Recommendations
Broaden the Definition of ValueProduct Owners should explicitly consider the needs and impacts on all stakeholders. Use stakeholder mapping tools from PMBOK and Agile Practice Guide to regularly identify and assess interests beyond customers.
Embed Ethical Principles in Decision-Making
Adopt frameworks such as the PMI Code of Ethics and ISO 31000 to guide decisions. Incorporate regular ethics reviews into sprint planning and reviews, especially when features might harm vulnerable users or conflict with regulatory or social expectations.
Foster Stakeholder Engagement
Create feedback loops with not only customers but also employees, community representatives, and regulators. Rick Dove’s work underscores the value of adaptive dialogue; consider stakeholder panels or advisory groups.
Assess and Mitigate Risks Holistically
Use risk management tools to evaluate both direct and indirect impacts of product features. For example, a feature that increases engagement should be assessed for the potential of addictive use and social consequences.
Create Transparency and Accountability
Clearly communicate the rationale behind decisions, including the trade-offs between customer and stakeholder value. Encourage open discussion within teams about ethical concerns, referencing the Agile Practice Guide’s emphasis on collaboration and trust.
The Bottom Line
Agile’s commitment to delivering value is a strength, but only if “value” is defined in a way that honours the complexity of stakeholder relationships and ethical responsibility. Product Owners must resist the temptation to equate value solely with customer or revenue gains, and instead champion a holistic, ethical approach that balances diverse interests. By embedding ethical principles, fostering broad stakeholder engagement, and proactively managing risks, Agile teams can deliver sustainable value that truly benefits society.
Questions for Readers
- How does your project team/organization define “value”—and who gets to decide?
- Can you recall a time when delivering customer value conflicted with broader stakeholder interests? What was the impact?
- What practices could your Agile team adopt to better integrate ethical and stakeholder concerns into product decisions?
