The Agile Enterprise

Introduction

Agile communities are no strangers to conversations about team dynamics, culture, and ethics. Tuckman’s ‘ladder” of group development, published in 1965, is a core topic in Agile training courses.  As Tuckman indicated, all these phases are necessary and inevitable in order for a team to grow, face up to challenges, tackle problems, find solutions, plan work, and deliver results. These inevitable phases are critical to team growth and development. An Agile enterprise must create the support culture and processes for teams and individuals, including one of the most important prerequisites: psychological safety.  Psychological safety—the shared belief that the team is safe for interpersonal risk-taking—has become a cornerstone of high-performing teams. When combined with robust team ethics, psychological safety forms the backbone of trust, transparency, and innovation within Agile environments.

Documents such as the PMI Code of Ethics and Professional Conduct, the Agile Practice Guide, ISO 31000, and the PMBOK all underscore the importance of ethical conduct, respect, and open communication. These principles not only shape how teams interact but also influence the ability to deliver value in fast-paced, complex projects.

This blog post explores the relationship between psychological safety and team ethics, the challenges faced by Agile teams, and recommendations to overcome them.

Challenges

The Myth of Respectful Treatment

Respectful treatment is often touted as a given in Agile teams. However, the reality is that even well-intentioned teams can slip into patterns of microaggressions, exclusion, or unintentional disrespect. The PMI Code of Ethics places respect at its core, defining it as “our duty to show a high regard for ourselves, others, and the resources entrusted to us.” Yet, Agile practitioners report that respect can be compromised under high pressure, tight deadlines, or when dealing with strong personalities.

Blame Cultures and Fear of Failure

A culture of blame is the antithesis of psychological safety. The Agile Practice Guide points out that when mistakes are met with finger-pointing rather than learning, teams become risk-averse and innovation stalls. In organizations where blame is common, team members often conceal problems, avoid experimenting, and withhold valuable feedback. This undermines both project outcomes and individual well-being.

Speaking Up: Risk and Retaliation

ISO 31000 highlights the importance of risk communication, yet many Agile teams struggle to speak up about risks, issues, or unethical behaviours. The fear of retaliation, ridicule, or being labelled a troublemaker can silence even the most conscientious team members. This silence can allow ethical breaches, technical debt, or project risks to fester until they become critical.

Handling Toxic Stakeholders

Dealing with toxic stakeholders—whether they are clients, managers, or team members—presents a significant challenge. On Agile forums there are many posts about the detrimental impact of toxic behaviours, such as manipulation, bullying, or undermining team decisions. Agile teams must navigate these situations delicately, balancing the need for stakeholder engagement with the imperative to protect team well-being and uphold ethical standards.

Recommendations

Embed Ethical Principles in Team Norms

Draw on the PMI Code of Ethics and the Agile Practice Guide to establish explicit team norms around respect, responsibility, fairness, and honesty. Make these principles visible—post them in the team area, reference them in retrospectives, and revisit them regularly.

Foster Psychological Safety Deliberately

Almost 3 decades ago, when Extreme Programming was developed, Ron Jeffries advocated for creating environments where it is safe to ask questions, challenge assumptions, and admit mistakes. Leaders, including Scrum Masters, can model vulnerability by admitting their own errors and inviting feedback. Regular check-ins, anonymous feedback channels, and psychological safety assessments can help track progress and uncover hidden issues.

Replace Blame with Curiosity

Use blameless retrospectives, post-mortems, and root cause analyses to transform failures into learning opportunities. Instead of asking “Who is at fault?” ask “What can we learn?” This shift in language and mindset is supported by PMBOK and ISO 31000, which encourage continuous improvement and knowledge sharing.

Empower Speaking Up—Safely

Create clear, confidential pathways for reporting concerns about risks or unethical behaviour. Train team members in assertive communication and active listening. Hold regular risk workshops, as recommended by ISO 31000, to normalize open discussion about uncertainties and potential threats.

Address Toxic Stakeholders Proactively

Equip the team with conflict resolution skills and clear escalation processes. Engage leaders and HR when necessary to address toxic behaviours. Be transparent about boundaries and team values, making it clear that toxic conduct will not be tolerated, in line with the PMI’s fairness and respect principles.

Align with Global Standards

Leverage frameworks like ISO 31000 (Risk Management), the PMBOK Guide, and the Agile Practice Guide to ensure that team practices align with international best practices for ethics, risk, and stakeholder management.

The Bottom Line

