Re:Manifesto for Half-Arsed Agile Software Development
by UK-AL on Wednesday January 15, 2014 @01:05PM
(#7064895)
Agile is underspecified because it is a general philosophy. I.E React to change, rather than following a 12 months rigid plan.
There are different concrete ways to implement Agile, such as using Scrum, DSDM, or various other methods.
Now I am seeing this from an outside perspective; I'm not a programmer or software engineer but I work directly with them in a weird sort of non-supervisory product manager role. In my opinion, this is no different...in fact, "Agile", which as far as I can tell is nothing more than a hand-wavy underspecified form of Extreme Programming, has so much ambiguity in its definition that you can't ask any two advocates and get the same response as to what it is. And as such, whenever there is a problem with the outcomes of the process, the only apt response is the No-True-Scotsman fallacy...which makes development descend into the phenomenal failure of productivity that all holy wars are.
This isn't unique to Agile. Lean and Six Sigma are also mixed bags of philosophy and process, and they have been mixed bags of occasional success and phenomenal failure.