The Agile Enterprise

Introduction

Decades from the first attempts to make the computer ‘think, Artificial Intelligence (AI) is rapidly transforming industries, reshaping the way organizations deliver value and interact with customers. As AI becomes more ubiquitous, ethical considerations such as bias, privacy, fairness, and transparency have come to the forefront. Delivering ethically sound AI products is not just a technical challenge—it’s a governance imperative. When combined with Agile delivery methodologies, which emphasize speed, adaptability, and incremental value, there arises a critical need to ensure that rapid innovation does not compromise ethical standards. This blog explores how organizations can harmonize the principles of AI Ethics with Agile delivery.

Challenges

Managing Bias in AI Products

Bias in AI can arise from skewed data, flawed algorithms, or unconscious human prejudices. Agile’s focus on rapid iteration can inadvertently perpetuate bias if ethical checks are overlooked in pursuit of speed. The PMI Code of Ethics stresses responsibility—AI teams must proactively identify, evaluate, and mitigate bias at every stage, ensuring outcomes are just and equitable.

Preserving Privacy

AI systems often process vast amounts of sensitive data. The Agile value of “working software over comprehensive documentation” can tempt teams to deprioritize robust privacy controls for the sake of fast releases. However, PMBOK emphasizes the importance of balancing stakeholder needs and adhering to legal and regulatory requirements. Privacy must be designed into AI solutions from the outset, with clear guardrails and regular audits.

Ensuring Fairness and Transparency

Fairness and transparency are foundational to public trust in AI. Agile’s principle of “customer collaboration over contract negotiation” encourages engagement, but frequent releases can leave little time for transparent communication about AI decision-making. The Manifesto for Enterprise Agility calls for organizations to be both fast and fair, advocating for clear, accessible documentation and open channels for stakeholder feedback.

Ethical Oversight Amid Rapid Change

Agile teams thrive on embracing change, but shifting priorities and evolving requirements can lead to ethical “drift.” The PMI Code of Ethics and PMBOK highlight the need for integrity and accountability, emphasizing that ethical standards must not be sacrificed for speed. Continuous delivery pipelines must include ethical review gates and mechanisms for raising concerns without fear of reprisal.

Recommendations

Embed Ethics into Agile Ceremonies

Integrate ethical checklists and discussions into Agile rituals such as sprint planning and retrospectives. Make ethics a standing agenda item, ensuring ongoing vigilance.

Diverse, Cross-Functional Teams

Build teams that reflect a variety of backgrounds, perspectives, and expertise. Diversity is a key defence against bias and blind spots in both AI and Agile delivery.

Privacy by Design

Adopt the “privacy by design” principle by incorporating privacy impact assessments and data minimization strategies into the definition of “done.” Use Agile backlogs to prioritize privacy features and technical debt reduction.

Transparent Communication

Publish regular, plain-language updates on how AI systems make decisions, how data is used, and what measures are in place to ensure fairness. Use Agile’s iterative feedback loops to gather input and address concerns early and often.

Ethical Governance Structures

Establish governance bodies or ethics boards that work alongside Agile teams. These groups should be empowered to review, approve, or halt releases if ethical risks are detected. Anchor these structures in the PMI’s values of honesty, fairness, and respect.

Continuous Learning and Improvement

Leverage Agile’s focus on continuous improvement to regularly revisit ethical standards, update training, and incorporate lessons learned from real-world incidents. The Manifesto for Enterprise Agility and PMBOK both stress adaptability—apply this to ethics as well.

The Bottom Line

The intersection of AI Ethics and Agile delivery is one of the fastest-growing governance and risk domains in today’s technology landscape. By embedding ethical considerations into every stage of Agile development, organizations can deliver AI products that are not only innovative but also trustworthy and responsible. Drawing on the guiding principles of PMI, Agile, and enterprise agility, leaders can foster a culture where speed and ethics reinforce rather than undermine each other. The future of AI depends on our collective commitment to doing what’s right—even when it’s not the fastest path.

Question for Readers

How does your organization ensure that ethical standards are upheld during rapid Agile delivery of AI solutions?

Introduction

