Kanban and the New New Product Development Game

One of the primary origins of Scrum is “The New New Product Development Game” by Hirotaka Takeuchi and Ikujiro Nonaka, published in the Harvard Business Review in 1986.  This is the article in which the contrast is made between a traditional sequential or “relay race” approach and a holistic or “rugby” approach. Hence  the name Scrum was derived.  As part of their explanation of the differences between the approaches, the authors describe three types of approach:

  • Type A – single phases, proceeding exactly sequential
  • Type B – single phases, overlapping at their borders
  • Type C – multiple phases, overlapping each other

Phase Types

The Type C diagram was in my mind when I was putting together the diagrams towards the end of The Anatomy of an MMF, and I think this approach actually describes a Kanban based approach pretty accurately, where we recognise and allow phases to exists as necessary, but at the same time encourage whole team collaboration.

Jeff Sutherland has also reinterpreted the classifications to describe how Scrum’s Sprints progress:

  • Type A – single Sprints, proceeding exactly sequential
  • Type B – single Sprints, overlapping at their borders
  • Type C – multiple Sprints, overlapping each other

Another way of describing this evolution could be to say that Type C is multiple, overlapping MMFs, where each MMF is variable length and not time-boxed.  Its worth noting that The New New Product Development Game makes no mention of time-boxes!

4 Comments

  1. That is too awesome. It’s been so long that I read that paper that I forgot how much bullshit had been added by the CSM crowd.

    No timeboxes. No Scrummasters. Overlapping phases. “Division of labor works well in a Type A system.”

  2. […] Kanban and the New New Product Development Game « AvailAgility […]

  3. […] that Scrum Type C is quite similar to what we are discussing. And I also came (again) across Kanban and the New New Product Development Game | AvailAgility which discusses MMFs and Scrum Type C and talks more or less about our direction […]

  4. […] let us design our own packages through a game!  The principle of gaming underpins the concept of Kanban, a popular software development technique – which helps people interact to develop […]

Comments are closed.