Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum ban

757 views

Published on

Scrum + Kanban

Published in: Technology

Scrum ban

  1. 1. Scrumban Taking Scrum outside it’s comfort zone
  2. 2. About Me • Agile Coach, Certified Scrum Practitioner, Certified Scrum Product Owner • 13 years experience leading R&D organizations (including VP R&D) focusing on System-level software and products. • Focusing on: – Change Management and effective Agile Transitions – Enterprise-scale Agility – Lean, Kanban, and agility for special circumstances – Using Retrospectives and Systems Thinking to identify and address deep issues with how product development organizations execute – Agile Management • Find me on: – yuval@agilesparks.com – @yuvalyeret – http://www.linkedin.com/in/yuvalyeret
  3. 3. TO DO IN PROGRESS DONE Why do we need to look outside Scrum? What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it?
  4. 4. Enterprise Project Development Scrum’s Comfort Zone Scrum Event-driven R&D
  5. 5. What is event-driven? • Helpdesk/Support activities (driven by cases opened by customers, under SLA)
  6. 6. What is event-driven? • Hardening/Packaging phases (driven by defects found in testing)
  7. 7. Backlog Pains • How do we manage the flow around the backlog? • How do we ensure we have enough analysis/stories ready for development? • How do we avoid preparing/analysing too many stories for the development to work on (Waste)? • We love the visibility Scrum provides us for the development lifecycle. How do we extend it to the backlog / story elaboration phases?
  8. 8. TO DO IN PROGRESS DONE Why do we need to look outside Scrum?What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it?
  9. 9. Kanban
  10. 10. Toyota Production System “The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation. The tool used to operate the system is kanban.” Taiichi Ohno, Toyota Production System (adopted 1962)
  11. 11. TO DO IN PROGRESS DONE Scrum Task Board Elad Inbar Mushon Inbar Elad Mushon
  12. 12. TO DO IN PROGRESS DONE What’s the problem? http://moduscooperandi.com Elad Inbar Mushon Inbar Elad Mushon Mushon Mushon Inbar Inbar Mushon Elad Inbar Inbar Inbar
  13. 13. TO DO IN PROGRESS DONE Late-binding, Multi-tasking limits http://moduscooperandi.com Inbar Elad Mushon Inbar Mushon Elad
  14. 14. TO DO READY (2) IN PROGRESS (5) DONE Voila! Kanban! http://moduscooperandi.comhttp://moduscooperandi.com
  15. 15. TO DO READY (2) IN PROGRESS (5) DONE Pull http://moduscooperandi.comhttp://moduscooperandi.com Mushon Mushon
  16. 16. TO DO READY (2) SPECIFY (2) EXECUTE (3) DONE Workflow
  17. 17. Throughput Work in Progress Throughput
  18. 18. Teamwork • Enhances Teamwork – Team focus on goals that add value not individual tasks • Encourages Swarming http://www.flickr.com/photos/markop/2523825358/
  19. 19. When Blocked… • Lower priority work… – Spikes – Analysis • Production Capability Improvement work… – Tool Automation – Refactoring – Personal Development – Innovation • But NOT – Anything which will create work downstream NOTE: This doesn’t mean you should ONLY “sharpen the knife” when Blocked!!!
  20. 20. Cumulative Flow Diagrams http://www.agilemanagement.net
  21. 21. TO DO IN PROGRESS (1) DONE Why do we need to look outside Scrum? What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it?
  22. 22. • Easier transition for Scrum teams/organizations – Step by step migration – see http://leansoftwareengineering.com/ksse/scrum-ban/
  23. 23. Team Cadence/Heartbeat
  24. 24. Board reset
  25. 25. TO DO IN PROGRESS (1) DONE Why do we need to look outside Scrum? What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it?
  26. 26. When should I use Kanban? Extend Scrum to the whole value stream – Upstream - Manage the Backlog process - All the steps preceding the actual development sprints – Downstream – Manage system testing, packaging, deployment
  27. 27. When should I use Kanban? • During hardening sprints • For the support/helpdesk teams/activities • For periods of heavy R&D
  28. 28. When should I use Kanban? • Another angle to start your transition from – Add visibility and WIP controls to current workflow – Inspect the constraints/bottelenecks – Adapt the workflow, resources, processes – Scrum It if it makes sense! – Drive for maximum throughput and fastest time to delivery – Repeat
  29. 29. TO DO IN PROGRESS (1) DONE Why do we need to look outside Scrum? What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it?
  30. 30. TO DO IN PROGRESS (1) DONE Why do we need to look outside Scrum? What is this Kanban/ Scrumban ? How does it complement Scrum? When would we want to use it? Detailed comparison between Scrum and Kanban How to manage in Kanban using TOC Kanban Release Planning Kanban and Commitment/ Velocity Flow of business value using Kanban Scrumban implementation Details Advanced Kanban Concepts
  31. 31. TO DO IN PROGRESS (1) DONE Detailed comparison between Scrum and Kanban How to manage in Kanban using TOC Kanban Release Planning Kanban and Commitment/ Velocity Flow of business value using Kanban Scrumban implementation Details Advanced Kanban Concepts
  32. 32. info@agilesparks.com, yuval@agilesparks.com Get the slides at http://www.slideshare.net/yyeret/ Ask us how
  33. 33. References and Material Scrumban - http://leansoftwareengineering.com/ksse/scrum-ban/ kjscotland@yahoo.co.uk http://availagility.wordpress.com aaron@sanders.name http://aaron.sanders.name/ http://groups.yahoo.com/group/kanbandev/

×