Read Next

Agile Scrum: Delivering Broken Software Since 1991

Update: This is quite a long article. If you're looking for a quick read, it breaks down a bit like this:

Update 2: There are active and interesting discussions of this article on HackerNews and Reddit

I have a lot of love for Scrum, the software development process. I have my own little box of Index Cards and Sharpies, and I have sized Backlogs for many of my side projects. Scrum has potential to empower developers more than almost any other set of techniques.

But in almost every implementation of Scrum I've seen in The Real World™, managers are incentivized to help their team deliver broken software to a deadline, and usually end up succeeding in the former and failing in the latter. And when implemented like that, a system that should be an absolutely overwhelming win for developers becomes a tool to beat them around the head with...

So here's Scrum, simplified, and as it's meant to work: You have a Backlog of work to complete, broken down in to Stories, which ­are distinct pieces of work that should take a few hours to a few days to complete. These are frequently displayed on a Story Board, real or virtual.

Why I really love SCRUM

On DROdio

 We've been using scrum all over the company for the past year, and the more I use it, the more i love it.  I previously wrote a blog about using the scrum agile development methodologies in a non-development capacity -- i.e., with a sales or marketing team.  I got a lot of questions from that blog about exactly why Scrum was so great, so in this post my goal is to tell you why I love Scrum so much, and why I recommend it to be adopted within any company (and if the US Government ever implemented Scrum -- correctly -- we'd seriously save trillions of dollars.  That's probably an impossible wish, but  after all, thinking big is free.)

Here's a good 7 minute video describing Scrum.  If you're not at all familiar with the methodology, you might want to read my case study below before you watch the video -- it'll make more sense that way.

Video: Scrum in 7 Minutes:

Scrum Case Study:

Rendering New Theme...