The three rules (in my head)
- Visualize the workflow
- Limit Work In Progress (WIP)
- Measure the lead time
The closest source: Kanban and Scrum, making the most of both
Next up: Crisp's homepage
At Toyota, Kanban is the term used for the visual & physical signaling system that ties together the whole Lean Production system. Most agile methods such as Scrum and XP are already well aligned with lean principles. In 2004, however, David Anderson pioneered a more direct implementation of Lean Thinking and Theory of Constraints to software development. Under the guidance of experts such as Don Reinertsen, this evolved into what David called a ”Kanban system for software development”, and which most people now simply refer to as ”Kanban”.Wow, a pioneer, David Anderson seemed as a promising track to research further!
David Anderson, a pioneer
Kanban uses five core properties to create an emergent set of Lean behaviors in organizations. These properties have been present in every succesful implementation, including the one at Microsoft described in chapter 4.The five properties are:
- Visualize Workflow
- Limit Work-in-Progress
- Measure and Manage Flow
- Make Process Policies Explicit
- Use Models to Recognize Improvement Opportunities
What the two "new" Kanban properties means
Common models in use with Kanban includes the Theory of Constraints, Systems Thinking, an understanding of variability through the teachings of W. Edwards Deming, and the concept of muda (waste) from the Toyota Production System. The models used with Kanban are continually evolving, and ideas from other fields, such as sociology, psychology, and risk management are appearing in some implementations.
Why were they dropped?
Others have been pondering this too in Kanban in Action
messier! But also revealed interesting info.
The three basic principles we describe in this section make up the foundation that kanban is based on. Recently, David J. Anderson and others have extended the three basic principles to five properties and later six practices; these are now referred to as the core practices.
Anyway, this info and Google led me to David Anderson's latest defintion, called Principles and General Practices of Kanban.
A blog post about Principles and General Practices of Kanban
Since the book was published, we’ve expanded this list and they are now known as the Principles and General Practices of Kanban.
Principles of the Kanban Method …
- Start with what you do now
- Agree to pursue incremental, evolutionary change
- Respect the current process, roles, responsibilities & titles
- Encourage acts of leadership at all levels in your organization
- Visualize (the work, workflow and business risks)
- Limit WIP
- Manage Flow
- Make Process Explicit
- Implement Feedback Loops
- Improve Collaboratively, Evolve Experimentally (using models & the scientific method)