In modern project management, agile development is becoming increasingly popular; agile is invoked at every turn, as if not being agile means falling behind the times. Is agile really a panacea for modern software projects? Is it truly a universally applicable development method?
The Origins of Agile
Let me start with the conclusion: agile development is in fact a method with considerable limitations, and it is not universally applicable! It grew and thrived simply because it aligned with the rapid growth of the Internet and matched the needs of Internet applications for changing requirements and frequent releases fairly well.
Compared with traditional software, Internet software also features incremental delivery, the ability to fix online issues quickly, and a relatively higher tolerance for quality problems. All this makes agile development easier to land in Internet projects.
And as Internet giants adopted agile methods and agile institutions promoted them vigorously, today agile seems to have become a universal method that applies everywhere. Various frameworks for applying agile have also emerged, such as Scrum, SAFe, LeSS, Nexus, and so on.


But when we look at how these frameworks developed and the scenarios where they are applied, we find that each framework carries considerable constraints. Small frameworks such as Scrum impose specific limits on team size and require meeting ceremonies; large frameworks such as SAFe impose requirements on organizational structure, multiple supporting roles, and dedicated teams. And so on…
The birth of large frameworks, too, came about through evolution in response to the real operation of actual projects; they were meant to address problems in specific scenarios, with more roles, ceremonies, and processes continuously added like bricks and tiles. Yet this seems to be retracing the development trajectory of traditional software R&D processes, and likewise racing headlong toward high-complexity teams!
The Limitations of Agile
So we cannot help but reflect: is agile really a method with universal applicability? Is it a panacea for solving traditional problems?
We cannot deny the positive value of the ideas agile emphasizes, such as collaboration and responding to change; the Agile Manifesto itself was an extremely necessary reform of rigid, traditional software processes.

The problem, however, is that agile was born out of reflection on software development processes. Without exception, the seventeen experts who proposed the Agile Manifesto all came from the field of software development. We cannot say that these masters’ thinking and vision were not ahead of their time, but the Manifesto itself was mainly a set of solutions proposed for the original problems in the domain of software development.
In other words, agile methods are inherently aimed only at software development, not at software products and project management. To form a software project and run a product, besides development there are other roles such as product, design, operations, customer service, quality, and security. The absence of these roles means that when the method is applied at the product level, it lacks targeted thinking from the corresponding perspectives, and instead focuses mostly on the problems that the development role encounters within the product.
Precisely because of this inherent limitation, agile tends to run into all kinds of problems in real-world application. During a project’s incubation period, when the focus is on R&D, agile is at its most valuable. But once a product gets on track and needs to coordinate with more different units and roles, agile often starts to show that it is not up to the task.
The Value of Agile
The success of any enterprise or project, in fact, cannot be separated from two things, systems and culture.
- Agile methods, because of their inherent limitations, are not universally applicable as a system.
- But the culture and values conveyed by agile methods are where the value of agile truly lies. Whether or not you adopt agile methods, even if you use traditional processes, embracing agile values can still help a project succeed.
Just my humble opinion. For more introductory articles on agile development, please refer to the collection.
