Goals

• You have a better understanding what Kanban is.
• You have a better understanding of how to apply it.

History

• Toyota 1940s by Taiichi Ohno
• Experimented to adopt to Software development in 2000s by David Anderson
• Pull based system
• Translates to "visual signals"

What is Kanban in Our World?

• Lightweight framework
• No prescription in roles, activities
• Easily adapts to frequent changes such as outside influences
• Well suited for stand off single units of work or repetitive unit work
• Requires maturity on team’s part for certain types of projects
• WIP limits reduce context switching - saving us time, attention, and energy
• Breaks down complex work into "sashimi slices", making it easier to get done
• Helps with creating more predictable outcomes and output
• Helps identity bottle neck and where we can increase throughput
• Help evaluate impact of process changes
• Each columns are each different steps of your process to ship item to done