In the 21st-century dynamic and interconnected business environment, ethical conduct in project management is more critical than ever. Project managers are tasked with balancing stakeholder interests, meeting tight deadlines, and delivering value, all while upholding the highest standards of integrity and professionalism. The PMI Code of Ethics and Professional Conduct provide guardrails to manage core ethical challenges and provide frameworks for navigating complex decision-making. This blog post explores the ethical landscape of project management, examines common challenges, and offers practical recommendations for professionals seeking to foster ethical cultures within their organizations.

Challenges

Conflicting Stakeholder Interests

A project manager often faces situations where stakeholder interests and goals conflict. For example, clients may push for rapid delivery, while team members require more time for quality work. The PMI Code of Ethics emphasizes fairness and respect for all parties, but real-world pressures can make it difficult to balance these interests.

Pressure to Compromise Standards

Tight deadlines and budget constraints can tempt professionals to cut corners or overlook issues. Ron Jeffries, a co-creator of Extreme Programming, notes that “the pressure to deliver can lead to short-term decisions that undermine long-term value.” Ethical lapses often occur when organizational culture prioritizes results over process.

Ambiguity in Ethical Guidelines

While codes of conduct provide general principles, project managers may encounter situations not explicitly addressed by existing frameworks. For example, there is ambiguity in managing intellectual property when using Artificial Intelligence, collaborating with third-party vendors, or open-source communities.

Cultural and Global Differences

Ethical standards may vary across regions and cultures. A practice considered acceptable in one country could be viewed as unethical elsewhere. The PMI Code of Ethics encourages cultural awareness and sensitivity, but navigating these differences remains a challenge for global teams.

Transparency and Communication

A lack of transparency, whether intentional or accidental, can erode trust within teams and with stakeholders. Ineffective communication is a leading cause of ethical breaches in project environments.

Recommendations

Embrace the PMI Code of Ethics and Professional Conduct

The PMI Code of Ethics and Professional Conduct provides a robust framework for ethical decision-making. Project managers should familiarize themselves with its four core values: responsibility, respect, fairness, and honesty. Regular training and open discussion of these principles can reinforce their importance across teams.

Foster an Ethical Culture

Leaders set the tone for organizational ethics. Encourage an environment where team members feel empowered to raise concerns without fear of retaliation. As Ron Jeffries advocates, “build systems that make it easy to do the right thing and hard to do the wrong thing.”

Provide Clear Guidelines and Support

Ambiguity breeds uncertainty. Develop clear policies for handling common ethical dilemmas, such as conflicts of interest, confidentiality, and intellectual property rights. Leverage resources such as discussion forums, webinars, articles, and participation in communities of practice to stay updated on best practices.

Prioritize Transparent Communication

Promote open and honest communication at every project stage. Transparency builds trust and helps ensure that all stakeholders have access to the information they need to make informed decisions.

Respect Cultural Differences

When managing international projects, invest in cultural competence training and adapt practices to accommodate diverse perspectives. The PMI Code of Ethics encourages respect for cultural norms, which is essential for effective global collaboration.

The Bottom Line

Ethical conduct is not just another academic requirement—it’s the foundation of successful project management. By adhering to established codes of conduct, fostering ethical cultures, and staying informed of emerging challenges, project managers can navigate complexity with confidence and integrity. The journey toward ethical excellence is ongoing, requiring vigilance, education, and a commitment to doing what’s right, even when it’s not easy.

Question for Readers: What strategies would you recommend for promoting ethical conduct in project environments?

In an increasingly interconnected world, international projects—whether in business, development, humanitarian aid, or research—bring together diverse teams from varied cultural, religious, and legal backgrounds. Success in these environments depends not just on technical competence or financial resources, but on navigating the complex terrain where personal beliefs, ethics, morals, and law intersect. Understanding the distinctions between these four domains is not merely academic; it is essential for effective collaboration, risk management, and sustainable outcomes.

Defining the Terms

I believe that before exploring their relevance to international projects, we must clarify what each term represents:

