The Agile Enterprise

Although there is no Agile Coaching Code of Ethics, like PMI’s Code of Ethics and Professional Conduct, Agile coaching ethics relies on guidelines adapted from broader professional bodies and community-led initiatives. Some examples of codes and frameworks used by Agile coaches include:

The Agile Coaching Code of Ethical Conduct

(Developed by an open community initiative supported by Agile Alliance and Scrum.org)

This is the primary dedicated code of ethics specifically created for the Agile coaching discipline. It covers 9 core commitments:

1. Protecting Confidentiality, Intellectual Property, and Information Security: Protecting client data and properly attributing ideas.
2. Acting Within My Ability: Remaining transparent about qualifications and stepping aside when client needs exceed personal expertise.
3. Introspection and Continuing Professional Development: Engaging with mentors/peers and pursuing continuous learning.
4. Navigating Conflicts of Interest: Proactively declaring potential conflicts and ensuring decisions benefit the client over personal gain.
5. Ensuring Value in the Relationship: Preventing client dependency and continuously verifying that the coaching engagement adds tangible value.
6. Upholding Social Responsibility, Diversity, and Inclusion: Actively discouraging discrimination and elevating diverse perspectives.
7. Agreeing on Boundaries: Establishing agreed-upon scope without imposing personal preferences or violating Agile principles.
8. Managing Differences in Status and Power: Refraining from misusing influence, authority, or rank.
9. Responsibility to the Profession: Uplifting professional standards and addressing unethical behaviour in the community.

Unlike PMI’s Code and other codes developed by professional bodies, such has Mechanical Engineering, Construction, Electrical Engineering or Medical Association, this code is not structured on certain values, like Responsibility, Respect, Fairness and Honesty, nor has specific mandatory and aspirational standards.

Scrum Alliance Code of Ethics

(Mandated for Scrum Alliance certified practitioners, including Certified Agile Coaches / CEC / CTC)

The Scrum Alliance Code of Ethics governs professional behaviour across five main areas:

• Representation: Truthfulness regarding credentials, background, and capabilities.
• Professionalism: Maintaining courtesy, respecting others, avoiding harassment/discrimination, and upholding hate speech policies.
• Professional Responsibility: Managing conflicts of interest, taking accountability for mistakes, and avoiding safety risks.
• Compliance with Scrum Alliance Policies: Respecting intellectual property and mark usage guidelines.
• Pledge of Ethics & Scrum Values: Aligning behaviour with the 5 Scrum Values (Focus, Courage, Openness, Respect, Commitment).

More ethics-oriented around Scrum values, the code does not have specific mandatory and aspirational standards. Like the Agile Alliance, the Scrum Alliance doesn’t supplement the Code with a framework for investigating and resolving ethics complaints related to violations of the code of ethics there is no body that can order disciplinary or remedial actions.

Complementary & Adjacent Codes

• International Coaching Federation (ICF) Code of Ethics, structured into 4 pillars:

Responsibility to Clients: Confidentiality, clear contracts, avoiding power imbalances, and managing client conflicts.

Responsibility to Practice and Performance: Maintaining personal boundaries, ongoing self-development, and ethical awareness.

Responsibility to Professionalism: Accurate representation of coaching qualifications and respecting intellectual property.

Responsibility to Society: Promoting equality, safety, and social well-being.

• International Association of Facilitators (IAF) Code of Ethics: Followed by Agile coaches emphasizing group facilitation stance (focusing on neutrality, inclusive participation, and group autonomy).
• European Mentoring and Coaching Council (EMCC) Global Code of Ethics: Common among UK/European Agile coaches, focusing on professional competence, context awareness, and safety.

Scenarios:

Following are some scenarios to demonstrate how PMI’s Code of Ethics ethical values can be used by Agile Coaches;

Scenario 1: Handling "Off-the-Record" Leadership Information

• Ethical Principle - Responsibility: Protecting Confidentiality & Information Security
• The Situation: During a 1-on-1, a director confides to you that a major restructuring and layoff phase is coming in two months. Later that week, a team member asks you directly, "I heard rumours about layoffs—is our team safe? Should I be updating my resume?"
• In Practice:
• Unethical Approach: Confirming the rumour off-the-record or blabbing to build trust with team members.
• Ethical Approach: Protect confidentiality while maintaining trust. Explain that you cannot comment on organizational rumours but offer space to explore their immediate concerns and direct them to HR or official leadership channels for official updates.

Scenario 2: Knowing When to Say "I'm Out of My Depth"

• Ethical Principle – Honesty: Acting Within My Ability
• The Situation: An executive asks you to lead an enterprise-wide scaling transformation, including redesigning compensation structures and org design. You have strong team-level coaching experience, but zero experience with executive change management or compensation models.
• In Practice:
• Unethical Approach: Accepting the contract or assignment anyway for the prestige, higher pay, or career progression, hoping to "fake it till you make it."
• Ethical Approach: Be transparent about your current scope of expertise. Offer to help co-coach alongside an enterprise specialist or advise the leadership team to bring in an experienced enterprise transformation consultant.

Scenario 3: Firing Yourself When Value Drops

• Ethical Principles - Honesty and Responsibility:Ensuring Value in the Relationship / Preventing Dependency
• The Situation: You have coached a department for 18 months. The teams are high-performing, self-organizing, and successfully resolving their own systemic blockers. However, management wants to keep you on a retainer indefinitely to "keep things smooth."
• In Practice:
• Unethical Approach: Staying on board, creating artificial problems to solve, or making yourself indispensable so the contract keeps rolling.
• Ethical Approach: Point out that the team has achieved self-sustainability. Recommend transitioning out of the daily coaching role, moving to an ad-hoc advisory check-in model, or wrapping up the engagement.

Scenario 4: The Boss Demands "Secret Performance Data"

• Ethical Principles – Respect and Fairness: Managing Differences in Status and Power / Protecting Confidentiality
• The Situation: A VP asks you, "I need you to tell me who the low performers are on Team X so I can decide on year-end bonuses. You observe their retrospectives every week."
• In Practice:
• Unethical Approach: Sharing individual observation notes or evaluating team members' personal contributions based on retrospective participation.
• Ethical Approach: Explain that retrospective observations and coaching interactions are safe, confidential spaces required for psychological safety. Offer instead to help leadership establish transparent, objective metrics for performance evaluating outside the coaching boundary.

Scenario 5: Managing Tool Vendor Kickbacks

• Ethical Principle – Responsibility and Honesty:Navigating Conflicts of Interest
• The Situation: An Agile tooling vendor offers you an affiliate commission or a free ticket to an international conference if you convince your current client company to adopt their enterprise software package.
• In Practice:
• Unethical Approach: Recommending the tool as the "best solution for the organization" without disclosing your financial incentive or alternative options.
• Ethical Approach: Disclose the potential conflict immediately to the client decision-makers. Remain objective by providing an unbiased evaluation of multiple tool options or step back from the selection committee altogether.

Scenario 6: Steering Clear of Dogma

• Ethical Principles – Responsibility, Honesty and Respect: Agreeing on Boundaries & Respecting Client Autonomy
• The Situation: You are a strict advocate for Scrum. A software engineering team at your client company is dealing with unpredictable operational incidents and wants to adopt Kanban.
• In Practice:
• Unethical Approach: Refusing to support them or insisting they stay with 2-week Scrum Sprints because "Kanban isn't really Agile."
• Ethical Approach: Put the client team's contextual needs over personal framework preferences. Help them design a flow-based Kanban system tailored to their operational reality, ensuring alignment with overall Agile principles.

Introduction

The phrase “Agile is a process” is a widespread misconception that has undermined countless organisational transformations. Starting with “We are implementing an Agile Methodology”, regardless of which Agile framework is referred to, is a mistake that can lead to failed Agile transformation. At its core, Agile is not a set of rigid steps but a mindset rooted in values such as learning quickly, delivering value early to customers, adapting to change, collaborating closely, and continuously improving. Misinterpreting Agile as merely a process, new titles or a set of ceremonies—like stand-ups, sprints, and retrospectives—can erode its ethical foundation and lead to failed transformations. This blog post analyses the ethical implications of this misconception.

Challenges

When organisations equate Agile with a process, they risk violating several ethical principles central to professional conduct. The PMI Code of Ethics emphasises responsibility, respect, fairness, and honesty—values that are compromised when Agile is reduced to a checklist of activities. For example, implementing ceremonies without embracing the underlying Agile mindset can foster environments where employees go through the motions, disengaged from genuine collaboration and continuous improvement. Ron Jeffries, one of the original signatories of the Agile Manifesto, has repeatedly stressed that the “heart of Agile” is about people, not processes and tools.

Failed Agile transformations often stem from superficial adoptions. By focusing solely on rituals, organisations may inadvertently create a culture of compliance rather than one of empowerment. This approach conflicts with the principle of respect, as outlined by PMI’s Code of Ethics, by treating team members as cogs in a machine rather than autonomous professionals capable of self-organisation and innovation.

Moreover, practitioners highlight the importance of adaptability and learning—core tenets of Agile. When these are ignored, organisations become less resilient and more likely to falter in the face of change. Risk management standards and frameworks, and all Agile frameworks advocate for adaptive approaches and stakeholder engagement, principles that are compromised when Agile is viewed as a static process.

Recommendations

To ethically implement Agile, organisations must shift their perspective from process to mindset. Here are several recommendations:

Cultivate an Agile Mindset:

• Emphasise values such as openness, courage, and respect. Encourage teams to question, learn, and adapt.
• Reference Ron Jeffries’ advice: Focus on communication, feedback, simplicity, and courage.

Prioritise People Over Process:

• Inspire trust by empowering teams to make decisions. The PMI Code of Ethics calls for treating individuals with dignity and fairness.
• Foster environments where psychological safety is paramount, supporting the Agile Practice Guide’s emphasis on collaboration.

Embrace Continuous Improvement:

1. Use retrospectives and feedback loops not as obligations, but as genuine opportunities for learning and adaptation.
2. Integrate principles from risk management standards and traditional project delivery approaches to manage risk and change proactively.
3. Align with Global Standards:
4. Use frameworks like ISO 31000 and PMBOK® to guide ethical decision-making and stakeholder management.
5. Ensure Agile practices are tailored to context rather than rigidly applied.
6. Educate and Coach:
7. Invest in Agile coaching that emphasises mindset and values, not just mechanics.
8. Leverage resources from PMI, Agile Alliance, and LinkedIn forums to support ongoing learning.

The Bottom Line

Viewing Agile as a process rather than a mindset is not simply a technical mistake—it is an ethical lapse. By prioritising ceremonies over values, organisations risk undermining trust, stifling innovation, and sacrificing long-term value for short-term compliance. Ethical Agile adoption demands a holistic approach grounded in professional values, global standards, and a relentless commitment to learning and adaptation. Only then can organizations realize the true promise of Agile: delivering value early to customers, responding to change, and fostering environments where collaboration and improvement are the norm.

Question for Readers:  What steps can leaders take to ensure Agile is implemented ethically and authentically in their organisations?

Introduction

Agile methodologies, inspired by the Manifesto for Agile Software Development, have revolutionized project management, strengthening adaptive planning and iterative delivery. One of the most recognized metrics in Agile is “velocity,” the sum of story points completed in a sprint. However, a persistent misconception lingers that velocity measures team productivity. Velocity, introduced by the Extreme Programming framework for software development, is a planning tool designed to help teams forecast future work—not a performance metric for comparing teams or individuals. Misusing velocity this way has significant ethical implications, leading to unfair evaluations, demotivation, and even manipulation of the very metric it seeks to leverage. This post explores the ethical dimensions of this misconception and provides actionable recommendations.

Challenges

The Relativity of Story Points

Story points are inherently subjective. They reflect a team’s unique understanding of effort, complexity, and risk. Context matters: what is a “5-point” story for one team may be a “2-point” story for another. The Agile Practice Guide and Ron Jeffries, the person credited with inventing story points, both highlight that teams develop their own baselines and estimation habits. Using velocity to compare teams disregards these differences, leading to unfair assessments.

Ethical Dilemmas in Misuse

The PMI Code of Ethics urges practitioners to act with honesty, responsibility, and respect. When organizations treat velocity as a productivity scorecard, they risk violating these principles. Teams might inflate story points or focus on quantity over quality to meet perceived performance expectations. This undermines transparency, distorts reporting, and creates a culture of fear or cynicism. Risk management practices include identifying behavioural risks—misapplied metrics are a prime example.

Value Delivery vs. Story Point Completion

