Teams play timed rounds of a simple game, and between the first two rounds the number of pieces of work passed on at once changes. They see for themselves how soon the first and last pieces of work reach the end.
Once they have played, participants learn what Kanban is and how to get work from start to finish without waiting. They also learn Little’s Law, a rule that links how much work is under way, how long each piece takes and how many pieces finish. It describes what has already happened; it does not predict.
Teams run a simulation of a team’s work on a Kanban board twice, and keep their own charts from both rounds showing how long each piece took to finish and how long unfinished pieces had been waiting. After each round they discuss it, first how it felt, then what their charts show.
Teams list the moves they used to keep work moving and stop items sitting unfinished for too long. Then they pick out, in the simulation they just played, the parts every Kanban system must have: what counts as a piece of work, where it starts and finishes, the stages, the cap on work in progress, and the agreed rules.
Each participant writes down how their own work really flows today, rather than copying their current Kanban board (the wall or screen where a team tracks each piece of work), if they have one, which rarely shows it. The sheet covers where work starts and finishes, the stages in between, the rules the team has agreed for how work moves, and how long a piece of work should usually take.
Participants learn to measure how much work is under way, how long pieces take, how many finish and how old unfinished pieces are, and what Little’s Law can and cannot tell them. They learn which numbers warn early and which only confirm after the event, and they practise reading a chart of how long pieces took to finish.
Groups visit example Kanban boards showing familiar failures, such as the cap on work started being ignored or finished work piling up, and work out what to ask the team, not what to tell them. In a case study, the reports say all is well while stakeholders say the team is unresponsive, and participants find that no single number tells the whole story.
Participants give advice on prepared problems and, in the eight-session format or where time allows, bring their own real problems for their peers to help with. They leave with guidance on preparing for the Professional Kanban I (PK I) certification assessment from ProKanban.org.