Personal beliefs are individual convictions—religious, philosophical, or cultural—that shape how a person sees the world. These are subjective, often deeply held, and vary dramatically across individuals, even within the same community. One team member may believe that Sunday must be reserved for rest; another may view hierarchical deference as non-negotiable; a third may consider certain foods spiritually polluting.

Morals are society's shared understandings of right and wrong, typically rooted in cultural or religious traditions. Moral codes tell a community what constitutes virtuous behaviour—honesty, loyalty, respect for elders, or modesty in dress. While morals provide social cohesion, they are not universal; what one culture considers moral duty, another may view as optional or even harmful.

Ethics are systematic frameworks for determining right conduct, often developed through rational deliberation rather than tradition. Professional ethics—such as engineering codes, medical ethics, or research integrity guidelines—provide structured principles (beneficence, non-maleficence, autonomy, justice) that can be applied across cultural contexts. Ethics attempt to be universalizable, seeking principles that reasonable people from different backgrounds could accept.

Law comprises the formal rules enforced by states or international bodies, backed by sanctions. Legal systems vary by jurisdiction, and international projects must navigate multiple overlapping legal frameworks—local regulations, national laws, international treaties, and institutional policies.

Why the Distinction Matters

Avoiding the Trap of Ethnocentrism

International projects often fail when participants unconsciously impose their own moral or belief systems as universal standards. A Western manager might view nepotism as corruption, while in some societies, hiring family members is a moral obligation of trust and mutual support. Without distinguishing between "this violates my personal morals" and "this violates professional ethics or local law," the team may fracture over perceived ethical lapses that are actually cultural differences.

Consider a project in a geographical zone where gift-giving to officials is traditional. A team member from a culture where such gifts constitute bribery may experience moral outrage. However, if the practice is legal locally and does not violate international anti-corruption conventions the project has adopted, the issue is one of conflicting morals, not necessarily ethics or law. The professional response is not to condemn, but to ensure the project's ethical guidelines (transparency, proportionality, legitimate purpose) are maintained while respecting local custom.

Managing Legal Pluralism

International projects operate under complex legal landscapes. A construction project might face environmental regulations in the host country, labour standards from the funding institution's country and international conventions on indigenous rights. These legal layers may conflict although local law might permit practices that international law prohibits, or vice versa.

Ethics provides the bridge. When laws conflict, professional ethics—such as the precautionary principle in environmental ethics or the duty to protect vulnerable populations—help teams determine which legal standard to prioritize. Without clear ethical reasoning, projects either default to the most permissive legal standard (risking reputation and harm) or the most restrictive (risking impracticality and local resentment).

Protecting Individual Conscience Without Paralysing Projects

Team members have inalienable rights to their personal beliefs. A religiously devout team member may need prayer times; a committed vegan may object to animal testing; a pacifist may refuse to work on military components. These are legitimate personal boundaries.

However, projects require coherent ethical standards. The distinction allows us to accommodate personal beliefs where possible (providing prayer times and spaces, reassigning roles) while maintaining that project ethics are non-negotiable. A researcher cannot refuse to obtain informed consent because they personally believe authorities know best—that would violate research ethics. But they can request not to be assigned to protocols involving procedures they find personally objectionable, provided alternatives exist.

Building Trust Across Difference

Trust is the currency of international collaboration. When teams conflate personal beliefs with professional ethics, they signal that only those who share their worldview are trustworthy. When they treat local laws as mere obstacles to be circumvented, they signal disrespect for host societies.

By explicitly distinguishing these domains, projects create space for genuine pluralism. Team members can say: "I personally believe X, but I recognize that our shared ethical framework requires Y, and I will uphold Y professionally." This stance—what philosopher John Rawls called "reasonable pluralism"—allows deep cooperation without demanding homogeneity.

Practical Applications

Developing Project-Specific Ethical Frameworks

Effective international projects establish ethical guidelines through inclusive deliberation. Rather than importing one culture's morals, teams should ask: What principles can we all accept as necessary for this project's integrity and the welfare of those affected?

For example, a health intervention project might establish that "do no harm" and "community participation" are non-negotiable ethical principles, while remaining neutral on specific moral questions like contraception access, provided local law permits both options. This allows team members with varying personal beliefs to participate, united by shared professional ethics.

