Dont limit yorself beyond kanban - presentation - paulo caroli

1,765
-1

Published on

Paulo Caroli presentation on the target-variance model. Beyond Kanban.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,765
On Slideshare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Dont limit yorself beyond kanban - presentation - paulo caroli

  1. 1. Don’t limit yourself!Kanban and beyond Paulo Caroli Agile Coach pcaroli@thoughtworks.com Twitter: @paulocaroli
  2. 2. Agenda• Workflow• Card Wall• Important parameters• Kanban mechanics• Replenishment• Going Beyond• Q&A
  3. 3. Workflow
  4. 4. A workflow is a sequence of steps and activities of workperformed by a person or a team to achieve a specific goal.
  5. 5. Final StageStage 1 Stage 2 Goal N (Done)
  6. 6. Workflow examples
  7. 7. Visible workflow
  8. 8. We have been usingCard Walls for a long time…
  9. 9. The workflow stages
  10. 10. The workflow stages the work
  11. 11. “these card walls are not inherently kanban systems. They are merely visual control systems. They allow teams to visually observe work-in- progress and to self-organize, assign their own tasks, and move work from a backlog to complete”
  12. 12. David has a point…
  13. 13. Parameters froma simple card wall
  14. 14. To Do Doing Done 1210 1 John 7 5 49 Suzy 21 18 31 Paul 17 5 Amy
  15. 15. To Do Doing Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  16. 16. To Do Doing Done Day 6 Day 1 12 1010 10 John 1 7 Lead Time 5 49 Suzy 21 18 31 Paul 17 5 Amy
  17. 17. To Do Doing Done Throughput 1210 1 John Day 1 7 Day 2 5 49 Suzy 21 Day 3 18 31 Paul 17 5 Amy
  18. 18. Kanban mechanics
  19. 19. DoingTo Do Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  20. 20. DoingTo Do (Limit) Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  21. 21. DoingTo Do (Limit) Done 1210 Demand Throughput 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  22. 22. DoingTo Do (Limit) Done 1210 Demand Throughput 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 AmyBalance demand against throughput
  23. 23. DoingTo Do (Limit) Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul Lead Time 17 5 Amy
  24. 24. DoingTo Do (Limit) Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul Lead Time 17 5 Amyincreased lead time => poorer quality
  25. 25. Doing To Do (Limit) Done 12 10 1 John 7 WIP 5 4 9 Suzy 21 18 31 Paul Lead Time 17 5 Amy# WIP is proportional to average lead time
  26. 26. Before and After example
  27. 27. In Dev In QC Ready forBacklog Q Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  28. 28. In Dev In QC Ready forBacklog Q Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  29. 29. In Dev In QC Ready forBacklog Q Sign off 10 12 John Suzy 5 1 7 Dan4 9 18 Paul Amy 31 21 5 17
  30. 30. In Dev In QC Ready forBacklog Q Sign off 10 12 John Suzy 5 1 7 Dan4 18 Paul Amy 31 21 5 9 17
  31. 31. In Dev In QC Ready forBacklog Q Sign off 10 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 3121 5 917
  32. 32. In Dev In QC Ready forBacklog Q Sign off 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 3121 5 917 10
  33. 33. In Dev In QC Ready forBacklog Q Sign off 21 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 31 5 917 10
  34. 34. Any problem?
  35. 35. In Dev In QC Ready forBacklog Q Sign off 21 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 31 5 917 10
  36. 36. Limit
  37. 37. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  38. 38. Pull System, Queue and Limits
  39. 39. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  40. 40. 80% done on Card #9
  41. 41. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  42. 42. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Amy Dan4 9 18 Paul Amy 31 21 5 17
  43. 43. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Amy Dan4 9 18 Paul 31 21 5 17
  44. 44. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Amy Dan 54 9 18 Paul 31 21 5 17
  45. 45. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 7 Amy Dan 54 9 18 Paul 31 21 5 17
  46. 46. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 7 Amy Dan 54 9 18 Paul 31 21 5 17
  47. 47. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 Amy Dan 54 9 18 Paul 31 21 5 17
  48. 48. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 Amy Dan 54 9 18 Paul Amy 31 21 5 17
  49. 49. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 Dan 54 9 18 Paul Amy 31 21 5 17
  50. 50. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 9 Dan 54 9 18 Paul Amy 31 21 5 17
  51. 51. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 9 Dan 54 18 Paul Amy 31 21 5 17
  52. 52. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 7 1 9 Dan 54 10 18 Paul Amy 31 21 5 17
  53. 53. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 John Suzy 7 1 9 Dan 54 10 18 Paul Amy 31 21 5 17
  54. 54. Don’t limit yourself
  55. 55. Replenishment
  56. 56. Replenishment is driven by actualconsumption, not sales forecasts
  57. 57. I have seen this before…
  58. 58. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  59. 59. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  60. 60. Eggplant at the wall
  61. 61. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  62. 62. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  63. 63. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  64. 64. Rethinking nomenclature…
  65. 65. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  66. 66. Target instead of Limit
  67. 67. “Yet another choice would be to… adopt a policy of exceedingthe WIP limit when a burst ofproduction text changes arrives...This was the choice made in thereal example ...”
  68. 68. Should we accept variance?
  69. 69. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  70. 70. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  71. 71. “For example, if we had tenpeople and anticipated twopeople per item, the WIP limitmight be five plus a few more tosmooth the impact of ablockage. Perhaps eight (five plusthree) would be the right limit insuch circumstances.”
  72. 72. … so we are already dealing with variance for upper limit…
  73. 73. … but, what about a variance for less?(to avoid starvation)
  74. 74. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  75. 75. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  76. 76. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 5 Dan4 9 18 Paul Amy 21 5 17
  77. 77. Backlog In Dev Q In QC Ready for (2) (2) (1) Sign off 12 10 John Suzy 1 Dan4 9 18 Paul Amy 21 5 5 17
  78. 78. Variance to cope with SWdevelopment empirical nature
  79. 79. “For example, if we had tenpeople and anticipated twopeople per item, the WIP limitmight be five plus a few more tosmooth the impact of ablockage. Perhaps eight (five plusthree) would be the right limit insuch circumstances.”
  80. 80. Make it visible!
  81. 81. [5,3] instead of (8)
  82. 82. Backlog In Dev Q In QC Ready for (4) (2) (2) Sign off 12 10 John Suzy 1 5 7 Dan4 9 Paul Amy 18 5 31 21 Tom 12 5 Rob Ben 17 12 Mar Sue y
  83. 83. Backlog In Dev Q In QC Ready for [4,2] [4,2] [2,1] [2,1] Sign off 12 10 John Suzy 1 5 7 Dan4 9 Paul Amy 18 5 31 21 Tom 12 5 Rob Ben 17 12 Mar Sue y
  84. 84. Thank you! Questions?Don’t limit yourself! Paulo Caroli Agile Coach pcaroli@thoughtworks.com Twitter: @paulocaroli
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×