From Scrum to Kanban and Back
After two years of doing Scrum for one of our teams, we needed to be very fluid for the two months leading up to a major event. The answer? Run using Kanban for those two months. In this talk, we'll describe why we decided to make this change, and then why we decided to go back to Scrum afterward.
Outline/Structure of the Talk
1. The challenge we faced
2. The decision-making process
3. Implementing the switch to Kanban
4. Running kanban
5. Should we switch back to Scrum?
6. Thoughts on the whole experience
You'll come away from this with an ability to recognize when Scrum might not be the best choice for your particular situation.
Anybody who has felt that two-week sprints are too long in some situations.
Prerequisites for Attendees
A prerequisite is that you understand the basics of Scrum. No prior Kanban knowledge needed.
I spoke at AgileDC 2015 on the topic of distributed development using Scrum. We continue to be an agile, distributed development team, and our experimentation with Kanban is part of our initiative to constantly improve the way we build and deliver software.