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.

1. Scrum with Kanban;
Small adjustments,
big improvements
Paulo Caroli Agile Coach Johann Arispe Business Analyst
pcaroli@thoughtworks.com jarispe@thoughtworks.com
Twitter: @paulocaroli

2. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

3. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

4. Image available at www.mountaingoatsoftware.com/scrum

5. Image available at www.mountaingoatsoftware.com/scrum

6. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

8. Workflow

9. A workflow is a sequence of steps
and activities of work performed by
a person or a team to achieve a
specific goal.

10. Final
Stage
Stage 1 Stage 2 Goal
N
(Done)

11. Workflow examples

16. On Agile projects,
we typically work with
User Stories…

17. Overall project
requirement

23. For each User Story…

25. The SW development workflow…

26. Analysis Design Code Test Deploy

27. Visible Workflow

29. The workflow stages

30. The workflow stages
the work

37. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

38. Pushing the work

39. Sprint Backlog Engineers
4 9
John
Suzy
Dan
12
Amy
21
10 Paul
5
31
17

40. Sprint Backlog Engineers
12 10 John
4 9 Suzy
21 31 Paul
5 Amy
17
Dan

41. Pulling the work

42. Sprint Backlog Engineers
4 9
John
Suzy
Dan
12
Amy
21
10 Paul
5
31
17

43. In Dev In QC Ready for
Backlog
Sign off
12
10 John Suzy 1
5
7 Dan
4
9 31
18
Paul Amy
21
5
17

44. In Dev In QC Ready for
Backlog
Sign off
12
10 John Suzy 1
5
7 Dan
4
9 31
18
Paul Amy 31
21
5
17

45. In Dev In QC Ready for
Backlog
Sign off
12
10 John Suzy 1
5
7 Dan
4
9 9
18
Paul Amy 31
21
5
17

46. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

47. A Sprint example…

48. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

49. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

50. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

51. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

52. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

53. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

54. Another team…

55. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

56. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

57. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

58. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

59. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

60. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

61. What about that Sprint review
meeting on Monday?

62. Common Kanban terms…

63. To Do Doing Done
12
10 1
John
7
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

64. To Do Doing Done
12
10 1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

65. To Do Doing Done
Day 6
Day 1 12 10
10 10
John 1
7 Lead Time
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

66. To Do Doing Done
Cycle time
12
10 1
John Day 1
7
Day 2 5
4
9 Suzy
21 Day 3 18
31
Paul
17
5 Amy

67. Kanban mechanics

68. Doing
To Do Done
12
10 1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

69. Doing
To Do (Limit) Done
12
10 1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

70. Doing
To Do (Limit) Done
12
10 Demand Throughput
1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul
17
5 Amy

71. Doing
To Do (Limit) Done
12
10 Demand Throughput
1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul
17
5 Amy
Balance demand against throughput

72. Doing
To Do (Limit) Done
12
10 1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul Lead Time
17
5 Amy

73. Doing
To Do (Limit) Done
12
10 1
John
7 WIP
5
4
9 Suzy
21 18
31
Paul Lead Time
17
5 Amy
increased lead time => poorer quality

74. 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

75. Before and After
example

76. In Dev In QC Ready for
Backlog
Sign off
12
10 John Suzy 1
5
7 Dan
4
9
18
Paul Amy 31
21
5
17

77. In Dev In QC Ready for
Backlog
Sign off
12
10 John Suzy 1
5
7 Dan
4
9
18
Paul Amy 31
21
5
17

78. In Dev In QC Ready for
Backlog
Sign off
10 12
John Suzy 5 1
7 Dan
4
9
18
Paul Amy 31
21
5
17

79. In Dev In QC Ready for
Backlog
Sign off
10 12
John Suzy 5 1
7 Dan
4
18
Paul Amy 31
21
5
9
17

80. In Dev In QC Ready for
Backlog
Sign off
10 12
John Suzy 5 1
7 Dan
4
18
Paul Amy 31
21
5
9
17

81. In Dev In QC Ready for
Backlog
Sign off
12
John Suzy 5 1
7 Dan
4
18
Paul Amy 31
21
5
9
17
10

82. In Dev In QC Ready for
Backlog
Sign off
21 12
John Suzy 5 1
7 Dan
4
18
Paul Amy 31
5
9
17
10

83. Any problem?

84. In Dev In QC Ready for
Backlog
Sign off
21 12
John Suzy 5 1
7 Dan
4
18
Paul Amy 31
5
9
17
10

86. Stop starting
and start finishing!

87. WIP Limit

88. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Dan
4
9
18
Paul Amy 31
21
5
17

89. Visible Workflow,
Pull System and WIP Limit

90. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Dan
4
9
18
Paul Amy 31
21
5
17

