Kanban (development)

The Kanban Method

The name 'Kanban' originates from Japanese, and translates roughly as "signboard". Kanban traces back to the early days of the Toyota production system. Taiichi Onho developed 1940/1950 kanbans to control production between processes and to implement Just In Time (JIT) manufacturing at Toyota manufacturing plants in Japan. The Kanban Method as formulated by David J. Anderson^[2] ^[3] is an approach to incremental, evolutionary process and systems change for organizations. It uses a work-in-progress limited pull system as the core mechanism to expose system operation (or process) problems and stimulate collaboration to continuously improving the system. One example of such a pull system, is a kanban system, and it is after this popular form of a work-in-progress limited pull system that the method is named.

The Kanban Method is rooted in these basic principles:

Start with what you do now: The Kanban Method does not prescribe a specific set of roles or process steps. There is no such thing as the Kanban Software Development Process or the Kanban Project Management Method. The Kanban Method starts with the roles and processes you have and stimulates continuous, incremental and evolutionary changes to your system.

Agree to pursue incremental, evolutionary change: The organization (or team) must agree that continuous, incremental and evolutionary change is the way to make system improvements and making them stick. Sweeping changes may seem more effective but more often than not fail due to resistance and fear in the organization. The Kanban Method encourages continuous small incremental and evolutionary changes to your current system.

Respect the current process, roles, responsibilities & titles: It is likely that what the organization currently does has some elements that work acceptably and are worth preserving. We must also seek to drive out fear in order to facilitate future change. By agreeing to respect current roles, responsibilities and job titles we eliminate initial fears. This should enable us to gain broader support for our Kanban initiative. Perhaps presenting Kanban against an alternative more sweeping approach that would lead to changes in titles, roles, responsibilities and perhaps the wholesale removal of certain positions will help individuals to realize the benefits.

The 5 Core Properties

In his book, Kanban - Successful Evolutionary Change for your Technology Business , David Anderson identified 5 core properties that had been observed to be present in each successful implementation of the Kanban Method.

1. Visualize the workflow

The workflow of the knowledge work of today is inherently not visible as it is “hidden” in information systems. Visualizing the flow of work and making it visible is core to building an understanding how work works. Without understanding the workflow making the right changes is harder. A common way to visualize the workflow is to use a card wall with cards and columns. The columns on the card wall representing the different states or steps in the workflow and the cards the feature/story/task/result of the workflow.

2. Limit WIP

Limiting work-in-progress implies that a pull system is implemented on parts or all of the workflow. The pull system will act as one of the main stimuli for continuous, incremental and evolutionary changes to your system. The pull system can be implemented as a kanban system, a CONWIP system, a DBR system, or some other variant. The critical elements are that work-in-progress at each state in the workflow is limited and that new work is “pulled” into the new information discovery activity when there is available capacity within the local WIP limit.

3. Manage Flow

The flow of work through each state in the workflow should be monitored, measured and reported. By actively managing the flow the continuous, incremental and evolutionary changes to the system can be evaluated to have positive or negative effects on the system.

4. Make Process Policies Explicit

Until the mechanism of a process is made explicit it is often hard or impossible to hold a discussion about improving it. Without an explicit understanding of how things work and how work is actually done, any discussion of problems tends to be emotional, anecdotal and subjective. With an explicit understanding it is possible to move to a more rational, empirical, objective discussion of issues. This is more likely to facilitate consensus around improvement suggestions.

5. Improve Collaboratively (using models & the scientific method)

The Kanban Method encourages small continuous, incremental and evolutionary changes that stick. When teams have a shared understanding of theories about work, workflow, process, and risk, they are more likely to be able to build a shared comprehension of a problem and suggest improvement actions which can be agreed by consensus. The Kanban Method suggests that a scientific approach is used to implement continuous, incremental and evolutionary changes. The method does not prescribe a specific scientific method to use.

Common models used are:

The Theory of Constraints (the study of bottlenecks)
The System of Profound Knowledge (a study of variation and how it affects processes)
Lean Economic Model (based on the concepts of “waste” (or muda, muri and mura)).

References

^ "kanban". Random House Dictionary. Dictionary.com. 2011. http://dictionary.reference.com/browse/kanban. Retrieved April 12, 2011.
^ Anderson, David (September 2003). Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Prentice Hall. ISBN 0131424602.
^ Anderson, David (April 2010). Kanban. Blue Hole Press. ISBN 0984521402.