AgileFever is a digital transformation consulting firm headquartered in Texas that provides Agile, DevOps, and Kanban training and coaching services globally. The presentation introduces Kanban, including its history starting in 1956 at a Toyota plant. It describes Kanban principles like limiting work in progress, managing flow, and implementing feedback loops. Key Kanban practices and events like daily stand-ups and retrospectives are also outlined. The presentation concludes with discussing common Kanban metrics like cycle time, work in progress, and throughput.
2. www.agilefever.com
Agenda
1 Brief Intro of AgileFever and Team
2 What is Kanban and History
3
4
5
6
7 Q & A
Kanban Principles
Kanban Practices
Kanban Events
Kanban Metrics
5 mins
5 mins
10 mins
15 mins
5 mins
10 mins
10 mins
3. www.agilefever.com
• AgileFever is a one-stop-shop for you digital Transformation services.
• We are headquartered in Texas USA and serving across the globe and growing quickly.
United States India Australia Europe China
Canada
8. www.agilefever.com
Introduction and History of Kanban-
• Written 看板 in Kanji (Chinese characters), kanban means “sign” or “large visual board”
• Written かんばん in Hiragana (the Japanese alphabet), kanban means “signal card(s)”
• Was discovered by Taiichi Ohno in 1956
Taiichi Ohno
9. www.agilefever.com
Kanban Method: Change Management Principles
Start with what you do now
•Understanding current processes, as actually practiced
•Respecting existing roles, responsibilities, and
job titles
Gain agreement to pursue improvement through
evolutionary change
Encourage acts of leadership at all levels
Understand and focus on the customer's needs and expectations
Manage the work; let workers self-organize around it
Regularly review the network and its policies to improve outcomes
Kanban Method: Service Delivery Principles
Kanban Principles -
10. www.agilefever.com
Show work and its flow.
Visualize risks.
Build a visual model that reflects how you
actually work.
visualize
Stop starting, start finishing!
Left yields to right.
Limit work in
the system to available capacity.
“Flow“ is the movement of work.
Manage the work towards smooth,
predictable delivery.
Use data.
Implement feedback loops
at an appropriate cadence.
Foster collaboration, learning, and improvements. Data-
driven.
Using the scientific method.
Hypothesis-driven change.
Run safe-to-fail experiments.
Limit Work in Progress Manage Flow
Implement Feedback Loops Improve Collaboratively,
Evolve Experimentally
6 Kanban Practices
• WIP Limits
• Classes of Service
• Dependencies
• Working agreements
• blocker handling
• Have agreed policies,
• visible to everyone involved
Make Policies Explicit