Training for Ethical Reasoning

Teams need training not just in compliance (what does the law require?) but in ethical reasoning (how do we navigate when values conflict?). Case-based learning—exploring realistic scenarios where personal beliefs, morals, ethics, and law pull in different directions—builds capacity for nuanced judgment.

Institutionalizing Review Mechanisms

International projects should establish ethics review boards or ombudspersons with cross-cultural competence. These bodies can adjudicate when personal belief accommodations conflict with project needs, or when local practices raise ethical concerns. Their authority derives from explicit ethical frameworks, not the preferences of powerful stakeholders.

Documentation and Transparency

When projects make decisions that involve balancing these domains, they should document their reasoning. If a project determines that following stricter environmental ethics requires exceeding local legal minimums, this should be transparent to stakeholders. Such transparency builds legitimacy and enables learning.

Case Study: The Extractive Industries

Consider international mining projects in developing countries. These projects often face:

• Personal beliefs: Individual engineers or geologists may hold religious convictions about stewardship of creation, or personal commitments to indigenous rights activism.
• Local morals: Communities may view land as ancestral heritage with spiritual significance, not mere commodity. Traditional leaders may see consultation as requiring specific ritual protocols.
• Professional ethics: Engineering codes require safety and environmental protection; international frameworks like the Extractive Industries Transparency Initiative demand revenue disclosure.
• Law: Host country mining codes, international human rights law, home country anti-bribery statutes, and contractual obligations all apply.

Projects that collapse these categories fail spectacularly. Those that treat local land spiritual beliefs as mere "superstition" to be overcome by legal property rights spark conflict. Those that allow personal activist convictions to override safety protocols endanger workers. Those that follow only local law when it permits unsafe tailings dams violate professional ethics and eventually face legal liability elsewhere.

Successful projects distinguish carefully: They respect local moral frameworks through culturally appropriate consultation (ethics of respect for persons). They uphold professional safety and environmental standards regardless of local legal minima (ethics of non-maleficence). They accommodate personal beliefs through role assignment where possible. And they maintain strict legal compliance while recognizing that law sets floors, not ceilings, for ethical behaviour.

Conclusion

The distinction between personal beliefs, morals, ethics, and law is not an invitation to moral relativism or unprincipled pragmatism. Rather, it is a framework for principled engagement across difference. International projects that master this distinction gain resilience: they can accommodate diversity without fragmenting, uphold standards without imperialism, and navigate complexity with clarity.

In a world where projects increasingly span borders and cultures, this capacity is not optional. It is the foundation of sustainable, legitimate, and genuinely collaborative international work. The question is not whether our projects will engage with these domains, but whether we will do so consciously and skilfully—or stumble blindly into conflict and failure.

Introduction

In the 21st-century business environment of continuous and disruptive change, project delivery, including project management, can’t escape from the buzzwords, and we can see Agile frameworks and established practices often travelling far from their origins. Two of the most influential concepts—Agile and Kanban—have been widely adopted, adapted, and, at times, misunderstood outside their intended contexts. This blog post explores the ethical implications and risks of using the term “Agile Manifesto” as a generic label for Agility and avoiding recognising Kanban as an over 50 years old Lean Six Sigma practice, rebranded the knowledge work implementation as “Lean Kanban” without acknowledging their roots. We’ll reflect on these issues through the lens of PMI’s Code of Ethics and Professional Conduct, the Agile Practice Guide (2026), the Agile Manufacturing Forum (1991), Manifesto for Enterprise Agility (2026), and the original Manifesto for Agile Software Development (2001) itself.

Challenges

Misrepresentation of Origins and Intent

The Manifesto for Agile Software Development was crafted by software developers for software development. Its values and principles are rooted in the challenges and culture of that specific discipline. When organizations refer to “the Agile Manifesto” as a universal principle for all types of work, they risk distorting its intent, potentially violating PMI’s ethical value of responsibility—which demands honesty and accuracy in representation.

