The Agile Enterprise

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?

Introduction

In the context of digital transformation, Agile delivery becomes the norm in many organisations and Agile tools have revolutionized how organisations track progress, collaborate, and deliver value. However, as these tools become popular, in some organisations, their use has shifted from fostering teamwork to monitoring individual employee activity. This transition raises serious ethical concerns, particularly when excessive surveillance undermines autonomy, dignity, and trust. This blog post explores the ethical implications of using Agile tools for surveillance, highlights the challenges faced, offers actionable recommendations, and closes with crucial questions for reflection.

Challenges of Excessive Surveillance in Agile Platforms

Loss of Autonomy and Dignity

The PMI Code of Ethics emphasizes respect as a foundational value, stating that leaders must treat employees with dignity and foster an environment of trust. Agile principles similarly stress self-organizing teams and individual empowerment. When managers use agile platforms to track task completion rates at the individual level, they risk reducing employees to mere data points. Public shaming of low performers, as seen in some organizations, corrodes morale and strips individuals of their autonomy, violating both PMI standards and agile values.

Fairness: Judging Through Incomplete Data

Fairness is another core PMI ethical value. Agile tools often capture quantitative metrics—number of tasks completed, time logged—but miss the qualitative aspects of work, such as problem-solving, teamwork, and creativity. Judging employees solely by incomplete data leads to unfair assessments, misrepresenting their contributions and potentially harming their professional reputation. The Manifesto for Agile Software Development advocates valuing individuals and interactions over processes and tools, reminding us that numbers rarely tell the whole story.

Responsibility: Misuse of Information for Control

The PMI Code of Ethics and Professional Conduct and Agile Practice Guide urge leaders to use information responsibly, to support improvement rather than exert control. Surveillance for its own sake, especially when used to intimidate or micromanage, is an ethical breach. The Manifesto for Enterprise Agility highlights the need for transparency and trust, which are undermined when leaders misuse Agile platforms to monitor activity excessively. This behaviour erodes psychological safety—a key ingredient in high-performing Agile teams—and stifles innovation.

Example: Public Shaming Through Task Tracking

Consider an organization where managers publish individual task completion rates, ranking employees from best to worst. Those at the bottom are publicly shamed, regardless of context. This practice violates the PMI‘s Code of Ethics mandate for respect, fairness, and responsibility. It also contradicts the Agile principle to focus on building motivated, trusted teams. Such surveillance fosters a culture of fear and compliance rather than growth and collaboration.

Recommendations for Ethical Use of Agile Tools

Promote Team Collaboration Over Individual Surveillance

Agile platforms should be used to enhance team visibility, not individual scrutiny. Leaders must shift the focus from tracking personal metrics to facilitating collective progress. Create dashboards that highlight team achievements, blockers, and opportunities for improvement, avoiding singling out individuals.

Respect Autonomy and Dignity

Embedding PMI’s ethical value of respect means trusting employees to self-organize and manage their work. Leaders should foster an environment where feedback is constructive and private, never public or punitive. Agile tools can be configured to support one-on-one coaching, mentorship, and peer reviews, upholding dignity always.

Ensure Fairness in Performance Assessment

Combine quantitative metrics with qualitative insights. Encourage regular retrospectives and feedback loops that capture the full spectrum of employee contributions. Use Agile tools to facilitate conversations, not make judgments. The Agile principle of valuing individuals and interactions should be reflected in every assessment.

Use Data Responsibly and Transparently

Leaders must communicate the purpose of data collection and use it ethically. Transparency builds trust, while secrecy breeds suspicion. Establish clear guidelines for what data is tracked, who can access it, and how it will be used. Reference the Manifesto for Enterprise Agility and PMI Code to reinforce responsible stewardship of information.

Address Ethical Breaches Proactively

Organizations should create channels for employees to report misuse of agile tools. Regular audits and training on ethical conduct can help prevent breaches. When violations occur—such as public shaming or unfair judgments—leaders must act swiftly to restore trust and correct behaviours.

The Bottom Line

Agile platforms are powerful enablers of collaboration and delivery. Yet, when used for excessive surveillance, they threaten the very principles that make Agile successful: respect, fairness, and responsibility. Ethical leadership is essential to ensure these tools serve their intended purpose—empowering teams, fostering trust, and driving improvement. Organizations must commit to ethical practices that protect employee autonomy and dignity. Ultimately, the way we use Agile tools reflects our values and shapes our culture.

Questions for Readers:

• How does your organization balance visibility with ethical value of respect for individual autonomy when using Agile tools?
• What safeguards are in place to ensure ethical values of fairness and transparency in performance tracking?
• How can leaders foster a culture where Agile tools support initiative and ethical values?

Introduction

