When Agile Fails…. Jonathan Rayback Motorola Solutions, Inc. Credit where credit is due…. Mike Brown blog entry at Utest : “Why Agile Fails, Sometimes…” http://blog.utest.com/why-agile-development-fails-sometimes/2012/11 /
Motorola Solutions, Inc.
Mike Brown blog entry at Utest:
“Why Agile Fails, Sometimes…”
…piqued my interest in the topic. Brown’s article provides the outline and much of the material for my presentation today.
“Agile consultants ruined the software group I work in. Making good software is hard, and anyone claiming to have a magical process that guarantees good software is selling snake oil. I can appreciate your wanting to make a buck, but would also seriously appreciate it if you could find some other industry besides software development to go screw up.”
– Anonymous Agile Victim
“This system is bloated with meetings, excel spreadsheets and anemic of any real documentation. Agile and the people who support it are full of themselves and their aversion to documentation is detrimental to real active communication. The disinterest to documentation presumes humans will retain meeting to meeting barrage of verbalized ideas. Agile is full of egotistical self congratulating ideologies over used buzz words like “flexible” and “living”. People can’t remember what they said from one over stated meeting to another.”
– Anonymous Agile Victim
"'Universal Credit' — the plan to consolidate all Britain's welfare payments into one — is the world's biggest 'agile' software development project. It is now close to collapse, the British government admitted yesterday…”
May 25, 2013 – Slashdot.org
Voke survey of 200 companies that had recently transitioned to Agile:
“While many people assume that Agile is faster, better, and cheaper, actual results vary greatly. Many organizations are diving into the Agile movement without a clear understanding of what it is, and what the consequences of adoption may be. They may not realize that today’s solutions are tomorrow’s problems.”
– Theresa Lanowitz, lead analyst at Voke
“I don’t think most people need convincing about agile principles, even if they’re just attracted to the idea of frequent delivery. In practice, however, a lot of waterfall behaviors survive by hiding behind the new agile jargon. If we want different results, it’s not enough to change our jargon, we have to actually change the way we collaborate!”
– Nate Oster, founder of CodeSquads LLC.
“When trying to adopt Agile practices, there will be a ton of excuses as why it won’t work. Those who understand the real benefits of the approach – and genuinely want to make the transition – will likely have success. Those who are searching for reasons why it will fail – well, they will likely find them and either abandon the effort entirely or end up practicing what Elisabeth Hendrickson calls ‘fake agile’.”
– Mike Brown, UTest.
“To the people who are victims of Fake Agile, I extend my deepest sympathies. “Agile” ruined your life only in that it provided an all-too-glib buzzword for your organization and management to latch onto. I dearly hope that you’re able to experience real Agile: frequent delivery of value at a sustainable pace while adapting to the changing needs of the business.”
– Elisabeth Hendrickson, Test Obsessed
“But there are implications. There’s no such thing as a free lunch! And there’s no magic bullet for software development. Sorry, no, you can’t just drink the cool aid :-) In exchange for all these benefits, you do get less predictability, software and humans are still difficult, you can’t blame someone else if things don’t go right, and it generally requires much more commitment and effort from everyone involved – i.e. teamwork is even more important.”
– Kelly Waters, All About Agile