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
- Have you experienced or witnessed the unethical practice of traditional practices being relabelled as Agile? What was the impact?
- How can leaders ensure that Agile transformations remain transparent and ethically grounded?
- What steps can practitioners take to observe ethical values and foster honest conversations about what is truly Agile and what is not?
