scrumday dk 2014: scrum, kanban, prince2, dos and donts
TRANSCRIPT
Scrum, Kanban & Prince 2dos and don’ts
Mads Troels Hansen
Scrumday Denmark, June 17th 2014
@MadsTH, [email protected]
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
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
Case: Using the Kanban MethodTeam 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
• More about “Change Management”
• Incremental Change
Kanban Method
You don’t change to the Kanban Method
Delivery vs.
Discovery
Predictivevs.
Empirical
Prince2
http://en.wikipedia.org/wiki/PRINCE2
PRojects IN Controlled Environments
7 principles - 7 Themes - 7 Processes
Prince2
http://en.wikipedia.org/wiki/PRINCE2
Scrum
ScrumScrum
Scrum
Scrum Scrum
Scrum
Delivery vs.
Discovery
Predictivevs.
Empirical