This document discusses Scrumban, which takes elements of Scrum and Kanban to address some of Scrum's limitations. Scrum works best for event-driven work like support/helpdesk activities, but Kanban can help manage upstream and downstream work from development sprints. Kanban uses pull-based workflow and limits work-in-progress to improve flow. It can be used to extend visibility and control outside of sprints. Scrumban combines the best of Scrum and Kanban for whole value stream management.

1. Scrumban Taking Scrum outside it’s comfort zone

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. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How does it complementScrum?

4. Scrum’s Comfort Zone Event-driven Scrum Enterprise Project Development R&D

5. What is event-driven? Helpdesk/Support activities (driven by cases opened by customers, under SLA)

6. What is event-driven? Hardening/Packaging phases (driven by defects found in testing)

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. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How does it complementScrum?

9. Kanban

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.” TaiichiOhno, Toyota Production System (adopted 1962)

11. Scrum Task Board Elad Inbar Mushon Inbar Elad Mushon

12. What’s the problem? Elad Inbar Mushon Inbar Elad Mushon Mushon Mushon Inbar Inbar Mushon Elad Inbar Inbar Inbar http://moduscooperandi.com

13. Late-binding, Multi-tasking limits Inbar Elad Mushon Inbar Mushon Elad http://moduscooperandi.com

14. Voila! Kanban! Inbar Elad Mushon Elad http://moduscooperandi.com http://moduscooperandi.com

15. Pull Mushon Mushon Inbar Elad Elad http://moduscooperandi.com http://moduscooperandi.com

16. Workflow Inbar Elad Mushon Inbar

17. Throughput

18. Teamwork Enhances Teamwork Team focus on goals that add value not individual tasks Encourages Swarming http://www.flickr.com/photos/markop/2523825358/

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. Cumulative Flow Diagrams http://www.agilemanagement.net

21. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How does it complementScrum?

23. Easier transition for Scrum teams/organizations Step by step migration – see http://leansoftwareengineering.com/ksse/scrum-ban/

24. Team Cadence/Heartbeat

26. Board reset

27. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How does it complementScrum?

28. 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

29. When should I use Kanban? During hardening sprints For the support/helpdesk teams/activities For periods of heavy R&D

30. 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

31. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How does it complementScrum?

32. Why do we need to look outside Scrum? When would we want to use it? What is this Kanban/Scrumban? How to managein Kanban using TOC Kanban Release Planning Kanban and Commitment/ Velocity Flow of business value using Kanban Scrumbanimplementation Details Advanced Kanban Concepts How does it complementScrum? Detailedcomparison between Scrum and Kanban

33. Kanban Deep Dive… Coming Soon… How to managein Kanban using TOC Kanban Release Planning Kanban and Commitment/ Velocity Flow of business value using Kanban Scrumbanimplementation Details Advanced Kanban Concepts Detailedcomparison between Scrum and Kanban

34. Ask us how info@agilesparks.com, yuval@agilesparks.com Get the slides at http://www.slideshare.net/yyeret/

35. References and Material Scrumban - http://leansoftwareengineering.com/ksse/scrum-ban/ kjscotland@yahoo.co.ukhttp://availagility.wordpress.com aaron@sanders.namehttp://aaron.sanders.name/ http://groups.yahoo.com/group/kanbandev/