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

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…