Coconut Headphones: Why Agile Has Failed by Mike Hadlow.
From the post:
The 2001 agile manifesto was an attempt to replace rigid, process and management heavy, development methodologies with a more human and software-centric approach. They identified that the programmer is the central actor in the creation of software, and that the best software grows and evolves organically in contact with its users.
My first real contact with the ideas of agile software development came from reading Bob Martin’s book ‘Agile Software Development’. I still think it’s one of the best books about software I’ve read. It’s a tour-de-force survey of modern (at the time) techniques; a recipe book of how to create flexible but robust systems. What might surprise people familiar with how agile is currently understood, is that the majority of the book is about software engineering, not management practices.
….
Something to get your blood pumping on a weekend. 😉
We all have horror stories to tell about various programming paradigms. For “agile” programming, I remember a lead programmer saying a paragraph in an email was sufficient documentation for a plan to replace a content management system with a custom system written on top of subversion. Need I say he had management support?
Fortunately that project died but not through any competence of management. But in all fairness, that wasn’t “agile programming” in any meaningful sense of the phrase.
If you think about it, just about any programming paradigm will yield good results, if you have good management and programmers. Incompetence of management or programmers, and the best programming paradigm in the world will not yield a good result.
Programming paradigms have the same drawback as religion, people are an essential to both.
A possible explanation for high project failure rates and religions that are practiced in word and not deed.
Yes?