Embed Size (px)
DESCRIPTION
Citation preview
Scheduling work in Kanban
Copyright Reaktor 2011
(Breaking the boundaries)
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
Experience report
Background
• Customer: Finnish telecom company
• Product: self service channel for corporate customer
• 3 years of Scrum, 9 months of Kanban
• 25-30 people directly involved
”Start with what you have”
No estimation
No sprints
No teams
No fixed domain areas
We changed a lot
”When are you going to be working on
my feature?!
Having a plan that changes is better than not having
a plan
Collaboratively creating a plan is a an effective way
of communicating the reasoning behind it
A transparent, visualized plan is a great way of
communicating direction to developers
Keys to success
• Collaboration
• Transparency
• Pessimism
http://www.samihonkonen.fi http://bit.ly/SchedulingInKanban
@shonkone [email protected]
Thanks!
Copyright Reaktor 2011
Interested in an article?