PMBOK and Agile Practice Guide stress that real value lies in meeting customer needs, not just completing tasks. A team could have a lower velocity but consistently deliver features that delight users or resolve critical business challenges. Conversely, a high-velocity team might churn out less impactful work. Using velocity as a direct proxy for value delivery ignores the true purpose of Agile: maximizing stakeholder value.

Contextual Variability

External factors—team experience, domain knowledge, technical debt, stakeholder availability—affect how teams estimate and deliver work. Context and team maturity significantly shape estimation accuracy and throughput. Comparing velocity across teams without accounting for these factors leads to misleading conclusions and can erode trust in leadership.

Recommendations

Use Velocity for Planning, Not Judgement

Adopt velocity as it was intended: to help a team predict how much work they can take on in future sprints. Avoid using it as a key performance indicator for individuals or to compare teams. Encourage teams to focus on delivering value, not just increasing their story point totals.

Foster an Ethical Measurement Culture

The PMI Code of Ethics calls for fairness, openness, and respect. Leaders should educate stakeholders about the true purpose of velocity and champion its ethical use. Transparency is critical—explain how estimates are derived and why comparisons are invalid. Recognize and reward behaviours that support collaboration, learning, and value delivery.

Supplement with Qualitative Feedback

Combine quantitative metrics with qualitative insights: customer satisfaction, team morale, ability to respond to change, and delivery of business value. The Agile Practice Guide advocates a balanced view of performance. Use retrospectives to capture lessons learned and context behind the numbers.

Emphasize Continuous Improvement

Encourage teams to use velocity to reflect on their own processes and seek improvement—not to compete with or be judged against others. Support experimentation and learning. Make it safe for teams to be honest about challenges and impediments.

Tailor Metrics to Context

Follow PMBOK and Agile Practice Guide recommendations by adapting measurement frameworks to organizational needs and contexts. Avoid one-size-fits-all metrics. Instead, co-create success criteria with teams and stakeholders.

The Bottom Line

Treating velocity as a productivity metric is not only a technical error but also an ethical misstep. It undermines Agile values, creates perverse incentives, and risks team well-being. By following the spirit of the PMI Code of Ethics, insights from Agile pioneers like Ron Jeffries, and industry best practices, organizations can foster healthier, more effective teams. Velocity is a tool for planning—not a yardstick for productivity.

Question for Readers: How can leaders better model ethical use of Agile metrics in their teams?

Why Business Leaders Must Unlearn the Belief That AI Can Reliably Perform Knowledge Work at Human-Expert Levels Without Significant Human Oversight

Introduction

The history of artificial intelligence contains an important lesson that if organisations choose to ignore it could lead to significant damage. Neither of the first two AI winters occurred because AI was completely useless. Instead, both resulted from a gap between what AI could actually do and what influential stakeholders claimed it could do. In the 1970s, expectations around general problem-solving exceeded reality. During the late 1980s, expert systems were marketed as capable of replicating professional judgment through rules and logic, only to reveal fundamental limitations when exposed to real-world complexity. Dangerously, a similar misconception is emerging today: AI can reliably perform knowledge work at human-expert levels without significant human oversight. This belief is not merely a technical misunderstanding. It is an ethical issue involving responsibility, honesty, fairness, risk management, and professional accountability.

Ethical leadership requires truthful communication about capabilities and limitations rather than promoting unrealistic expectations. From an ethical perspective, the danger is clear. When organizations remove human oversight based on exaggerated assumptions about AI capability, they transfer risk to customers, employees, patients, investors, and society. This violates fundamental principles of professional conduct and risk management.

The issue is not whether AI is valuable. It clearly is. The issue is whether organizations are deploying AI responsibly and transparently, particularly in domains where errors can create significant harm.

Challenges

Confusing Fluency with Understanding

Like their grandmother Elisa, modern AI systems generate responses that appear intelligent, confident, and authoritative. However, convincing language is not the same as genuine understanding.

Ron Jeffries, one of the co-creators of Extreme Programming, has repeatedly warned about confusing visible outputs with actual value and understanding. Metrics, demonstrations, and impressive presentations can create an illusion of capability while masking underlying limitations.

Ethically, this creates a challenge for leaders. Employees and stakeholders often assume that articulate AI responses indicate expertise. AI systems can produce inaccurate recommendations while sounding completely confident. When leaders accept fluency as proof of competence, they risk making decisions that affect people's livelihoods, finances, health, and safety.

