© AgiliX Agile Development Consulting

看 , カン 板 , バン Kan Ban

30 min intro

Cesario Ramos

© AgiliX Agile Development Consulting

© AgiliX Agile Development Consulting

Focus on FLOW

Cycle Time = Work In ProgressAvg Completion Rate

(Little’s Law)

© AgiliX Agile Development Consulting

Overproduction

Delay

Hand-offsTask Switching

Defects

InventoryRelearning

Seeing WASTE

© AgiliX Agile Development Consulting

Why KanBan

• By reducing the WIP all kinds of WASTE will emerge.

• Bottlenecks in the process become clear.

• You’ll get an average cycle time.• You’ll get an average wait time.

© AgiliX Agile Development Consulting

Scrum v.s. KanBan

• Velocity• Sprint• WIP per sprint• Roles• Cannot

change sprint.• Item must fit

in sprint

• Cycle Time• No timebox• WIP per state • No Roles• Can change at

any time.• No timebox…

© AgiliX Agile Development Consulting | |

WIP and Cycle Time

Source: M Griffiths

© AgiliX Agile Development Consulting | |

Bottlenecks

Source: M Griffiths

© AgiliX Agile Development Consulting

© AgiliX Agile Development Consulting

One metric to rule them all

Lead Time =

CycleTime *

Work In Progress +

Delay Between Sub-Processes

© AgiliX Agile Development Consulting

Improve Kan Ban bottlenecks using A3

• Lead Time gives us a clear indication for potential wastes.

• Analyze waste to determine current situation

• Specify future state• Find root cause by walking the gemba• Propose counter measures for attacking

root cause.• Make a plan.• Sell it to management.

© AgiliX Agile Development Consulting

看 , カン 板 , バン Kan Ban

30 min intro