Four reasons to dump Scrum

Credit: flickr/tomasz przechlewski

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?

Defense

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

Yes "changing Scrum" to suit you might work, but if it still does not work, whose fault would it be?

Joshua Partogi on scrumalliance.org

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

In my opinion, tailoring your process to your situation has always seemed the most agile option of all.

Gene Hughson on lostechies.com

I always mention that if something doesn't work for the team, do something that will work for the team. So listen to your team to get the maximum output.

Harald Rietman on scrumalliance.org

Scrum is hard. It requires the kind of buy in that, if you've got it, you probably don't need Scrum anyway.

debacle on news.ycombinator.com

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.

For the latest IT news, analysis and how-tos, follow ITworld on Twitter, Facebook, and Google+.

Now read this:

Developer declares 'I am done with the Freemium Business Model'

Khan Academy offers JavaScript as their first computer language

Study says Facebook profile can predict job performance

From CIO: 8 Free Online Courses to Grow Your Tech Skills
Join the discussion
Be the first to comment on this article. Our Commenting Policies