2 ms·
I think the basic problem with Agile (with a capital "A") is that it has always been a marketing term and not a technical one. Thus it has been drowning under t
by Silhouette 16y ago
I think the basic problem with Agile (with a capital "A") is that it has always been a marketing term and not a technical one. Thus it has been drowning under the weight of its own hype for so long that it no longer really means anything.
I'm sure a lot of practices that are commonly considered Agile have genuine merit. Indeed, good developers have been using many of these practices since long before anyone started naming them. Equally, bad developers probably won't adopt them whatever they are called.
Other practices that tend to get bundled into various specific Agile processes are, IMNSHO, 100% pure snake oil. After so many years, they have a pretty poor track record, when surely they should be dominating the software development field by now if they were as effective as their advocates claim and everyone else is doing such horrible things.
I always find it rather ironic that despite the basic tenet of the Agile Manifesto that individuals and interactions are more valuable than processes or tools, we still have consultants and authors pushing processes like XP or Scrum or whatever the next one is, almost invariably using all-or-nothing arguments about how you need to use all the components of their favourite buzzword method or it just doesn't work, and if you don't and your project fails then that must be why.
What would I do differently next time, in the sense of promoting what actually works and not some diluted buzzword bingo entry? I'd single out individual elements, such as using shorter iterations or emphasizing ongoing communication with a client over formal up-front specifications. I would describe them in plain English, I would consider their merits and risks individually, and perhaps I would consider how some of them interact. But above all, I would not artificially bundle up a whole bunch of distinct ideas that can be understood perfectly well in isolation (whether or not they are actually effective) and create some artificial super-idea and a black-and-white approach to using it.
And I'd execute anyone who started naming practices, overall processes, or the roles within those processes in a way that would make anyone outside the Kool-Aid drinkers burst out laughing.