Scrum to Scrumban Migration
5 likes2,202 views
This document describes one team's transition from Scrum to Kanban or "Scrumban". It outlines their typical Scrum process, including daily standups and weekly planning and retrospectives. It then discusses how they experimented with different work in progress limits on their Kanban board and the problems they encountered, such as bottlenecks. Finally, it notes how their process evolved more naturally over time with continuous improvement and that they retained stakeholder demos and retrospectives as needed rather than having fixed weekly meetings.
Scrum to Scrumban Migration
- 1. Scrum to Scrumban Confessions of a Kanban Virgin Chris Pitts Thursday, 11 March 2010
- 2. Scrum to Scrumban • How things were working & the problems • How to change • Pros and Cons • What next? Thursday, 11 March 2010
- 3. The starting point 1 week Thursday, 11 March 2010
- 4. A typical week •Every day standup •Every week Stakeholder demo Retrospective Planning Game Thursday, 11 March 2010
- 5. Thursday, 11 March 2010
- 6. Thursday, 11 March 2010
- 7. Q. How many columns? Thursday, 11 March 2010
- 8. Q. What are our WIP Limits? • 6 developers, 1 QA • Interested in limited pairing • Need to find the “Goldilocks Value” Thursday, 11 March 2010
- 9. Option 1 - 7 in flight Thursday, 11 March 2010
- 10. Option 2 - 4 in flight Thursday, 11 March 2010
- 11. Option 2 - 4 in flight Thursday, 11 March 2010
- 12. The Initial Board Thursday, 11 March 2010
- 13. Problems! WIP Violation Thursday, 11 March 2010
- 14. Problems! WIP Violation Thursday, 11 March 2010
- 15. Problems! BLOCKED! Thursday, 11 March 2010
- 16. Problems! BLOCKED! Thursday, 11 March 2010
- 17. Cycle Time Thursday, 11 March 2010
- 18. Cycle Time Thursday, 11 March 2010
- 19. Evolution Thursday, 11 March 2010
- 20. Side Effects • Weekly stakeholder demos retained • Weekly retrospectives retained • Team and Product Owner conversations happened naturally & frequently Thursday, 11 March 2010
- 21. Side Effects • Weekly stakeholder demos retained • Weekly retrospectives retained • Team and Product Owner conversations happened naturally & frequently • Confusion over how to explain to external Gantt chart fetishists... Thursday, 11 March 2010
- 22. Natural Evolution • Instead of holding weekly formal retrospectives, retrospect and fix problems as they happen. “KAIZEN” Thursday, 11 March 2010
- 23. Where are they now? Thursday, 11 March 2010
- 24. Questions? Thursday, 11 March 2010
- 25. Thursday, 11 March 2010