Scheduling work in     Kanban  (Breaking the boundaries)        Copyright Reaktor 2011
Sami Honkonen•    Software development coach•    Reaktor, Helsinki, Finland•    10 years in sw dev•    6 years of experien...
Experience  report
Background•  Customer: Finnish telecom company•  Product: self service channel for corporate   customer•  3 years of Scrum...
”Start with what you have”
No estimation
No sprints
No teams
No fixeddomain 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
Thanks!Interested in an article?     Copyright Reaktor 2011
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Sami honkonen   scheduling work in kanban
Upcoming SlideShare
Loading in …5
×

Sami honkonen scheduling work in kanban

1,445 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,445
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sami honkonen scheduling work in kanban

  1. 1. Scheduling work in Kanban (Breaking the boundaries) Copyright Reaktor 2011
  2. 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. 3. Experience report
  4. 4. 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
  5. 5. ”Start with what you have”
  6. 6. No estimation
  7. 7. No sprints
  8. 8. No teams
  9. 9. No fixeddomain areas
  10. 10. We changed a lot
  11. 11. ”When are you going to be working on my feature?!
  12. 12. Having a plan that changes is better than not having a plan
  13. 13. Collaboratively creating a plan is a an effective way of communicating the reasoning behind it
  14. 14. A transparent, visualized plan is a great way of communicating direction to developers
  15. 15. Keys to success •  Collaboration •  Transparency •  Pessimism
  16. 16. Thanks!Interested in an article? Copyright Reaktor 2011

×