6. Kanban
(1) http://en.wikipedia.org/wiki/Kanban
Kanban (かんばん(看板) is a scheduling system
for Lean and just-in-time (JIT) production1
Scrum: Manage complex work
• Organizing for value
Kanban: Manage complicated work
• Organizing for flow
Delivery
vs.
Discovery
Kanban (System)
Predictive
vs.
Empirical
7. Kanban Method
Foundational Principles
• Start with what you do now
• Agree to pursue evolutionary change
• Initially, respect current roles, responsibilities & job titles
• Encourage acts of leadership at all levels
Core Practices
• Visualise
• Limit work in progress (WIP)
• Manage Flow
• Make Process Policies Explicit
• Implement feedback loops
• Improve collaboratively, evolve experimentally
Source: http://www.leankanbanuniversity.com/kanban-method
8. Case: Using the Kanban Method
Team not using Scrum
• Board visualizing work
• A team
• A facilitator in the team
• WIP limit on people in the team
• Backlog with a owner
• Daily stand-up meeting
• Definition of Done
• Ready state
• Agreed on how to manage requests
• Retrospectives biweekly
9. • More about “Change Management”
• Incremental Change
Kanban Method
You don’t change to the Kanban Method
Delivery
vs.
Discovery
Predictive
vs.
Empirical
14. Summary
You don’t change to the Kanban Method
Delivery vs. DiscoveryPredictive Empirical
When applying tactics and processes with Scrum
2014, Mads Troels Hansen (@MadsTH)www.Teamdriven.dk
A kanban system alone is more about delivery and flow
Scrum in Prince2 is NOT only about delivery