Although most Agile frameworks emerged from software development practices, over 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.
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. 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.
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. 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.
Blog post: Rebranding Traditional Management as Agile: An Ethical Examination
ProjectManagement.com - The Agile Enterprise
