Agile and Lean Influences - Where did Kanban, Scrum, Scrumban and Lean Startup come from?

Agile and Lean Influences - Where did Kanban, Scrum, Scrumban and Lean Startup come from?

The following diagram summarizes in a very quick and visual way where Kanban, Scrum and Lean Startup got their inspiration. It is not just history; it also shows the dual nature of Kanban, the Agile and Lean influences that make it so powerful, and also how Scrum shares some Lean history.

Mr. Yasunobu Kawaguchi created the original diagram, and we have updated it with contributions from Agustin Villena and Joseph Hurtado. In particular we added Scrumban to the list, as well as the dates when critical books about a technique or methodology were released to the public. We hope this diagram makes your Agile and Lean learning much more rewarding. Kanban stands in the shoulders of giants.

At the AgileLion Institute we are also making our own contributions to Kanban: Open Kanban, and Kanban Ace. Kanban Ace is the first Open Kanban method, it combines the best of Agile with the power of Lean. If you are interested in our know-how we have a solid selection Kanban Ace classes worldwide.

Comments

Nice diagram.

I think the ordering of Scrumban and Kanban in the diagram is confusing and shows the weakness of only using the publication dates for books to place the methods on the diagram. Kanban is usually dated from the first conference presentation of the method which was Agile 2007 in Washington. Since Anderson and Ladas were working closely together at that time it's not surprising they were influencing each others publications.

Hi,

Great job!

Just a point, I don't understand the relationship from Design Patterns to Scrum and XP, what does it mean? why?

Regards

Nice diagram. It always easier to criticize than create. Your diagram is very close. I am not sure these mentions below should be noted and where you do it since simplification is almost always better.

My additional thoughts:

Lean Startup: In earlier writings Eric mentioned Boyd's OODA Loop a lot. The OODA Loop has gone on to influence just about everyone that discusses agility and adaptability.

Omitting Dr. Deming seems to be a shame. Not only was he the main influence upon Toyota but his work had significant impact on the Lean Software community outside of Toyota. I believe Dr. Deming was the main influence on making Lean successful in the knowledge (software) field. Without his contributions Lean may have stayed bogged down in manufacturing.

Under the Agile name, I think recognition (thought it has taken a lot of criticism) of the Agile Manifesto would seem appropriate. The main principles of the manifesto are still widely quoted and serve as a basis for the other links.

Anderson's Kanban was heavily influenced by Goldratt's Theory of Constraints. David's first book was based on TOC. You could argue that traditional Kanban influenced the visibility (card, board, pull) but the limiting WIP was a result of TOC.

I think you did a great job but thought I would add my 2 cents.

I think this is a great resource, and using the dates of significant publications helps get rid of some of the subjectivity.

Historical accuracy is important I think. I came to know about the Japanese manufacturing industry through JIT ERP and value Engineering (Late 80's early 90's) and then later TQM (Mid 90's).

The next big influence om myself was Smalltalk and the "Smalltalk Way" leading me into OO and the Patterns Movement (OOPSLA, PLoP) and finally Extreme Programming and then Scrum in around 2003.

Agiles roots in the Japanese way of thinking was always clear to me, and was re-enforced when I read The New New Product Development Game, published in 1986! I always saw Agile as Japanese thinking applied to New Product Design (specifically Software Products with XP).

Then later, around 2005, I came across the work of the Poppendieks which I viewed as revisiting those Agile roots in Japanese Manufacturing and Design to see if there was anything else that could be gleamed, and there were. Concurrent Design comes to mind.

It's a shame that in recent years it has become popular to tout "Lean" and "Lean Thinking" as a new alternative to Agile. I've even heard people describe it as Agile 2.0. For me this is to turn the historical chronology on its head. Agile grew out of Lean, and to set them up as some how different is to not understand the roots of Agile at all.

Thanks for setting the record straight. BTW, I've mentioned on or two things that you could add, like Smalltalk, but the diagram is fine as it is.

Well done!

Nice diagram Joseph, but I'm a bit surprised there's not a literary reference to Womak, et al, for "The Machine That Changed The World" between Toyota / Lean manufacturing and Lean.

Thank you for using the diagram I created. I am very honer!
And author names and published years are really really great. I love it!

I also considered adding TOC and some technologies, I know these importance, but this diagram is just for describing the roots of Agile and Lean. So, I decided to omit these and have kept it simple.

This is a good overview. Would you think that "Lean IT" book (Orzen/Bell) belong here, too?