High-performing Agile teams do not emerge by accident. They are intentionally built on a foundation of psychological safety and strong ethical values. Respectful treatment, learning from failure, open communication about risks, and effective handling of toxic stakeholders are not just “nice-to-haves”—they are essential components of sustainable project success.

By embedding the PMI’s ethical principles and utilizing proven standards such as ISO 31000, organizations create environments where teams can thrive, innovate, and deliver lasting value.

Questions for Readers

1. How does your organisation and the senior management actively foster psychological safety and ethical behaviour?
2. What strategies have worked (or failed) when addressing blame cultures or toxic stakeholders in your experience?
3. In what ways can Agile teams better align their practices with established ethical and risk management standards?

Introduction

Like Agile, Artificial Intelligence (AI) is no longer seen as a concept limited to software development. Artificial Intelligence has become a defining force in product innovation across industries. As Agile delivery cycles accelerate the introduction of AI-powered features, organizations face a critical question: Can Agile teams govern AI risks effectively within short delivery cycles? The challenges are complex, touching on bias, explainability, accountability, and human oversight. As this debate takes centre stage in many professional forums, references such as the PMI Code of Ethics and Professional Conduct, the Agile Practice Guide, ISO 31000, and the PMBOK provide valuable perspectives on delivering responsible AI products.

This blog post aims to spark thoughtful discussion and practical action on one of today’s most critical technology challenges.

Challenges

Bias in Machine Learning Models

AI models are only as fair as the data and assumptions they are built on. Biases—historical, societal, or technical—can be inadvertently embedded in models, leading to unfair or discriminatory outcomes. Ensuring fairness is not a one-off task; it requires continuous attention to data quality, model design, and real-world impacts. However, Agile sprints prioritize delivering working increments rapidly, often leaving insufficient time for comprehensive bias audits or fairness tests. Adaptive systems require continuous learning and adjustment, but Agile teams may lack the bandwidth for deep dives into bias within each sprint.

Explainability Versus Innovation

AI’s power often stems from complex, opaque algorithms—especially deep learning models. While these models can drive rapid innovation, they are notoriously difficult to explain. The Agile Practice Guide encourages iteration and experimentation, but when stakeholders demand clarity on how AI makes decisions, Agile teams can struggle to balance transparency with speed. This tension is especially acute in regulated industries, where explainability is not just desirable but often mandatory. The PMI Code of Ethics underscores responsibility and honesty, making it ethically necessary to provide understandable explanations for AI-driven outcomes.

Accountability for AI Decisions

When an AI system makes a decision—such as denying a loan or flagging fraudulent activity—who is accountable? Agile frameworks support empowered, cross-functional teams, but the distributed nature of responsibility can blur lines of ownership. ISO 31000 and PMBOK emphasize the importance of risk management and clear accountability, yet Agile teams may focus on delivering features rather than establishing structures for post-release monitoring or escalation. The rush to “get to done” can sideline the deeper question of who answers for AI’s impact in the wild.

Human Oversight Requirements

The need for human-in-the-loop processes is well-documented, particularly for high-stakes AI applications. However, Agile’s emphasis on automation and continuous delivery may inadvertently reduce opportunities for meaningful human review. Everyone agrees on the importance of oversight to catch errors, biases, or unintended consequences before they affect users. Yet, as teams deliver features within a sprint, the time for thorough, cross-disciplinary review is often squeezed, creating risks that may not emerge until after deployment.

Recommendations for Agile Teams

Integrate Risk Management Early and Often:

Reference ISO 31000 and PMBOK to embed risk assessments into backlog refinement and sprint planning. Make risk mitigation a shared responsibility across roles.

Allocate Dedicated Time for Ethical Evaluation:

Ensure each sprint includes scheduled activities for reviewing fairness, bias, and explainability. Use checklists inspired by the PMI Code of Ethics to guide discussions.

Foster Multidisciplinary Collaboration:

Involve ethicists, domain experts, and impacted stakeholders in sprint reviews and retrospectives. Their perspectives can surface risks overlooked by developers alone.

Document Decision-Making Processes:

Maintain transparent records of design choices, especially around model selection, data sources, and trade-offs between explainability and performance. This supports accountability and future audits.

Implement Continuous Monitoring:

Don’t stop at deployment. Set up post-release reviews and monitoring to catch biases, errors, or harmful impacts that emerge in production.

Empower Human Oversight:

Build mechanisms for humans to intervene or override AI decisions, especially in critical contexts. Ensure these processes are well-communicated and accessible.

The Bottom Line

AI’s promise, opportunities, and risks are magnified by the speed of Agile delivery. While Agile teams are well-positioned to respond to change and incorporate feedback, governing AI risks demands intentional, systemic approaches that extend beyond the sprint. By weaving ethical considerations into every stage, teams can deliver AI-powered products responsibly, even under tight timelines. The challenge is ongoing, but the path forward is clear: ethics and agility must go hand in hand.

Questions for reflection:

1. How does your team address ethical risks in AI projects within short delivery cycles?
2. Have you encountered situations where speed conflicted with fairness or transparency? How did you resolve the tension?
3. What additional practices or frameworks would you recommend for Agile teams delivering AI features?

Introduction

In the last couple of decades, Agile frameworks have changed the way organisations deliver products and services, bringing a new perspective to the lean focus on maximizing customer value. In theory, this focus ensures that teams build what matters most to those who pay for, use, or depend on a product. But as technology pervades more aspects of daily life, a pressing ethical question emerges: Should teams optimize only for customer value? When the needs and desires of customers conflict with the well-being of employees, communities, or society at large, how should teams respond? And who gets to decide what constitutes ‘value’?

The Ethical Challenges

Defining Value: More Than Just the Customer

Frameworks like Scrum emphasize delivering customer value above all else. Paraphrasing Albert Einstein, as project managers, we should focus not on achieving financial success but on delivering value to society. “Be creative, but make sure that what you create is not a curse for mankind”. Customer value is not always synonymous with social good. In some cases, optimizing for one group can actively harm another.

When Value Delivery Harms the Public Good

Several real-world examples illustrate how this tension plays out:

• Surveillance Features: A government client requests capabilities for tracking citizens in the name of security. While this delivers customer value, it raises serious privacy and human rights concerns.
• Engagement and Addictive Design: Product owners ask for features that increase user engagement—sometimes by encouraging addictive behaviours. While this boosts KPIs, it may harm users’ mental health.
• Cost-Saving Initiatives: Organizations may request automation or layoffs to save costs, delivering value to the business but negatively impacting employee livelihoods.

Who Decides What Value Is?

The PMI Code of Ethics and Professional Conduct urges practitioners to balance responsibility to clients with responsibility to the public. Agile frameworks often leave the definition of value to the “customer” or product owner, but this approach can ignore wider consequences. Agility must go together with adaptability and ethical awareness, especially in complex, interconnected environments.

Ethical Considerations vs. Customer Requirements

Should ethical considerations outrank customer requirements? According to the PMBOK Guide and Risk Management standard ISO 31000, risks to stakeholders—including the public—must be managed alongside project objectives. The Agile Practice Guide recommends that teams “consider the impact of decisions on all affected parties,” not just end users or paying customers.

Recommendations

Broaden the Definition of Value:

• Teams should actively seek input from stakeholders beyond the customer: employees, users, regulators, and the public.
• Use stakeholder mapping to identify who is affected by product decisions.

Build Ethics into Agile Processes:

• Incorporate ethical checkpoints into backlog refinement, sprint reviews, and retrospectives.
• Use models like PMI’s Code of Ethics as a framework for decision-making.

Empower Team Members to Raise Concerns:

• Create a culture where team members can voice ethical concerns without fear of reprisal.
• Leverage the wisdom of diverse team members to identify risks that may not be obvious.

Make Ethical Trade-offs Explicit:

• When faced with conflicting values, document the trade-offs and rationale behind decisions.
• Use tools such as impact mapping and risk registers to make these trade-offs visible.

Engage in Ongoing Learning:

• Stay informed about evolving norms and regulations (e.g., data privacy laws, labour standards).
• Learn from case studies on professional forums, research sites and guidance from industry leaders.

The Bottom Line

Delivering customer value is a core tenet of Agile and project management frameworks, but it must not be pursued in isolation. Practitioners are increasingly called to weigh the interests of customers against the broader public good. As the PMI Code of Ethics emphasizes, our duty is to act responsibly, respect the dignity of those affected, and ensure our actions do not cause harm—even when it means saying “no” to a customer requirement. Ultimately, the most sustainable value is that which benefits everyone: the customer, the team, and society at large.

Questions for reflection

1. How should a team balance customer value and public good when they come into conflict?
2. Who should define what counts as “value” in your projects?
3. Can you recall a situation where delivering customer value had unintended negative consequences? What would you do differently?

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

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

Product 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

1. How does your project team/organization define “value”—and who gets to decide?
2. Can you recall a time when delivering customer value conflicted with broader stakeholder interests? What was the impact?
3. What practices could your Agile team adopt to better integrate ethical and stakeholder concerns into product decisions?

Introduction

