Monday, November 17, 2008

Seven Years To Rot

So here we are, seven years after the Manifesto, and the webersphere is pontificating about the decline of agile, to the point that Uncle Bob has hard time containing his anger in front of such a display of nonsense and dishonesty.

What is going on with agile? After seven years of existence (I know, the techniques and approaches agile promotes predate the Manifesto), has it started to rot?

Some suggest that agile is following the Gartner hype-cycle and has now past its "peak of inflated expectations":

Of course, there is hype around agile and the diatribe of some of its fanatics can be a little over the top. But I think that the current "decline" in agile is not due to some disillusionment.

I think this so-called "decline" comes from the numerous software sweat shops and less-than average programmers who started to pretend they do "agile" without changing anything in their craftsmanship. Instead of a disillusionment, agile suffers from dilution.

Hopefully, people will be able to sort the wheat from the chaff and debunk these agile fraudsters. When this will happen, agile will start climbing its "slope of enlightenment".


Carl Schmidt said...

It's inevitable. New methods and tools will get introduced on a regular basis, folks will latch on to them, hoping to find an easy path to success, and then turn around and blame the method or tool when they fail. As Uncle Bob says, the secret is simply to do a good job. The best tools and methods will produce mediocre results when employed by mediocre practitioners.

David Dossot said...

You are right.

What blurs the whole picture is that many of these new methods and tools turn out to be ill-generalized solutions to niche problems or pure snake-oil salesman's fantasies. These clearly deserve a blame. So maybe agile is the baby that gets thrown with the bath's water?

Or maybe our tendency to be suckers for new stuff is to be blamed?