When Agile Projects Go Bad 139
blackbearnh writes "CIO Magazine has an article up looking at some of the ways that Agile projects can fail, or Agile can be misapplied in organizations. Some of the issues raised may not be new, but folks might want to pay special attention to these, since the people throwing the stones are two of the original Agile Manifesto signatories, Alistair Cockburn and Kent Brock. From the article: 'Once individuals become familiar with Agile, either through training or practice, they can become inflexible and intolerant of people new to the process. Cockburn has seen this in action. "I'm one of the authors of the manifesto, so if I say something 'weird,' they can't tell me I don't understand Agile. But if someone else — and it doesn't matter how many years of experience they have — says something funny, they get told they don't understand Agile."'" Here's another recent article by the same author on the perils now besetting Agile.
Uhm... (Score:4, Funny)
Alistair who ??
Cockburn? (Score:5, Funny)
Cockburn has seen this in action.
I have personally experienced cockburn and assure you will become "become inflexible and intolerant".
Re:Project steps (Score:3, Funny)
list the steps from requirements gathering right through to production deployment.
That would not be agile :-)
Re:Buzzword Boredom (Score:3, Funny)
Agreed. Despite some successes, generally speaking mostly small or low mid-scale projects, "Agile" is to software engineering what Red Bull Flugtag contraptions are to aviation engineering.
Re:Lots of ragging on Agile here (Score:3, Funny)
Rather, it's "right people" who are rare. Not every project can hire only programmers that are in the top 10%. There just aren't that many to go around. Maybe as low as 1 in 10, by some estimates...
That can't be right - over 75% of the developers that I've asked rate themselves in the top 10%!