Similarly, “Kanban” in its pure form is a Lean Six Sigma manufacturing tool, while “Lean Kanban” is a knowledge work adaptation. Treating “Lean Kanban” as something else than Kanban can mislead stakeholders. The term Lean in front of an established practice potentially violating the ethical value of respect by failing to honour the history and contributions of the practitioners who developed these adaptations

Erosion of Professional Integrity

The PMI Code of Ethics emphasizes fairness and honesty. Presenting the Manifesto for Agile Software Development or Lean Kanban as universal tools for any context undermines professional integrity. It suggests a one-size-fits-all mentality that can lead to failed implementations, disenfranchisement of teams, and a loss of trust.

The Agile Practice Guide and PMBOK both stress tailoring methods to context. Ignoring the original intent of these frameworks can cause project managers to violate the ethical value of responsibility—by not exercising due care in their professional duties.

Risks of Oversimplification

When “Agile” or “Kanban” are thrown around as buzzwords, organizations may ignore the need for real cultural change and the discipline required for successful implementation. Scientific articles published in the 1990s by the Agile Manufacturing Forum, the Manifesto for Enterprise Agility, and PMBOK indicate that successful Agile transformation requires deep understanding, respect for context, and continuous learning. Oversimplification can result in failed transformations, wasted resources, and diminished value delivery—contradicting the ethical value of responsibility and respect for stakeholders.

Impact on Stakeholders

The PMI Code of Ethics underscores the importance of respect and fairness toward all stakeholders. By misapplying frameworks, organizations risk creating confusion and setting unrealistic expectations among teams, leaders, and customers. This can lead to disengagement, frustration, and even project failure.

Recommendations

Honor the Origins

Acknowledge that the Manifesto for Agile Software Development was written by and for software developers. When applying Agile principles outside software, draw from sources such as the Manifesto for Enterprise Agility, which intentionally adapts Agile thinking to broader contexts. Similarly, acknowledge the roots of Lean Kanban (as applied in knowledge work) in the original Kanban in manufacturing.

Tailor with Integrity

Follow the guidance of the PMBOK and Agile Practice Guide: tailor your approach to fit the context. This means being honest about the limitations and applicability of each framework. When communicating with stakeholders, clarify what version or adaptation of Agile or Kanban you are using—and why.

Educate Stakeholders

Invest time in stakeholder education. Ensure teams, leaders, and clients understand the source and intent of the practices being used. This supports responsibility and respect, and aligns with the PMI value of serving the public interest.

Reflect on Ethical Values

Use PMI’s Code of Ethics and Professional Conduct as a compass. Ask yourself: Are you being honest about what you are implementing? Are you respecting the contributions of those who developed these frameworks? Are you treating stakeholders fairly by setting realistic expectations?

Continuous Improvement

Adopt a mindset of learning and humility. Just as the Manifesto for Agile Software Development calls for continuous reflection, so too should organizations regularly review their practices in light of ethical standards and evolving contexts.

The Bottom Line

Using the Manifesto for Agile Software Development (aka “Agile Manifesto”) as a blanket term for all things Agile or treating Lean Kanban as something other than the Lean Six Sigma practice of kanban risks misrepresentation, confusion, and ethical lapses. By honouring the origins, tailoring with integrity, educating stakeholders, and reflecting on ethical values, project managers and organizations can uphold the ethical values of responsibility, respect, fairness, and honesty. This not only avoids ethical pitfalls, but also increases the likelihood of real, sustainable transformation and value delivery.

Question for Readers: Have you experienced challenges when Agile or Kanban were applied outside their original context?

Introduction

Agile has reached maturity in many organisations, and the success of Artificial Intelligence (AI) makes its use unavoidable for organisations to evaluate and enhance the performance of Agile teams. While AI promises a data-driven, objective lens for analysing team dynamics, productivity, and outcomes, its application to evaluate project team performance raises profound ethical questions—particularly when viewed through the lens of the Project Management Institute’s (PMI) Code of Ethics and Professional Conduct. This blog post explores the ethical implications of using AI to compare Agile team performance, guided by PMI’s values of responsibility, respect, fairness, and honesty.

Challenges

