Started with Toyota, learning from supermarket.
Just-in-time production.
Kanban card for super clear communication.
Visualize work (we interpret images 60 000 times faster than text, 90 % of all information to brain are images). Leads to increased communication and collaboration. Seeing is believing.
Limit work in process (W.I.P). Reduces time for one item to get finished, and reduces the need to constantly reprioritize items.
Focus on flow using team-driven policies. Pull, don’t push! You can see and predict problems in the work flow easier.
Continuous improvement. Measure effectiveness by tracking flow, quality, throughput, lead times and more. Identify problems/possibilities and experiment with changes to drive improvements.
More adaptive than Scrum, which needs to be “hacked” to allow support/maintenance.
When to use a flow rather than planning?
Work is unclear.
Blocked work – impeded.
Work can’t be estimated.
Technical debt.
Much unplanned work.
Parked work – too much half-finished, too many interruptions etc.
Requirements change often.
Planning with Kanban on a management level
Measure lead time and extrapolate. Find good KPIs (key performance indicator) for quality and effectiveness etc.
Impediments that need management attention or decisions are made clear.
Use W.I.P. limits to keep focus and guarantee (some) results.
