The Making of ‘SCRUM in 10 Minutes’ Video Tutorial

If you have been following this blog, you already know that Axosoft is embracing SCRUM in a big way. We have adopted SCRUM into our own development efforts and we have also made it a top-priority to have full SCRUM support in OnTime 2009 (due out in Q1 of 2009 and currently in beta).

But as our own customer survey showed, even though SCRUM is the top agile development method, it is in use by only 12% of software development teams. So if SCRUM is so great, why is it not more widely adopted? There are several potential answers to that question:

1. There isn’t a single good source of information on SCRUM.
2. The few videos that do talk about SCRUM are either extremely long, obnoxious, boring or vague. In some cases, all of the above!
3. SCRUM classes are expensive. A two-day class generally runs in the neighborhood of $1800.
4. There is far too much talk and unnecessary debate about chickens, pigs and other minor details!
5. The few sources of information that do exist generally push their own products, tools or services.

With that information in mind, I felt that the software community could use a brief crash-course that covers the core concepts of SCRUM without any product, tools or services being promoted to distract the viewer. So I set out to create a video that would introduce SCRUM in under 10 minutes. It turns out, this is not such an easy task.

The SCRUM Script

I started writing the script in a style that might be familiar to a lot of boring college professors:

A product backlog is a list of features…a sprint is like a milestone…blah blah blah

Even as I wrote the script, I thought the script was bad, but I wanted to get something on paper as a starting point. I then shared the script with one of my partners in crime, Angelo Coppola. He immediately blasted it. He ripped into it calling it “boring”, “vague” and “obnoxious.” Wait a second! Those descriptions sounded vaguely familiar. I already knew what Angelo was telling me: a total re-write had to be done. But before re-writing the script, I went to our conference room white board and I created a storyboard of what I wanted in the visuals:

As you can see, I was meant to be an artist! I must have missed my true calling somewhere along the line. With the new visuals in hand (or I should say in my iPhone), I went back to re-writing the script. I brought in Derek Harju, our resident flash artist at Axosoft, asking him to take my storyboard and bring it to life! Pretty easy, right?

In the new script, I decided to introduce concepts and visuals simultaneously. In a previous video I made on a political topic, the impact of bringing in visuals and words together at the same time seemed to work  well. So the script changed from a boring “a product backlog is blah blah blah…” to something like this:

In SCRUM you work with THESE [show a product backlog], which is then broken down into THESE [show a release backlog]…and so on.

This time, I felt the script was much stronger and Angelo agreed. So it was on to the visuals.

The SCRUM Visuals

Over the next several weeks, Derek went to work to bring the visuals to life. From the beginning, Derek’s work was great. Here are a couple of the earlier samples:

The Team and a Product X Under Development

Illustrating the Product Backlog

The early illustrations were good, but they weren’t great. So with each iteration of the visuals, we would make minor adjustments. I would say “the people are too flat” and Derek would make 3D people, Angelo would say “the box is ugly” and would photoshop a potential box. Then Derek would take it and run with it. Eventually, after countless meetings and having way too many dreams about how to illustrate SCRUM, we were finally down the right path. The end results became this:

Page 1 of 2 | Next page