Beyond WIP Limits (Lean Kanban Tour Edition)

3,567 views
3,172 views

Published on

Beyond WIP Limits (Lean Kanban Tour Edition)

  1. 1. Beyond WIP limits Pawel Brodzinski @pawelbrodzinski
  2. 2. Hi, I’m PawelVSofthttp://vsoft.plSoftware ProjectManagementhttp://blog.brodzinski.comTwitter@pawelbrodzinski
  3. 3. Once upona time…
  4. 4. Why?
  5. 5. 100% utilization
  6. 6. Cost of multitasking Source: Gerald Weinberg, Quality Software Management: Vol. 1 System Thinking
  7. 7. Time to market
  8. 8. Catching up UM… HOW DOES THIS DARN CODE WORK, AGAIN?
  9. 9. Moremistakes Source: E. Ophir, C. Nass, A. Wagner:Cognitive control in media multitaskers
  10. 10. On a highway
  11. 11. In a call center
  12. 12. On a computer
  13. 13. At a conference
  14. 14. Ball FlowGame
  15. 15. No WIP Limits
  16. 16. Using WIP Limits
  17. 17. Total time: 26% betterAverage cycle time: 59% better Predictability*: 89% better *Standard deviation
  18. 18. Why something that intuitiveseems so counterintuitivewhen we talk aboutmanagement?
  19. 19. …and they livedhappily everafter
  20. 20. WIP limits! 5O
  21. 21. Average cycle time: 50% betterPessimistic scenario: 53% better Predictability*: 65% better *80th percentile
  22. 22. Why?
  23. 23. Slack time
  24. 24. Automation
  25. 25. Code quality
  26. 26. Simpleconfiguration
  27. 27. Self-balancingteam
  28. 28. Slack time introduced byWIP limits drives continuous improvement
  29. 29. When introducing WIP limits start with 2x average WIP Don Reinertsen
  30. 30. Cost of blocked work: 1% worseCost of idle capacity: 1% worseAverage cycle time: 28% better Source: Don Reinertsen, #lkce12 keynote
  31. 31. Are aggressiveWIP limitsuseful? 2O
  32. 32. What’s the useof slack time?
  33. 33. Idletimeonly?
  34. 34. Helpothers
  35. 35. Learn
  36. 36. Systemimprovements!
  37. 37. COST OF DELAYVALUE
  38. 38. Project andCOST OF DELAY product work VALUE
  39. 39. Project andCOST OF DELAY product work System improvements VALUE
  40. 40. Cost of blocked work: 1% worse
  41. 41. Cost of blocked work: 1% worse What’s the value of blocked or rejected work?
  42. 42. Cost of idle capacity: 1% worse
  43. 43. Cost of idle capacity: 1% worseIs capacity wasted or used to do something else?
  44. 44. Average cycle time: 28% better
  45. 45. Average cycle time: 28% better What happens to cycle time thanks to improvements?
  46. 46. Project andCOST OF DELAY product work System improvements VALUE
  47. 47. Takeouts
  48. 48. 100% utilization is a myth 1OO%
  49. 49. Introducing WIP limits results in improved efficiency
  50. 50. Slack time sets us on path of continuous improvement
  51. 51. Thank youSpecial thanks to Don Reinertsen Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski

×