91. Dev Complete for Card #9

92. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Dan
4
9
18
Paul Amy 31
21
5
17

93. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Amy Dan
4
9
18
Paul Amy 31
21
5
17

94. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Amy Dan
4
9
18
Paul 31
21
5
17

95. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
5
7 Amy Dan
5
4
9
18
Paul 31
21
5
17

96. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 1
7 Amy Dan
5
4
9
18
Paul 31
21
5
17

97. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
7 Amy Dan
5
4
9
18
Paul 31
21
5
17

98. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
Amy Dan
5
4
9
18
Paul 31
21
5
17

99. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
Amy Dan
5
4
9
18
Paul Amy 31
21
5
17

100. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
Dan
5
4
9
18
Paul Amy 31
21
5
17

101. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
9 Dan
5
4
9
18
Paul Amy 31
21
5
17

102. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
9 Dan
5
4
18
Paul Amy 31
21
5
17

103. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
10 John Suzy 7 1
9 Dan
5
4
10
18
Paul Amy 31
21
5
17

104. Backlog In Dev In QC Ready for
(2) (3) Sign off
12
John Suzy 7 1
9 Dan
5
4
10
18
Paul Amy 31
21
5
17

105. Back to the Sprint example…

106. Backlog In Dev In QC Signed
Off
1
2
3
4
5
Today is: M Tu W Th F

107. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

108. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

109. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

110. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

111. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

112. Backlog In Dev In QC Signed
(2) (1) Off
1
2
3
4
5
Today is: M Tu W Th F

113. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

114. A release example…

115. Features on the product backlog
Stories for Feature A
Stories for Feature B
Stories for Feature C
115

116. The Product Backlog
116

117. Functionality
4
8
4
2 Total Scope: 40
8
8
2
4
117

118. If all work could be
started at the same time...
118

119. Functionality Product Backlog
time
119

120. The team has 3 pairs of engineers,
and dependent Stories
(swim lanes)
120

121. time
121

122. Functionality
time
122

123. Now looking at Sprints
123

124. sp 1 sp 2 sp 3
Functionality
time
124

125. sp 1 sp 2 sp 3
Functionality
4
8
4
2
8
8
2
4
time
125

126. Let’s go back in time
and compare planned and actuals
126

127. 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

128. Velocity (planned)
sp 1 sp 2 sp 3
Functionality
15 15
10
time
128

129. Burn Up (planned)
sp 1 sp 2 sp 3
Functionality
40
25
10
time
129

130. Actual...
130

131. sp 1 sp 2 sp 3
Functionality
2
4
time
131

132. sp 1 sp 2 sp 3
Functionality
2
4
time
132

133. Planned: 10
sp 1 sp 2 sp 3
Functionality
10 2
4
time
133

134. Finished: 6
sp 1 sp 2 sp 3
Functionality
10 2
6
4
time
134

135. Burn Up (planned)
sp 1 sp 2 sp 3
Functionality
40
25
10
planned
actual
6
time
135

136. That Sprint review meeting...
136

137. sp 1 sp 2 sp 3
Functionality
2
8
2
4
time
137

138. sp 1 sp 2 sp 3
Functionality
4
8
4
2
18 16
8
15 15
8
10 2
6 4
time
138

139. Burn Up
sp 1 sp 2 sp 3
Functionality
40
25
24
planned 10
actual
6
time
139

140. Tracking lead time and cycle time
140

141. Story Tracking
Story #
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

142. 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

143. sp 1 sp 2 sp 3
Functionality
4
8
4
2
8
8
2
4
time
143

144. sp 1 sp 2 sp 3
Functionality
time
144

145. Story Tracking
Story #
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

146. 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

147. sp 1 sp 2 sp 3
Functionality
time
147

148. Story Tracking
Story #
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

149. 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

150. sp 1 sp 2 sp 3
Functionality
4
time
150

151. Story Tracking
Story #
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

152. 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

153. sp 1 sp 2 sp 3
Functionality
4
8
4
2
8
8
2
4
time
153

154. 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

155. Lead Time and Cycle Time
Lead 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

156. 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

157. Agenda
• The Scrum flow of work
• Visible workflow
• Pull don’t push
• Limit WIP
• Tracking lead time and cycle time
• Q&A

158. Scrum with Kanban;
Small adjustments,
big improvements
Paulo Caroli Agile Coach Johann Arispe Business Analyst
pcaroli@thoughtworks.com jarispe@thoughtworks.com
Twitter: @paulocaroli

159. Thank you!
Questions?
feedback please: @paulocaroli
Paulo Caroli Agile Coach Johann Arispe Business Analyst
pcaroli@thoughtworks.com jarispe@thoughtworks.com
Twitter: @paulocaroli