Nowadays, Agile delivery is embraced by many organisations, attracted by the promise of delivering more with fewer resources. Senior management expects that project and product teams will deliver value fast, experiment early, and release software continuously. Agile frameworks changed how products are built, favouring short cycles and iterative progress over lengthy planning. However, with this acceleration comes a challenging debate: does the pursuit of speed undermine ethical responsibility? As teams race to meet sprint goals and ship new features, will other considerations—like user privacy, safety, accessibility, and broader societal impact—be sidelined?

The Project Management Institute (PMI) Code of Ethics and Professional Conduct asks practitioners to uphold integrity, responsibility, and respect. Yet, Agile’s “fail fast” ethos can come into tension with these values, especially when the effects of rapid releases are not fully understood. This blog post explores this complex balance and examines what it means to be both fast and ethical in modern software delivery.

Challenges

The Allure of Speed

Agile’s promise is seductive: quicker feedback, faster releases, happier customers. Teams are expected, sometimes incentivized, to get features into users’ hands as soon as possible, learn from real-world data, and iterate. This rapid cadence is essential in competitive markets, but it can create pressure to cut corners—sometimes at the expense of thorough validation or ethical review.

Unintended Consequences

A classic example is the release of AI-powered products. In the drive to “gather user feedback,” features may go live before the team fully understands their implications. An AI algorithm, for instance, might unintentionally introduce bias, disproportionately affecting certain customer groups. Such incidents are not rare; sometimes rapid deployment led to negative social impacts. The risk is amplified when teams lack diverse perspectives or fail to anticipate how their creations will be used (or misused).

Ambiguity in Risk Assessment

How much validation is enough before release? Standards such as ISO 31000 for risk management and guidance from PMBOK suggest systematic analysis, but Agile teams often struggle to balance this with their need for speed. The “definition of done” may overlook ethical checks, focusing instead on functional completeness and passing tests. This gap can result in features that work as intended but cause harm in ways the team did not predict.

The Ethics of Experimentation

Agile champions experimentation and learning from failure. But when users are part of live experiments, ethical questions arise: Is it acceptable to “fail fast” if it means real people might suffer negative effects? The PMI Code of Ethics stresses responsibility—to users, to society, and to the profession. Ron Jeffries, one of the original Agile Manifesto authors, has cautioned that “doing the right thing” must not be sacrificed for speed.

Recommendations

Embed Ethics in the Definition of Done

Update your team’s “definition of done” to include ethical review checkpoints. This could mean assessing for bias, privacy risks, or accessibility at the end of each sprint. Make these standards explicit and non-negotiable, in line with PMI’s focus on responsibility and respect.

Involve Diverse Stakeholders

Actively seek out perspectives from users, subject matter experts, and underrepresented groups. Agile practitioners advocate for inclusive design and decision-making processes. Broader participation helps teams anticipate unintended consequences and design safer, fairer products.

Apply Structured Risk Management

Leverage risk management frameworks like ISO 31000, PMI’s Project Risk Management standard, and PMBOK’s risk-related processes. Before releasing a feature, conduct a formal risk assessment: What could go wrong? Who might be harmed? How likely are these outcomes? Document risks and mitigation plans and revisit them as the product evolves.

Adopt Guardrails for Experimentation

Define clear boundaries for “fail fast” experiments. For example, restrict potentially harmful changes to limited user segments or non-production environments. Ensure informed consent when experimenting with real users, echoing ethical research practices.

Foster a Culture of Responsibility

Promote open discussion of ethical dilemmas within your team. Create safe spaces for raising concerns about speed versus responsibility. As the Agile Practice Guide notes, psychological safety enables transparency and continuous improvement—not just in delivery, but in decision-making.

Continuous Learning and Improvement

After release, monitor for negative outcomes and respond quickly. Encourage feedback from all stakeholders. Use retrospectives not only to improve process efficiency, but to question whether ethical standards were met.

The Bottom Line

Speed is a hallmark of Agile, but it must not come at the expense of ethical responsibility. The best teams deliver value quickly while upholding the highest standards of integrity, respect, and care for their users and society. By embedding ethical reviews into workflows, involving diverse voices, and applying structured risk management, organizations can harness the power of Agile without losing sight of their professional and societal duty.

Ultimately, the question is not whether to choose speed or ethics—but how to achieve both. True Agility means being responsive not just to market demands, but to the broader consequences of our work. Responsible delivery is the only way to build trust and create lasting value.

Questions for Readers

1. How does your team balance rapid delivery with ethical responsibility?
2. Have you ever faced a situation where speed conflicted with your professional values?
3. What practices have you found effective in identifying and mitigating ethical risks in Agile projects?