Kanban Weak Spots

7,520 views

Published on

Kanban is considered very light-weight yet very effective method helping teams to organize their work and make their flow effective but most importantly to foster continuous improvement. Cost of introducing Kanban is very low and usually first effects of its implementation show up pretty quickly. However it doesn't mean that Kanban will survive in any environment. The method has some weak spots, which a team should take care of, otherwise there can be little value of introducing it.

Addressing potential issues related to Kanban implementation is as crucial to its success as knowing its strengths. It is also very important to plan for those risks so a team can get much value out of introducing them method.

The presentation discusses a number of different Kanban weak spots, showing their negative effects and advising how they can be avoided which helps teams to make improvements fostered by Kanban sustainable.

Both: problems and solutions are based on real-life stories of teams facing issues connected with adopting Kanban.

Published in: Business, Technology
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
7,520
On SlideShare
0
From Embeds
0
Number of Embeds
4,447
Actions
Shares
0
Downloads
75
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Kanban Weak Spots

  1. 1. Kanban weak spots Pawel Brodzinski @pawelbrodzinski #lkce11
  2. 2. PEOPLE! With a special thanks to Katherine Kirk
  3. 3. But you change the system, not the people! With a special thanks to Bob Marshall
  4. 4. Thank youQuestions? Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski
  5. 5. Hi, I’m Paweland I’m happyto meet you hereVSofthttp://vsoft.plSoftware ProjectManagementhttp://blog.brodzinski.comTwitter@pawelbrodzinski
  6. 6. Let me introduce a party ofheroes...
  7. 7. I mean, another party of heroes
  8. 8. The partywanted tolevel up asthis is whatheroes do...
  9. 9. ...so theydecided to join the Kanban Guild
  10. 10. THE GOAL: Don’t fail with Kanban implementation
  11. 11. QUEST 1: The Kanban boardnot up to date
  12. 12. 2 3 2 1
  13. 13. 2 3 2 1
  14. 14. 2 3 2 1
  15. 15. 2 3 2 1
  16. 16. 2 3 2 1
  17. 17. Treat the board as the main source of information about the reality
  18. 18. Questcompleted!
  19. 19. QUEST 2:Abusedlimits
  20. 20. 2 3 2 1
  21. 21. 2 8 6 4
  22. 22. Make abusing limits painful
  23. 23. Questcompleted!
  24. 24. QUEST 3:Suddenly,the boardstood still
  25. 25. 2 3 2 1
  26. 26. 2 3 2 1
  27. 27. 2 3 2 1
  28. 28. 2 3 2 1
  29. 29. Create and exploit ocassions to change Kanban board
  30. 30. Questcompleted!
  31. 31. QUEST 4:Wishful I WISH WE HADthinking NO PROBLEMS WHATSOEVER IN OUR PROJECT…
  32. 32. 2 4 4 2
  33. 33. 2 4 2
  34. 34. Keep the board aligned with the reality, whatever it takes
  35. 35. Questcompleted!
  36. 36. QUEST 5:Over-engineers ahead!
  37. 37. 6 9 6 6
  38. 38. KISS (Keep It Simple Stupid)
  39. 39. Questcompleted!
  40. 40. QUEST 6: Kanban as Project Management or Software Development method
  41. 41. Learn and apply what you learned
  42. 42. Questcompleted!Level up!
  43. 43. Kanban is simpleBut it also meansit is fragile
  44. 44. Kanbanis like aflower...
  45. 45. And ifyou do,than well…
  46. 46. Thank youQuestions? Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski

×