Requirements Always ready to serve Small stories handled one at a time JIT planning Protect the other teams Staffed from different departments (doing service) Constantly learning and self-organizing But it could not be Scrum. No batch and deliver at all We had to find another model/process
From Scrum to Lean - looking at Toyota Sort of like a plant at Toyta One vehicle at a time Signaling needs for an item with a kanban system The Scrum board becomes a signaling system for JIT planing and delivery
KSSE We found a small bunch of people working with defining a process like this for software engineering Kanban System for Software Engineering Kanban System for Sustaining Engineering Focus: Use the visual signaling system as an engine to drive the process
Kanban properties (infoq) Physical: It is a physical card. It can be held in the hand, moved, and put into or onto something. Limits WIP: It limits WIP (Work-In-Process), i.e. prevents overproduction. Continuous Flow: It notifies needs of production before the store runs out of stock. Pull: The downstream process pulls items from the upstream process. Self-Directing: It has all information on what to do and makes production autonomous in a non-centralized manner and without micro-management. Visual: It is stacked or posted to show the current status and progress, visually. Signal: Its visual status signals the next withdrawal or production actions. Kaizen: Visual process flow informs and stimulates Kaizen. Attached: It is attached to and moves with physical parts supplied.
T3 kanban boardEmerg- ency 7 Work slot queues In Wait max State 12 tp DOD:ed this week To be planned Work In Done Process