Scaling Scrum in the Enterprise with Kanban

2,624 views

Published on

We look at how Kanban can be used to enhance Scrum at the enterprise level.
Enterprises often work with large or complex projects that require the cooperation of several Scrum teams.
As synchonization between teams becomes crucial, we look at how Kanban can enhance the Scrum-of-Scrums to acheive control and sustainability.

Published in: Technology

Scaling Scrum in the Enterprise with Kanban

  1. 1. Scaling Scrum in the Enterprise with Kanban Agila Sverige, 2010-05-11 Christophe Achouiantz Agile/Lean Coach
  2. 2. First project with Scrum: Success! SM Development • 1 team PO Team • Best team • Low risk project Christophe Achouiantz
  3. 3. Let’s roll-out Scrum in the Enterprise! What could possibly go wrong? Project • Large project or CIO • Whole department Manager CM Architect Team 1 Team 2 Team 3 Team n Christophe Achouiantz
  4. 4. Dependencies! Hand-overs Code Project Manager API Specialists CM Architect Functions Timing Team 1 Team 2 Team 3 Team n Christophe Achouiantz Components
  5. 5. Problems with several Scrum teams • What’s our status? How are we doing? • What is slowing us down (problems)? • What will slow us down (risks)? • What can I do as project manager / product owner / line manager to help? Christophe Achouiantz
  6. 6. Solution: Scrum-of-Scrums? • Hard to get it right - Quickly degenerates in status report • Focus on immediate issues • Hard to understand the whole picture Christophe Achouiantz
  7. 7. What we need • Understand how the work Map value stream flows (dependencies) • Visualize the work, Visualize value impediments, bottlenecks to stream identify problems and risks • Focus on what is top priority Limit WIP Kanban? Christophe Achouiantz
  8. 8. Enhance the Scrum-of-Scrums with Kanban Christophe Achouiantz
  9. 9. Scaling Scrum with Kanban 1. Create an organization of Scrum teams that map to the value stream (you might realize that you miss some teams) 2. In doing so, you define a process 3. Visualize the organization and process Christophe Achouiantz
  10. 10. Create an organization of Scrum teams that map to the value stream Dev. Team Dev. Team Idea PO Team Dev. Team Integration Team Product Dev. Team Dev. Team Christophe Achouiantz
  11. 11. Organization may need to be complex Dev. Team PO Integration Team Team Dev. Team Ideation Dev. Integration Production Team Team Team Team PO Dev. Integration Team Team Team Dev. Team Christophe Achouiantz
  12. 12. Visualize Organization and Process To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Dev. Team 3 Dev. Team 4 Christophe Achouiantz
  13. 13. Visualize Organization and Process To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Process Dev. Team 2 Organization Dev. Team 3 (Teams) “Work” Dev. MMFs,feature, Team 4 functions, activities Christophe Achouiantz
  14. 14. Visualize Organization and Process To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Team’s direct Team’s responsibility activities (e.g. defects) Dev. Team 3 Dev. Team 4 Christophe Achouiantz
  15. 15. Identify Bottlenecks To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Dev. Team 3 Dev. Team 4 Christophe Achouiantz
  16. 16. Identify Type of Work Release 1.2 MMF 2322 Project A As a pension saver, I want to browse my account history Date Started Ideation Integration Design Pre-prod Dev. Done! Christophe Achouiantz
  17. 17. Visualize Type of Work To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Dev. Project A Team 3 Release 1.1 Dev. Team 4 Christophe Achouiantz Support/Maintenance
  18. 18. Visualize Impediments To Dev. & Inte- Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Dev. Team 3 Dev. Team 4 Christophe Achouiantz
  19. 19. Limit WIP to shorten Lead-times 4 To Dev. & 5 Inte- 3 Pre- Ideation Design Ready! Do Test gration prod Dev. Team 1 Dev. Team 2 Dev. Team 3 Dev. Team 4 Christophe Achouiantz
  20. 20. Visualization over time • Can show variations over time - release - project Kanban board gives us - MMF rich data that can be - team used as leading indicator - steps in the process • WIP, Lead-times, cycle-times (Cumulative Flow Diagrams) • Impediments Christophe Achouiantz
  21. 21. WIP and Lead-times over time Cumulative Flow Diagram (CFD) Can be done for each: team, release, project or MMF! To Do Lead-time Design Development & Test PreProd Integration Ready Sprints under Release
  22. 22. WIP and Lead-times over time Cumulative Flow Diagram (CFD) 300 300 200 200 100 100 0 0 1 2 3 4 1 2 3 4 Whole IT Release 1.2 300 300 300 300 200 200 200 200 300 100 100 100 100 200 0 0 1 02 3 4 1 0 2 100 4 3 1 2 3 4 1 2 3 4 0 Projects in Release 1.2 Teams 1 2 3 4 Christophe Achouiantz
  23. 23. Impediments over time Can be done for each: team, release, project or MMF! 10 Oops! Let’s do something 8 about it Impediments 6 Much better! 4 Thanks for the help 2 0 1 2 3 4 5 6 7 8 9 10 Weeks Christophe Achouiantz
  24. 24. Using Kanban on top of Scrum gives good decision-making • Gives a truthful, factual status • Visible for anyone: anyone can help! • Rich data gives leading indicators - Identifies risks & problems ASAP • Limit work in progress to what is prioritized Christophe Achouiantz
  25. 25. Good decision-making gives Control Christophe Achouiantz
  26. 26. Control gives Scalability Adding new teams becomes cheaper, as coordination and synchronization is now cheaper Christophe Achouiantz
  27. 27. Thank you! Did you know? Scrum can be used to scale Kanban... Ask me! christophe.achouiantz@avegagroup.se Blog: http://blog.avegagroup.se/ChristopheAchouiantz Twitter: ChrisAch Christophe Achouiantz

×