Removing Oversight Before Building Verification

One of the most troubling trends in the current AI cycle is the movement from assistance toward autonomy. AI initiatives frequently focus on reducing human involvement. Yet risk management practice emphasizes that risk management should be integrated into decision-making processes and that uncertainty must be actively managed rather than ignored. Risk is fundamentally the effect of uncertainty on objectives and must always be taken into consideration when decisions are made.

Many organizations are pursuing cost savings through automation while delaying investments in verification, auditing, monitoring, and governance mechanisms. This reverses the logical order of responsible risk management.

Ethically, oversight should not be removed because technology appears impressive. Oversight should only be reduced after evidence demonstrates that risk remains within acceptable limits.

High-Stakes Domains Magnify Ethical Risk

It is interesting to see that the strongest push for autonomous AI is occurring in environments where mistakes matter most:

• Healthcare
• Legal services
• Financial advice
• Software engineering
• Public administration

Errors in these domains carry consequences that extend beyond productivity losses. They may affect patient outcomes, legal rights, financial security, privacy, regulatory compliance, and public trust.

PMI's ethical framework emphasizes acting responsibly and protecting stakeholders. Similarly, risk management practices stress proactive management of uncertainty and transparent decision-making.

Allowing AI systems to operate with insufficient human review in high-consequence environments creates ethical exposure that organizations may underestimate.

Overreliance on Best-Case Demonstrations

Vendor demonstrations typically showcase ideal scenarios. Real-world work rarely resembles these controlled conditions.

Agile ways of working emphasize continuous feedback, collaboration, transparency, and adaptation to actual operating conditions rather than assumptions.

Ethically responsible leaders must recognize that demonstrations are hypotheses, not proof. A technology that performs well in a polished demonstration may behave very differently when exposed to incomplete information, conflicting requirements, organizational politics, regulatory constraints, and ambiguous stakeholder needs.

Ignoring the Human Dimension of Knowledge Work

Agile practices demonstrate that Agility depends not only on knowledge but also on the capability to interpret, adapt, learn, collaborate, and respond to changing conditions. Knowledge application requires context and judgment. Knowledge work is rarely a simple process of retrieving information. It requires:

• Ethical judgment
• Contextual awareness
• Stakeholder management
• Negotiation
• Accountability
• Organizational learning

Current AI systems can support these activities but cannot reliably replace the full spectrum of human responsibility that accompanies them.

Recommendations

Match Oversight to Consequence

Not every AI output requires the same level of review. Low-risk activities such as brainstorming, drafting, or summarization may require limited supervision. High-risk activities involving legal, medical, financial, or strategic decisions require rigorous human validation.

This approach aligns with PMI's Code of Ethics principles of responsibility and fairness and follows a risk-based decision-making philosophy.

 Build Verification Before Autonomy

Organizations should establish:

• Audit trails
• Human review checkpoints
• Quality assurance processes
• Performance monitoring
• Escalation procedures

before expanding AI autonomy.

Agility is not about eliminating controls. True agility balances learning, adaptation, and accountability.

Prioritize Transparency and Honest Communication

The PMI Code explicitly highlights honesty as a core professional value. Leaders should avoid overstating AI capabilities to executives, boards, customers, or regulators. Ethical communication means:

• Explaining limitations clearly
• Reporting failures openly
• Avoiding marketing exaggerations
• Separating demonstrated capability from future aspirations

Trust grows when organizations communicate reality rather than hype.

Treat AI as a Knowledge Amplifier, not a Knowledge Replacement

The Agile Manufacturing Enterprise concept, defined in 1991, suggests that organizational success emerges from balancing knowledge management and response capability. Knowledge without appropriate application creates little value. AI should be viewed as:

• A decision-support tool
• A productivity enhancer
• A knowledge accelerator

rather than a wholesale replacement for professional judgment.

Establish Ethical AI Governance

Organizations should create governance frameworks incorporating:

• Accountability standards
• Risk ownership
• Independent reviews
• Human-in-the-loop controls
• Continuous learning mechanisms

Such practices align with both PMBOK risk-management principles and emphasis on continual improvement, stakeholder engagement, and integrated governance.

The Bottom Line

The greatest threat of a third AI winter is not that AI lacks value. It is that organizations may once again confuse genuine capability with exaggerated expectations.

