Downloaded 33 times
Uploaded byAGILEMinds
Sami honkonen scheduling work in kanban
This document discusses scheduling work using Kanban rather than Scrum at a Finnish telecom company developing a self-service channel for corporate customers. It had previously used Scrum for 3 years and transitioned to Kanban for the past 9 months. Key aspects of Kanban discussed include not having estimations, sprints, fixed teams or domain areas. The document emphasizes collaboration, transparency and pessimism as keys to success with Kanban scheduling.
More Related Content
Similar to Sami honkonen scheduling work in kanban
Sami honkonen scheduling work in kanban
- 1. Scheduling work in Kanban (Breaking the boundaries) Copyright Reaktor 2011
- 2. Sami Honkonen • Software development coach • Reaktor, Helsinki, Finland • 10 years in sw dev • 6 years of experience with Scrum • 9 months of experience with Kanban • Blog: http://www.samihonkonen.fi – Direct link: http://bit.ly/SchedulingWorkInKanban • Twitter: @shonkone
- 3.
- 5. Background • Customer: Finnishtelecom company • Product: self service channel for corporate customer • 3 years of Scrum, 9 months of Kanban • 25-30 people directly involved
- 8. ”Start with whatyou have”
- 9.
- 10.
- 11.
- 12.
- 13. We changed alot
- 15. ”When are yougoing to be working on my feature?!
- 22. Having a planthat changes is better than not having a plan
- 23. Collaboratively creating a plan is a an effective way of communicating the reasoning behind it
- 24. A transparent, visualized plan is a great way of communicating direction to developers
- 25. Keys to success • Collaboration • Transparency • Pessimism
- 26. Thanks! Interested in anarticle? Copyright Reaktor 2011