Agile methodologies emerged as a response to excessive bureaucracy, inflexible processes, and slow delivery cycles in traditional project management. The Agile Manifesto, published in 2001, championed values such as individuals and interactions over processes and tools, customer collaboration over contract negotiation, and responding to change over following a plan. Yet, as organizations scale Agile implementations, they often introduce new frameworks, governance structures, and reporting requirements. Ironically, these additions risk recreating the very bureaucracy Agile was designed to eliminate.

From an ethical perspective, this trend raises important questions. Are organizations honouring their commitment to agility, or are they merely adopting the language while reinstating old habits? By examining principles from the Project Management Institute (PMI) Code of Ethics and Professional Conduct, the Agile Practice Guide, the Manifesto for Enterprise Agility, and the PMBOK, we can better understand the ethical implications of bureaucratizing Agile practices.

Challenges

Governance and Reporting Overload

Scaling frameworks often introduce significant governance, reporting layers, new roles, and recurring meetings. These additions can dilute Agile’s core tenet: delivering value quickly by minimizing non-essential processes. Business teams may find themselves spending excessive time in planning ceremonies, status meetings, and compliance activities that offer little direct value to customers.

Ethical Breaches: PMI Code of Ethics

• Responsibility: The PMI Code of Ethics emphasizes prudent use of resources and delivering value to stakeholders. When organizations allocate valuable time and effort to low-value activities, they violate the principle of responsibility. Resources are wasted, and the focus shifts from solving customer problems to satisfying procedural requirements.
• Respect: Employees’ time and expertise are among an organization’s most precious assets. When unnecessary administrative work becomes the norm, it signals a lack of respect for employees as professionals. The Agile Practice Guide underscores the need for empowered, self-organizing teams, yet bureaucracy can erode autonomy and morale.
• Honesty: Perhaps most troubling is the gap between stated intentions and actual practice. Organizations often claim increased agility while simultaneously increasing procedural overhead. This disconnect undermines honesty and transparency, core values both of PMI’s Code of Ethics and the Agile Manifesto.

Value Mismatch: Agile Manifesto and Enterprise Agility

The Manifesto for Enterprise Agility and the Manifesto for Agile Software Development stress delivering value and reducing waste. When teams spend more time justifying their work than doing it, the original intent of Agile is subverted. The PMBOK calls for continuous process improvement, but bureaucracy tends to ossify processes instead of streamlining them.

Real-World Example: Ceremonies Without Value

It’s not uncommon for business teams to attend numerous planning and coordination sessions—release planning, PI planning, Scrum of Scrums, and more—that consume significant time but add minimal value to customers. When these ceremonies become ends in themselves, rather than means to deliver value, the ethical foundation of Agile is undermined.

Recommendations

Revisit Core Agile Principles

Organizations should regularly revisit the Manifesto for Agile Software Development and the Manifesto for Enterprise Agility to ensure new processes and structures support, rather than hinder, value delivery. Question whether each new meeting or report truly serves the customer.

Apply Ethical Checks from the PMI Code of Ethics

• Responsibility: Audit activities to ensure resources—especially people’s time—are directed toward outcomes that matter.
• Respect: Engage teams in decision-making about which processes are necessary. Empower them to challenge wasteful practices.
• Honesty: Report both successes and failures in Agile adoption truthfully. Avoid “Agile-washing”—claiming agility while layering on bureaucracy.

Lean into Continuous Improvement (PMBOK & Agile Practice Guide)

Encourage regular retrospectives focused on process improvement. Identify bottlenecks, redundant meetings, and reporting requirements that don’t add value. Incrementally eliminate or streamline them.

Adopt a Value-First Mindset

Measure the impact of new roles, meetings, or governance structures through the lens of customer value. If a process doesn’t directly contribute to delivering value, reconsider its necessity.

Foster a Culture of Respect and Autonomy

Support teams in tailoring Agile practices to their context. Avoid one-size-fits-all scaling frameworks that prescribe rigid structures regardless of team needs.

The Bottom Line

Bureaucratization of Agile is a paradox that threatens the ethical and practical foundations of agility. By introducing layers of governance, reporting, and ceremony, organizations risk violating the very principles Agile was meant to uphold. The PMI Code of Ethics and Professional Conduct, the Agile Manifesto, the Manifesto for Enterprise Agility, and the PMBOK all emphasize responsibility, respect, honesty, and value. Staying true to these principles requires vigilance, humility, and a willingness to challenge entrenched processes. Only then can organizations realize the true benefits of Agile—delivering meaningful value to customers, empowering teams, and continuously improving.

Questions for Reflection

• Does your organization’s Agile implementation align with the original ethical values of the Agile Manifesto, or has bureaucracy crept in?
• How can you, as a project professional, advocate for ethical Agile practices in your workplace?
• What steps could your team take to enforce ethics, reduce low-value administrative work and refocus on customer value?

