September 13, 2012, 1:53 AM —
Although one of the leading Agile Development tools, and used by enterprises everywhere, Scrum is not for everyone or everything.
Programmer Jimmy Bogard gives four reasons to un-Scrum in “Why I'm done with Scrum” on his LosTechies (se habla code) blog. He prefers pull-based approaches, dislikes iteration planning meetings, Scrum disrupts established organizations, and shifts the focus away from delivery. Bogard has had success with Scrum, but tells us why it can't work everywhere.
Even the ScrumAlliance agrees, in their blog entry “What to do When Scrum Doesn’t Work.” Of course, their first thought is that people who fail with Scrum may be using it wrong, and they're blaming the messenger, Scrum, when the process exposes problems, they're impatient, they're not adapting the process, or they're using the wrong process. But aren't some projects doomed no matter what you do?
When I took over development of a extremely dysfunctional engeering team at an established startup with 100 people, the first thing I did (after watching for a bit to learn) was put in scrum. It worked. And it worked really, really well.
fingerprinter on news.ycombinator.com
Scrum is a self-destructive methodology, it ceases to exist the moment people know what to do, when to do -- then the process becomes a burden and annoyance, you may have hit that point.
Francisco Aquino on lostechies.com
If you read between the lines, you realize that Scrum was created and popularized by consultants who go into dysfunctional teams/organizations, and tries to fix the worse problems.
martincmarin on news.ycombinator.com
Done with Scrum
I hate it, for different reasons than you though (but I am no expert, so I may be wrong on some counts)
JS on lostechies.com
Scrum might have valuable in big hierarchical companies or when there are many average-talent programmers, but there's no way I'd foist it on a team of smart developers much less and early stage startup.
eevilspock on news.ycombinator.com
Get it done
Scrum isn't an acronym, it's named after a rugby scrum. A 1986 study compared high-plerforming, cross-functional teams to the rugby Scrum formation. Hence the photo.