From this short assessment, I knew why they were failing. You see, agile project management isn't enough. As a mathematician might say, "It's necessary, but not sufficient." The underlying goal of agile software development is to rapidly deliver high-quality code that meets the users' needs.
Agile project management practices go a long way to making this possible. They keep requirements flexible and allow them to change pretty much on a whim. The catch is that the software itself has to be able to change on a whim too.
It's one thing to be able to say halfway into your project that you are going to make major changes to the requirements. It's another thing to actually do it and still deliver on time.
The presumption, borne out through years of experience, is that software requirements change rapidly. The project must be able to keep pace with these changes or risk being obsolete before it is even delivered.
Collection
[
|
...
]