The ethical danger lies in believing that AI can reliably perform human-expert knowledge work without meaningful oversight. History shows that such claims can damage far more than individual projects. They can undermine trust in an entire field.

The lesson is not to reject AI. The lesson is to deploy it responsibly.

Business leaders who embrace this principle will recognize that AI's long-term impact is likely enormous. However, achieving that impact requires honesty about present limitations, disciplined risk management, and unwavering commitment to ethical responsibility.

Organizations that combine AI capability with human accountability will create sustainable value. Organizations that pursue autonomy without verification risk repeating the mistakes that contributed to previous AI winters.

The future of AI will not be determined solely by technological advancement. It will be determined by whether leaders choose ethical stewardship over short-term optimism.

Question for Readers: Should business leaders understand AI capabilities honestly, or should expectations be shaped more by vendor demonstrations than real-world evidence?

Introduction

Risk management is a cornerstone of responsible project delivery, yet the debate over when and how to manage risks remains fierce. Should risks be identified and analysed comprehensively upfront, as in traditional predictive methodologies, or should they be managed continuously throughout delivery, as Agile frameworks propose? This question is not just a matter of methodology; it is fundamentally ethical, touching upon our duties to clients, teams, stakeholders, and society at large. This post explores the ethical dimensions of the Agile vs. Traditional risk management debate.

Challenges

Upfront Identification: Governance vs. Uncertainty

The traditional predictive approach emphasizes comprehensive risk registers and formal upfront analysis. As outlined in the PMBOK and ISO 31000, this method has the ability to reduce surprises and provide transparency, key for governance and audit requirements. It aligns with PMI’s ethical principle of responsibility—ensuring all foreseeable risks are considered and documented. However, the complexity and dynamism of modern projects mean that many risks cannot be foreseen at the outset. Over-reliance on upfront planning may create a false sense of security and stifle responsiveness.

Continuous Management: Adaptation vs. Oversight

Agile frameworks advocate for continuous risk identification and adaptation. This approach recognizes that most risks emerge during delivery, especially in complex or innovative projects. Continuous inspection aligns with PMI’s values of honesty and respect—facing risks as they arise, communicating transparently, and adapting ethically. Yet, critics argue that this approach may lack the rigor required for governance, potentially overlooking systemic risks or failing to meet audit standards.

Ethical Dilemmas: Transparency, Accountability, and Trust

Both approaches present ethical dilemmas. Waterfall’s upfront analysis supports accountability and transparency but may lead to bureaucratic inertia or ignore emerging threats. Agile’s ongoing adaptation fosters trust and openness but could result in missed documentation or gaps in formal oversight. The PMI Code of Ethics emphasizes balancing stakeholder interests, which is challenged by both extremes.

Recommendations

Blend Approaches for Ethical Integrity

Research and best practices suggest that an ethical approach to risk management blends the strengths of both models. Initial identification and documentation should be robust enough to satisfy governance and audit requirements. However, teams must also commit to continuous risk inspection, adaptation, and transparent communication, in line with Agile values and PMI’s ethical standards.

Prioritize Stakeholder Engagement

Ethical risk management requires ongoing stakeholder engagement. This means not only communicating risks early and often but also ensuring that stakeholders understand the evolving risk landscape. As the PMBOK and Agile Practice Guide emphasize, fostering dialogue and trust is crucial to responsible project delivery.

Document Adaptations Transparently

To meet both audit and ethical requirements, all risk adaptations should be documented as they occur. This satisfies the PMI’s principles of fairness and honesty and ensures that lessons learned are shared across teams and organizations.

Foster an Ethical Culture

Project leaders must cultivate a culture where risk is everyone’s responsibility. This means encouraging team members to speak up about emerging risks, rewarding transparency, and never penalizing those who surface inconvenient truths.

The Bottom Line

There is no one-size-fits-all answer to the Agile vs. Traditional risk management debate. The ethical path lies in integrating comprehensive upfront analysis with continuous risk management. By respecting governance requirements and embracing adaptive practices, project professionals can fulfill their duties to clients, teams, and society. Ultimately, ethical risk management is about more than compliance—it’s about stewardship, transparency, and the courage to confront uncertainty as it arises.

Question for Readers: What ethical challenges have you faced when balancing governance requirements with the realities of Agile project delivery?