Responsibility: Ensuring Informed and Accountable Use

According to the PMI Code of Ethics, project managers are responsible for the decisions they make and their impact on stakeholders. The use of AI introduces a new layer of responsibility, as the algorithms and models deployed can influence critical business and technical decisions, team morale, and individual careers. Without a clear understanding of how AI systems operate, there is a risk of delegating accountability to technology, thereby abdicating human responsibility. Furthermore, Agile teams thrive on transparency and trust (Manifesto for Agile Software Development), and opaque AI models can undermine these foundational principles.

Respect: Preserving Dignity and Psychological Safety

The Agile Practice Guide and Manifesto for Enterprise Agility stress the importance of respect among team members. AI-driven comparisons risk reducing team members to data points, potentially diminishing their sense of value and psychological safety. This is especially concerning when performance metrics are derived from sources like code commits, velocity, or issue resolution rates, which may not capture the full scope of an individual’s or team’s contribution. Respecting people means recognizing their unique contexts, strengths, and the human factors that are not always quantifiable.

Fairness: Avoiding Bias and Ensuring Equity

PMI’s value of fairness calls for impartial and just decision-making. AI systems are only as unbiased as the data and assumptions upon which they are built. If training data reflects organizational biases or historic inequalities, AI may perpetuate or even exacerbate them. For example, if one team’s work is more client-facing and another’s more technical, or a team is developing new features while another is fixing defects, comparing them using the same metrics may yield unfair outcomes. The Manifesto for Agile Software Development emphasizes individuals and interactions over processes and tools, serving as a reminder that context matters—and fairness demands careful consideration of these differences.

Honesty: Transparency and Truthfulness in Reporting

Honesty, as defined by PMI, compels project managers to provide accurate and truthful information. The complexity of AI models can make it difficult to explain how conclusions are reached, leading to challenges in maintaining transparency. Agile values also highlight the importance of open communication and feedback loops. When AI-generated comparisons are presented without clear explanations, stakeholders may question their validity, eroding trust in both the technology and its advocates.

Recommendations

Human-Centric AI Design

AI tools should be designed to support, not replace, human judgment. Agile frameworks encourage continuous improvement, collaboration, and adaptation. In line with PMI’s ethical standards, organizations should ensure that AI complements human insight, enabling teams to learn and grow rather than simply ranking or scoring them.

Transparent Methodologies

Explainability is crucial. Both the PMI Code of Ethics and the Manifesto for Agile Software Development value transparency and trust. Organizations deploying AI to compare Agile teams must clearly communicate how data is collected, what metrics are used, and how results are interpreted. This fosters informed dialogue and minimizes misunderstandings.

Regular Bias Audits

Regularly audit AI systems for bias, in alignment with PMI’s fairness value. Engage diverse stakeholders—including team members—in the design and review of AI models. Use feedback to refine algorithms and ensure that they remain equitable and relevant.

Contextualized Metrics

Avoid one-size-fits-all comparisons. Agile teams operate in diverse environments, with varying goals, challenges, and customer needs. Tailor metrics to the context of each team, and supplement quantitative data with qualitative insights. This reflects the Manifesto for Agile Software Development's focus on individuals and interactions, ensuring a holistic view of performance.

Foster Psychological Safety

Use AI insights to support team development rather than to penalize. The Agile Practice Guide underscores the importance of psychological safety for learning and innovation. Frame AI-driven feedback as an opportunity for growth, not as a tool for surveillance or punitive action.

The Bottom Line

The integration of AI into Agile team performance comparison presents a unique set of ethical challenges. By grounding our approach in PMI’s values of responsibility, respect, fairness, and honesty—and by drawing on the wisdom of the Agile Practice Guide, Manifesto for Agile Software Development, Manifesto for Enterprise Agility, and PMBOK—we can harness the power of AI while upholding the highest ethical standards. Ultimately, the goal is not to let technology dictate our decisions, but to use it as a catalyst for deeper understanding, stronger teams, and more meaningful outcomes.

Question for Reflection: How can organizations ensure that AI-driven performance comparisons reinforce, rather than undermine, Agile and ethical values?