Downloaded 1,343 times
Uploaded byYuval Yeret
Kanban/Scrumban - taking scrum outside its comfort zone
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.
More Related Content
Similar to Kanban/Scrumban - taking scrum outside its comfort zone
![Governance, Deployment & Methodologies for Agentic Automation [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day2-251112135038-a386476d-thumbnail.jpg?width=640&height=640&fit=bounds)
Kanban/Scrumban - taking scrum outside its comfort zone
- 1. ScrumbanTaking Scrum outsideit’s comfort zone
- 2. About MeAgile Coach,Certified Scrum Practitioner, Certified Scrum Product Owner13 years experience leading R&D organizations (including VP R&D) focusing on System-level software and products. Focusing on:Change Management and effective Agile TransitionsEnterprise-scale AgilityLean, Kanban, and agility for special circumstancesUsing Retrospectives and Systems Thinking to identify and address deep issues with how product development organizations executeAgile Management Find me on:[email protected]@yuvalyerethttp://www.linkedin.com/in/yuvalyeret
- 3. Why do weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How does it complementScrum?
- 4. Scrum’s Comfort ZoneEvent-drivenScrumEnterpriseProject DevelopmentR&D
- 5. What is event-driven?Helpdesk/Supportactivities (driven by cases opened by customers, under SLA)
- 6. What is event-driven?Hardening/Packagingphases (driven by defects found in testing)
- 7. Backlog PainsHow dowe 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 weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How does it complementScrum?
- 9.
- 10. Toyota Production System“Thetwo 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.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. TeamworkEnhances TeamworkTeam focuson goals that add value not individual tasksEncourages Swarminghttp://www.flickr.com/photos/markop/2523825358/
- 19. When Blocked…Lower prioritywork…SpikesAnalysisProduction Capability Improvement work…Tool AutomationRefactoringPersonal DevelopmentInnovationBut NOTAnything which will create work downstreamNOTE: This doesn’t mean you should ONLY “sharpen the knife” when Blocked!!!
- 20.
- 21. Why do weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How does it complementScrum?
- 23. Easier transition forScrum teams/organizationsStep by step migration – see http://leansoftwareengineering.com/ksse/scrum-ban/
- 24.
- 26.
- 27. Why do weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How does it complementScrum?
- 28. When should Iuse Kanban?Extend Scrum to the whole value streamUpstream - Manage the Backlog process - All the steps preceding the actual development sprintsDownstream – Manage system testing, packaging, deployment
- 29. When should Iuse Kanban?During hardening sprintsFor the support/helpdesk teams/activitiesFor periods of heavy R&D
- 30. When should Iuse Kanban?Another angle to start your transition fromAdd visibility and WIP controls to current workflowInspect the constraints/bottelenecksAdapt the workflow, resources, processes – Scrum It if it makes sense!Drive for maximum throughput and fastest time to deliveryRepeat
- 31. Why do weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How does it complementScrum?
- 32. Why do weneed to look outside Scrum? When would we want to use it?What is this Kanban/Scrumban? How to managein Kanban using TOCKanban Release PlanningKanban and Commitment/ VelocityFlow of business value using KanbanScrumbanimplementation DetailsAdvanced Kanban ConceptsHow does it complementScrum?Detailedcomparison between Scrum and Kanban
- 33. Kanban Deep Dive…ComingSoon…How to managein Kanban using TOCKanban Release PlanningKanban and Commitment/ VelocityFlow of business value using KanbanScrumbanimplementation DetailsAdvanced Kanban ConceptsDetailedcomparison between Scrum and Kanban
- 34. Ask us [email protected],[email protected] the slides at http://www.slideshare.net/yyeret/
- 35. References and MaterialScrumban- http://leansoftwareengineering.com/ksse/scrum-ban/[email protected]://[email protected]://aaron.sanders.name/http://groups.yahoo.com/group/kanbandev/
Editor's Notes
- #5 Scrum doesn’t