Skip to main content

The Car that Scrum Built

You have heard the objections: "Scrum is great for software, but we're doing hardware." Or, "we're doing embedded. Scrum won't work here." Or, "Would you really build a bridge with Scrum?"

Well maybe not a bridge, but how about a car?

Remember the Ansari X PRIZE? The winner N328KF by Burt Rutan and Paul Allen is now the basis for Virgin Galactic's space tourism venture. In 2008, the Progressive Insurance Automotive X Prize competition put out a 10 Million Dollar prize for the first/best company to to produce a car that:
  1. you could actually drive on the street
  2. would achieve the equivalent of 100 mpg (2.35ltr/100km) and 200g/km well to road CO2 emmissions
  3. has a reasonably convincing plan for going into production by 2014.
Joe Justice, a soft-spoken Agilist, nerd and black belt kung-fu expert, was intrigued and, somewhat inadvertently, launched a Linux or Wikipedia-like project to create an entry in the class 'mainstream' (i.e. it should look like a car you would actually want to drive).

Three months later they had an entry. They didn't win, but they were number 10 (in a field that had declined from 136 entrants to 43 in the face of changing requirements). What was unique about this approach?
  1. Brilliant, knowledgeable people did this for fun in their spare time! Much like open source.
  2. They used Scrum as the management framework
  3. They used Pairing, Test Driven Development, Object Orientation, Refactoring and other XP practices to actually do the design and build the car.

I am not sure I can do justice to his talk in the scope of a blog article. I don't believe Joe's Scrum Gathering talk was filmed, but here is a similar talk he gave to the to the American Council of Engineering Companies Leadership Seminar in Cle Elum, WA. You can feel the next chapter of 'The Machine the Changed the World' being written as we watch:



Anonymous said…
They hardly used any Scrum practice in wikispeed. The title of blog is very misleading.
Peter said…
Joe's talk at the Scrum Gathering is now online. This talk describes more how they use Scrum.

You can find the videos on their video channel or jump directly to part 1 or part 2 of his talk.
Joe Justice said…
Thanks for commenting Anonymous! We build our cars using a product owner, a scrum master, a prioritized backlog, weekly sprints, a stand up meeting, demos, and sprint planning. Come check us out at:

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …