Successfully reported this slideshow.
Upcoming SlideShare
×

of

Upcoming SlideShare
Kanban Avançado - Além de Visualizações e Limites
Next

13

Share

# 7 Ways To Track Lead-Time

Measuring lead time is important and is a key performance indicator (KPI) that every Agile team should track. Poor lead time causes bottlenecks in the team production flow, inefficiencies, delay costs, not to mention unhappy customers. Come to this session to discuss with others how to track and monitor improvement on lead time.

See all

See all

### 7 Ways To Track Lead-Time

2. 2. Agenda• Flow numbers at my bar• 7 Ways to track lead time• Q&A
3. 3. Flow numbers at my bar
4. 4. WIP• The number of bottles in the bar. Bottlesthat have been opened, but are not yetempty.
5. 5. Lead time• The time between the bottle is added tothe bar and the bottle comes out of thebar (empty).
6. 6. Cycle time• The time between two successive emptybottles leaving the bar
7. 7. Throughput• The rate at which bottles are passing throughthe bar.
8. 8. Batch size• The size of the bottles.
9. 9. My bar…
10. 10. I was really interested inmeasuring a whiskey bottleaverage lead time in my bar...
11. 11. “The average number of workitems in a stable system is equalto their average completion rate,multiplied by their average timein the system.”John Little, 1961
12. 12. WIP = Throughput x Lead time
15. 15. 12 bottles...
16. 16. an average of 6 bottles peryear…
17. 17. ?
18. 18. What is the average lead timefor a bottle of whiskey?
19. 19. (a) 2 months(b) 3 months(c) 6 months(d) 1 year(e) 2 yearsWhat is the average lead time fora bottle of whiskey?
20. 20. WIP = Throughput x Lead time
21. 21. WIP = Throughput x Lead time12 b= 6 b / year x Lead time
22. 22. WIP = Throughput x Lead time12 b= 6 b / year x Lead timeLead time = 2 years
23. 23. Little’s law math
24. 24. WIP = Throughput x Lead time12 b= 6 b / year x Lead timeLead time = 2 years
25. 25. WIP = Throughput x Lead time1
26. 26. Visual repesentation for SWDevelopmemnt work...
27. 27. Doing DoneTo Do105931181721475112JohnSuzyPaulAmy
28. 28. Doing DoneTo Do105931181721475112JohnSuzyPaulAmyLead Time10 10Day 1Day 6
29. 29. Write on card
30. 30. Banana peal
31. 31. Chickenpox
32. 32. Story tracking graph
33. 33. Little’s Law
34. 34. Story Tracking
35. 35. Little’s Law
36. 36. Control Chart
37. 37. Control Chart
38. 38. Control Chart
39. 39. Cummulative Flow Diagram
40. 40. Doing(Limit) DoneTo Do105931181721475112JohnSuzyPaulAmyWIPLead Time
42. 42. Lead TimeCumulative Flow Diagram
43. 43. Let’s build these graphs together!61
44. 44. Story #time
46. 46. Worktime
47. 47. 66Functionalitytime
48. 48. 67Functionalitytime
49. 49. Story #time
51. 51. Worktime
52. 52. Worktime
53. 53. 72Functionalitytime
54. 54. Story #time
56. 56. Worktime
57. 57. Worktime
58. 58. 77Functionalitytime4
59. 59. Story #time
61. 61. Worktime
62. 62. Worktime
63. 63. Agenda• Flow numbers at my bar• 7 Ways to track lead time• Q&A
64. 64. WIP = Throughput x Lead time1
65. 65. Little’s Law
66. 66. Control Chart
67. 67. Lead TimeCumulative Flow Diagram
70. 70. Question / ExamplePlanned and Planning:velocity versus lead time92
71. 71. 93Functionality42882484Total Scope: 40Total Scope: 40
72. 72. If all work could bestarted at the same time...94
73. 73. Product Backlog95Functionalitytime
74. 74. The team has 3 pairs of engineers,and dependent Stories(swim lanes)96
75. 75. 97time
76. 76. 98Functionalitytime
77. 77. Now looking at Sprints99
78. 78. 100Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3
79. 79. 101Functionalitytime42882484sp 1sp 1 sp 2sp 2 sp 3sp 3
80. 80. Let’s go back in timeand compare planned and actual102
81. 81. Planned103Functionality42882484Total Scope: 40 points1 Release of 3 sprintsExpected velocity:10 points for Sprint 115 points for Sprint 2 and 3Total Scope: 40 points1 Release of 3 sprintsExpected velocity:10 points for Sprint 115 points for Sprint 2 and 3
82. 82. 104Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3Velocity (planned)1015 15
83. 83. 105Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3Velocity (planned)1015 15
84. 84. 106Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3Burn Up (planned)102540
85. 85. Actual...107
86. 86. 108Functionalitytime42sp 1sp 1 sp 2sp 2 sp 3sp 3
87. 87. 109Functionalitytime42sp 1sp 1 sp 2sp 2 sp 3sp 3
88. 88. 110Functionalitytime42sp 1sp 1 sp 2sp 2 sp 3sp 3Planned: 1010
89. 89. 111Functionalitytime42sp 1sp 1 sp 2sp 2 sp 3sp 3Finished: 6106
90. 90. 112Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3Burn Up (planned)102540plannedactual6
91. 91. That Sprint review meeting...113
92. 92. 114Functionalitytime42sp 1sp 1 sp 2sp 2 sp 3sp 382
93. 93. 115Functionalitytime42882484sp 1sp 1 sp 2sp 2 sp 3sp 31015 15618 16
94. 94. 116Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3Burn Up102540624plannedactual
96. 96. Story #time
98. 98. 120Functionalitytime42882484sp 1sp 1 sp 2sp 2 sp 3sp 3
99. 99. 121Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3
100. 100. Story #time
102. 102. 124Functionalitytimesp 1sp 1 sp 2sp 2 sp 3sp 3
103. 103. Story #time
105. 105. 127Functionalitytime4sp 1sp 1 sp 2sp 2 sp 3sp 3
106. 106. Story #time
109. 109. Planning131Functionality42882484Total Scope: 8 StoriesOn day 6 out of 15:3 Stories are done, 2 are inprogress; 3 to goAvg lead time = 5 days andthe team work on 3 stories inparallelTotal Scope: 8 StoriesOn day 6 out of 15:3 Stories are done, 2 are inprogress; 3 to goAvg lead time = 5 days andthe team work on 3 stories inparalleldoneInprogressnext
110. 110. Will we make it?Answer based on lead time: yes, weshould finish all stories by day 15132Answer based on velocity: we need to increate theteam velocity, otherwise we will not finish all 40story points by day 15vs.
112. 112. You can get average per story size134
115. 115. Or average for lead time (if you arealready over extimates)137
116. 116. Control Chart
117. 117. QuestionHow do i visualize cycle time?139
118. 118. SMLSLMLMCycle timeCycle timetimeLead time
• #### syerram

Oct. 27, 2019

Aug. 1, 2019
• #### JohnnyDark

Dec. 19, 2014
• #### robertatc

Jul. 26, 2013

Jul. 7, 2013

Jul. 6, 2013

Jul. 3, 2013

Jul. 2, 2013

Jul. 1, 2013

Jul. 1, 2013

Jul. 1, 2013
• #### megatroom

Jun. 29, 2013
• #### rerebelo

Jun. 27, 2013

Measuring lead time is important and is a key performance indicator (KPI) that every Agile team should track. Poor lead time causes bottlenecks in the team production flow, inefficiencies, delay costs, not to mention unhappy customers. Come to this session to discuss with others how to track and monitor improvement on lead time.

Total views

6,514

On Slideshare

0

From embeds

0

Number of embeds

4,044

0

Shares

0