Scrum with Kanban; small adjustments, big improvements

1,274 views

Published on

Scrum with Kanban; small adjustments, big improvements.
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.

Published in: Technology

Scrum with Kanban; small adjustments, big improvements

  1. 1. Scrum with Kanban; Small adjustments, big improvementsPaulo Caroli Agile Coach Johann Arispe Business Analystpcaroli@thoughtworks.com jarispe@thoughtworks.comTwitter: @paulocaroli
  2. 2. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  3. 3. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  4. 4. Image available at www.mountaingoatsoftware.com/scrum
  5. 5. Image available at www.mountaingoatsoftware.com/scrum
  6. 6. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  7. 7. Workflow
  8. 8. A workflow is a sequence of stepsand activities of work performed by a person or a team to achieve a specific goal.
  9. 9. Final StageStage 1 Stage 2 Goal N (Done)
  10. 10. Workflow examples
  11. 11. On Agile projects,we typically work with User Stories…
  12. 12. Overall project requirement
  13. 13. For each User Story…
  14. 14. The SW development workflow…
  15. 15. Analysis Design Code Test Deploy
  16. 16. Visible Workflow
  17. 17. The workflow stages
  18. 18. The workflow stages the work
  19. 19. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  20. 20. Pushing the work
  21. 21. Sprint Backlog Engineers 4 9 John Suzy Dan 12 Amy 2110 Paul 5 31 17
  22. 22. Sprint Backlog Engineers12 10 John 4 9 Suzy21 31 Paul 5 Amy 17 Dan
  23. 23. Pulling the work
  24. 24. Sprint Backlog Engineers 4 9 John Suzy Dan 12 Amy 2110 Paul 5 31 17
  25. 25. In Dev In QC Ready forBacklog Sign off 12 10 John Suzy 1 5 7 Dan4 9 31 18 Paul Amy 21 5 17
  26. 26. In Dev In QC Ready forBacklog Sign off 12 10 John Suzy 1 5 7 Dan4 9 31 18 Paul Amy 31 21 5 17
  27. 27. In Dev In QC Ready forBacklog Sign off 12 10 John Suzy 1 5 7 Dan4 9 9 18 Paul Amy 31 21 5 17
  28. 28. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  29. 29. A Sprint example…
  30. 30. Backlog In Dev In QC Signed Off1 2 3 4 5 Today is: M Tu W Th F
  31. 31. Backlog In Dev In QC Signed Off 1 23 4 5 Today is: M Tu W Th F
  32. 32. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  33. 33. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  34. 34. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  35. 35. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  36. 36. Another team…
  37. 37. Backlog In Dev In QC Signed Off1 2 3 4 5 Today is: M Tu W Th F
  38. 38. Backlog In Dev In QC Signed Off 1 23 4 5 Today is: M Tu W Th F
  39. 39. Backlog In Dev In QC Signed Off 1 23 4 5 Today is: M Tu W Th F
  40. 40. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  41. 41. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  42. 42. Backlog In Dev In QC Signed Off 1 2 3 4 5 Today is: M Tu W Th F
  43. 43. What about that Sprint review meeting on Monday?
  44. 44. Common Kanban terms…
  45. 45. To Do Doing Done 1210 1 John 7 5 49 Suzy 21 18 31 Paul 17 5 Amy
  46. 46. To Do Doing Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  47. 47. 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
  48. 48. To Do Doing Done Cycle time 1210 1 John Day 1 7 Day 2 5 49 Suzy 21 Day 3 18 31 Paul 17 5 Amy
  49. 49. Kanban mechanics
  50. 50. DoingTo Do Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  51. 51. DoingTo Do (Limit) Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  52. 52. DoingTo Do (Limit) Done 1210 Demand Throughput 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 Amy
  53. 53. DoingTo Do (Limit) Done 1210 Demand Throughput 1 John 7 WIP 5 49 Suzy 21 18 31 Paul 17 5 AmyBalance demand against throughput
  54. 54. DoingTo Do (Limit) Done 1210 1 John 7 WIP 5 49 Suzy 21 18 31 Paul Lead Time 17 5 Amy
  55. 55. 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
  56. 56. 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
  57. 57. Before and After example
  58. 58. In Dev In QC Ready forBacklog Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  59. 59. In Dev In QC Ready forBacklog Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  60. 60. In Dev In QC Ready forBacklog Sign off 10 12 John Suzy 5 1 7 Dan4 9 18 Paul Amy 31 21 5 17
  61. 61. In Dev In QC Ready forBacklog Sign off 10 12 John Suzy 5 1 7 Dan4 18 Paul Amy 31 21 5 9 17
  62. 62. In Dev In QC Ready forBacklog Sign off 10 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 3121 5 917
  63. 63. In Dev In QC Ready forBacklog Sign off 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 3121 5 917 10
  64. 64. In Dev In QC Ready forBacklog Sign off 21 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 31 5 917 10
  65. 65. Any problem?
  66. 66. In Dev In QC Ready forBacklog Sign off 21 12 John Suzy 5 1 7 Dan 4 18 Paul Amy 31 5 917 10
  67. 67. Stop startingand start finishing!
  68. 68. WIP Limit
  69. 69. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  70. 70. Visible Workflow,Pull System and WIP Limit
  71. 71. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  72. 72. Dev Complete for Card #9
  73. 73. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Dan4 9 18 Paul Amy 31 21 5 17
  74. 74. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Amy Dan4 9 18 Paul Amy 31 21 5 17
  75. 75. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Amy Dan4 9 18 Paul 31 21 5 17
  76. 76. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 5 7 Amy Dan 54 9 18 Paul 31 21 5 17
  77. 77. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 1 7 Amy Dan 54 9 18 Paul 31 21 5 17
  78. 78. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 7 Amy Dan 54 9 18 Paul 31 21 5 17
  79. 79. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 Amy Dan 54 9 18 Paul 31 21 5 17
  80. 80. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 Amy Dan 54 9 18 Paul Amy 31 21 5 17
  81. 81. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 Dan 54 9 18 Paul Amy 31 21 5 17
  82. 82. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 9 Dan 54 9 18 Paul Amy 31 21 5 17
  83. 83. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 9 Dan 54 18 Paul Amy 31 21 5 17
  84. 84. Backlog In Dev In QC Ready for (2) (3) Sign off 12 10 John Suzy 7 1 9 Dan 54 10 18 Paul Amy 31 21 5 17
  85. 85. Backlog In Dev In QC Ready for (2) (3) Sign off 12 John Suzy 7 1 9 Dan 54 10 18 Paul Amy 31 21 5 17
  86. 86. Back to the Sprint example…
  87. 87. Backlog In Dev In QC Signed Off1 2 3 4 5 Today is: M Tu W Th F
  88. 88. Backlog In Dev In QC Signed (2) (1) Off1 2 3 4 5 Today is: M Tu W Th F
  89. 89. Backlog In Dev In QC Signed (2) (1) Off 1 23 4 5 Today is: M Tu W Th F
  90. 90. Backlog In Dev In QC Signed (2) (1) Off 1 23 4 5 Today is: M Tu W Th F
  91. 91. Backlog In Dev In QC Signed (2) (1) Off 1 2 3 4 5 Today is: M Tu W Th F
  92. 92. Backlog In Dev In QC Signed (2) (1) Off 1 2 3 4 5 Today is: M Tu W Th F
  93. 93. Backlog In Dev In QC Signed (2) (1) Off 1 2 3 4 5 Today is: M Tu W Th F
  94. 94. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  95. 95. A release example…
  96. 96. Features on the product backlog Stories for Feature A Stories for Feature B Stories for Feature C 115
  97. 97. The Product Backlog 116
  98. 98. Functionality 4 8 4 2 Total Scope: 40 8 8 2 4 117
  99. 99. If all work could bestarted at the same time... 118
  100. 100. Functionality Product Backlog time 119
  101. 101. The team has 3 pairs of engineers, and dependent Stories (swim lanes) 120
  102. 102. time 121
  103. 103. Functionality time122
  104. 104. Now looking at Sprints 123
  105. 105. sp 1 sp 2 sp 3Functionality time 124
  106. 106. sp 1 sp 2 sp 3Functionality 4 8 4 2 8 8 2 4 time 125
  107. 107. Let’s go back in timeand compare planned and actuals 126
  108. 108. Functionality Planned 4 Total Scope: 40`points 8 4 1 Release of 3 sprints 2 8 Expected velocity: 8 10 points for Sprint 1 15 points for Sprint 2 and 3 2 4 127
  109. 109. Velocity (planned) sp 1 sp 2 sp 3Functionality 15 15 10 time 128
  110. 110. Burn Up (planned) sp 1 sp 2 sp 3Functionality 40 25 10 time 129
  111. 111. Actual... 130
  112. 112. sp 1 sp 2 sp 3Functionality 2 4 time 131
  113. 113. sp 1 sp 2 sp 3Functionality 2 4 time 132
  114. 114. Planned: 10 sp 1 sp 2 sp 3Functionality 10 2 4 time 133
  115. 115. Finished: 6 sp 1 sp 2 sp 3Functionality 10 2 6 4 time 134
  116. 116. Burn Up (planned) sp 1 sp 2 sp 3Functionality 40 25 10 planned actual 6 time 135
  117. 117. That Sprint review meeting... 136
  118. 118. sp 1 sp 2 sp 3Functionality 2 8 2 4 time 137
  119. 119. sp 1 sp 2 sp 3Functionality 4 8 4 2 18 16 8 15 15 8 10 2 6 4 time 138
  120. 120. Burn Up sp 1 sp 2 sp 3Functionality 40 25 24 planned 10 actual 6 time 139
  121. 121. Tracking lead time and cycle time 140
  122. 122. Story TrackingStory # 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  123. 123. Lead time Lead Time and Cycle Time 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  124. 124. sp 1 sp 2 sp 3Functionality 4 8 4 2 8 8 2 4 time 143
  125. 125. sp 1 sp 2 sp 3Functionality time 144
  126. 126. Story TrackingStory # 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  127. 127. Lead time Lead Time and Cycle Time 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  128. 128. sp 1 sp 2 sp 3Functionality time 147
  129. 129. Story TrackingStory # 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  130. 130. Lead time Lead Time and Cycle Time 15 14 13 12 11 10 9 8 7 6 5 4 3 S 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  131. 131. sp 1 sp 2 sp 3Functionality 4 time 150
  132. 132. Story TrackingStory # 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  133. 133. Lead time Lead Time and Cycle Time 15 14 13 12 11 10 9 8 7 L 6 5 M 4 3 S 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  134. 134. sp 1 sp 2 sp 3Functionality 4 8 4 2 8 8 2 4 time 153
  135. 135. Lead time Lead Time and Cycle Time 15 14 13 12 11 10 9 L L 8 7 L 6 5 M M 4 M 3 S S 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  136. 136. Lead Time and Cycle TimeLead time 15 14 13 12 11 10 9 L L 8 7 L 6 5 M M 4 M 3 S S 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  137. 137. Lead time Lead Time and Cycle Time 15 14 Cycle time 13 12 11 10 9 L L 8 7 L 6 5 M M 4 M 3 S S 2 1 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 time
  138. 138. Agenda• The Scrum flow of work• Visible workflow• Pull don’t push• Limit WIP• Tracking lead time and cycle time• Q&A
  139. 139. Scrum with Kanban; Small adjustments, big improvementsPaulo Caroli Agile Coach Johann Arispe Business Analystpcaroli@thoughtworks.com jarispe@thoughtworks.comTwitter: @paulocaroli
  140. 140. Thank you! Questions? feedback please: @paulocaroliPaulo Caroli Agile Coach Johann Arispe Business Analystpcaroli@thoughtworks.com jarispe@thoughtworks.comTwitter: @paulocaroli

×