Introduction

Although most Agile frameworks emerged from software development practices, in the last decade, “Agile” has become a discussion topic and even a target state in many organisations. From boardrooms to project kick-offs, organizations are eager to embrace Agility, because it promises faster delivery, adaptability, and happier teams. However, Agile communities of practice are concerned with the trend that introducing Agile practices outside product development teams, especially scaling at the enterprise level, could see existing bureaucratic management approaches rebranded as “Agile” without substantive change or transparency. Another concerning trend is using Lean Six Sigma practices and metrics such as kanban, flow, throughput, and cycle time without mentioning their origin and purpose; Those practices are not just a matter of semantics; it raises significant ethical concerns. This blog post explores the ethical pitfalls of mislabelling and relabelling established methods as Agile.

Challenges

Misrepresentation and Honesty

The PMI Code of Ethics emphasizes honesty as a foundational value for project managers and practitioners. Misrepresenting traditional methods as Agile violates this principle. When existing Lean Six Sigma or bureaucratic practices are simply renamed—without acknowledging their origins or limitations—it creates a false impression of transformation. For instance, calling a rigid compliance process an “Agile workflow” when approval times and hierarchies remain unchanged is misleading. This misrepresentation can erode trust among stakeholders and undermine the credibility of Agile initiatives.

Disrespecting Stakeholders

Respect is another core value in the PMI Code of Ethics. Stakeholders deserve accurate, clear, and complete information to make informed decisions. When organizations relabel legacy processes as Agile, they deny stakeholders the truth about what is really changing and what is not. This disrespect can have tangible consequences: unrealistic expectations, frustration, and disengagement from teams and customers who were promised agility but receive bureaucracy in disguise.

Failing in Responsibility

The principle of responsibility, as outlined by the PMI Code of Ethics, mandates that practitioners communicate implementation realities and potential impacts. Failing to clarify the differences between genuine Agile practices and legacy methods leaves teams unprepared for the challenges ahead. It also hampers learning, improvement, and transparency, core tenets of both the Agile Manifesto and the Manifesto for Enterprise Agility. Pretending that a process is Agile, when it is not, prevents organizations from honestly assessing what works, what doesn’t, and where true change is needed.

The Illusion of Progress

PMBOK and the Agile Practice Guide stress the importance of continuous improvement and transparency. When traditional practices are rebranded as Agile, organizations may celebrate perceived progress without making meaningful improvements. This creates an illusion of transformation, stalling genuine change and reinforcing the status quo. Teams may become cynical, and the organization risks missing out on the real benefits of Agile, such as faster feedback, empowered teams, and adaptive planning.

Recommendations

Acknowledge Origins and Limitations

Ethical practice starts with honesty. Organizations must clearly identify which processes are genuinely Agile and which are rooted in traditional management. Acknowledge the value and limitations of Lean Six Sigma, or bureaucratic practices. Transparency fosters trust and enables constructive dialogue about what should change and why.

Educate Stakeholders

Invest in stakeholder education about the principles of Agile, as articulated in the Agile Manifesto and the Manifesto for Enterprise Agility. Explain what Agile is, what it is not, and how it differs from other approaches. This empowers teams, customers, and leaders to set realistic expectations and support meaningful transformation.

Communicate with Integrity

Follow the PMI Code of Ethics by communicating implementation realities. If a process has not changed, do not present it as Agile. Share both the opportunities and limitations of current practices. This honesty allows for informed decision-making and continuous improvement.

Foster a Culture of Feedback

Agile is rooted in feedback, reflection, and adaptation. Encourage open discussion about what is working and what is not. Solicit input from teams and stakeholders. Use retrospectives and regular check-ins to identify areas for authentic Agile adoption.

Align Practices with Agile Values

Review current workflows against the Agile values and principles. Are teams empowered to respond to change? Is customer collaboration prioritized over contract negotiation? Is working software (or deliverables) valued more than comprehensive documentation? Ensure that your practices reflect these priorities before labelling them as Agile.

The Bottom Line

Rebranding traditional management as Agile without genuine change is more than a missed opportunity; it is an ethical breach. It undermines honesty, disrespects stakeholders, and shirks responsibility. Genuine Agile adoption requires transparency, education, and a willingness to confront uncomfortable truths about legacy processes. By adhering to the PMI Code of Ethics and related guidance, organizations can avoid these pitfalls and build a culture rooted in trust, respect, and continuous improvement.

Questions for Reflection

1. Have you experienced or witnessed the unethical practice of traditional practices being relabelled as Agile? What was the impact?
2. How can leaders ensure that Agile transformations remain transparent and ethically grounded?
3. What steps can practitioners take to observe ethical values and foster honest conversations about what is truly Agile and what is not?