4 ms·
A central point of TFA -- which the grandparent post offers an example of -- is that "Agile" has "failed" because rather than adopting the values of the Agile M
by mindcrime 11y ago
A central point of TFA -- which the grandparent post offers an example of -- is that "Agile" has "failed" because rather than adopting the values of the Agile Manifesto, organizations adopted cargo-cult "Agile" rituals without understanding the principles and purposes of Agile
Right, and I agree 110% with that. I'm just not sure I'd agree that that means "agile has failed". There are companies out there using agile oriented processes and having quite a lot of success with them. When done well, Scrum really is a very effective process. I remember when I worked for Lulu.com, we had a great scrum-master, a company culture where everybody, including the business people, "bought in" to the approach, and a group of really talented developers, and it all worked great for us. So had "agile failed" there? I'd say not.
What I will definitely agree with, and what I've said myself, is that the term "agile" has been overloaded to the point of being essentially meaningless now, except in a very constrained context.
- amyjess 11y ago> I'm just not sure I'd agree that that means "agile has failed". I think that's because you're disagreeing with what Agile has failed at. You're interpreting it as "Agile has failed to be an effective process", while GP and the article are interpreting it as "Agile has failed to achieve widespread adoption". Agile can certainly be an effective process, but that doesn't matter if 90% of the companies that claim they use Agile are actually using something very un-Agile that they happen to call Agile. This actually raises the barrier to Agile being adopted by more companies, because now everyone hears "Agile" and automatically thinks of it as this... thing that's adopted by MBAs instead of what it actually is, so they reject it.
- derefr 11y agoI think there's a third interpretation: "Agile has failed to spread the spirit of its message to its followers without being corrupted in the process." 'Agile' has achieved widespread adoption. Agile techniques have not. Thus, if 'Agile' were a person—the founder and namesake of a religion, say—they would be ashamed at what their followers were doing in their name.
- mindcrime 11y agoFair enough. I think we're basically in agreement.
- georgemcbay 11y ago"So had "agile failed" there? I'd say not." But was it the cause of success? Who knows? In my experience, if you assemble a great team (either by happenstance or by planning) pretty much any process you adopt can work great, but (ignoring the downtime for learning the new process) you could swap out that process with virtually any other software process that is common enough to have a name and still get great results. Meanwhile, a mediocre or overly political team will find new and interesting ways to fail with any process.
- mindcrime 11y agoBut was it the cause of success? Who knows? The cause? No, I wouldn't say so, not in and of itself. I don't know that any process can really "cause" success all by itself. But some are better than others at not getting in the way and actually helping rather than hindering. My (admittedly subjective) observation is that our use of Scrum at Lulu was helpful, compared to either "no process" (eg, pure cowboy coding) or some of the more broken processes I've been exposed to in the past. And to me, that's about as much as you can hope for. Because, at the end of the day, it really is more about the team than the methodology. And yes, a truly great team can probably overcome nearly any broken methodology / process and still ship something awesome. The question is how much pain they have to endure to do so.