Kanban System

kan = visual
ban = card

Invented at Toyota as a scheduling system for just-in-time manufacturing.

Evolved to system that track work in process and optimize workflow

• what to produce
• when to produce
• how much to produce

Kanban system combine practices of Lean Thinking and Theory of Constraint

Goal

Make the work flow fast through the whole value chain, from idea or concept to software in production.

Principles

• Visualize
• Limit WIP
• Manage continuous flow
• Make process policies explicit: based on objective data
• Implement feedback loop: operation review
• Improve collaboratively, evolve experimentally:
  - using models and the scientific method
  - can include Theory of Constraints model
  - can include Lean methods

Visual system

Visualize the flow

WIP in knowledge work isn't visual and this is the driving force behind wanting to visualize work.

• Single point of access for the organisation
• Map of our works
• Bring understanding of our system immediately and intuitively
• Explicit about:
• roles
• responsibilities
• policies
• WIP
• rate of completion
• structure of our process
• impediments.
• Dissolve division between the department of the organisation