Scrum with Kanban; small adjustments, big improvements (Paulo Caroli and Johann Arispe) 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. Johann Arispe Business Analyst
jarispe@thoughtworks.com
Scrum with Kanban;
Small adjustments,
big improvements
Paulo Caroli Agile Coach
pcaroli@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. Stage 1 Stage 2
Stage
N
Final
Goal
(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. 10
5
9
31
17
21
4
12
John
Suzy
Paul
Amy
Dan
Sprint Backlog Engineers

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

41. Pulling the work

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

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

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

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

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. In Dev In QC Signed
Off
Backlog
2
4
5
3
1
M Tu W Th FToday is:

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

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

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

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

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

54. Another team…

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

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

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

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

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

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

61. What about that Sprint review
meeting on Monday?

62. Common Kanban terms…

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

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

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

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

67. Kanban mechanics

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

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

70. Doing
(Limit) DoneTo Do
10
5
9
31
18
17
21
4
7
5
1
12
John
Suzy
Paul
Amy
WIP
ThroughputDemand

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

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

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

74. Doing
(Limit) DoneTo Do
10
5
9
31
18
17
21
4
7
5
1
12
John
Suzy
Paul
Amy
WIP
Lead Time
# WIP is proportional to average lead time

75. Before and After
example

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

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

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

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

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

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

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

83. Any problem?

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

86. Stop starting
and start finishing!

87. WIP Limit

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

89. Visible Workflow,
Pull System and WIP Limit

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

91. Dev Complete for Card #9

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

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

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

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

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

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

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

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

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

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

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

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

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

105. Back to the Sprint example…

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

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

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

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

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

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

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

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
115
Stories for Feature A
Stories for Feature B
Stories for Feature C

116. The Product Backlog
116

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

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

119. Product Backlog
119
Functionality
time

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

121. 121
time

122. 122
Functionality
time

123. Now looking at Sprints
123

124. 124
Functionality
time
sp 1 sp 2 sp 3

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

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

127. Planned
127
Functionality
4
2
8
8
2
4
8
4 Total Scope: 40`points
1 Release of 3 sprints
Expected velocity:
10 points for Sprint 1
15 points for Sprint 2 and 3

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

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

130. Actual...
130

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

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

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

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

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

136. That Sprint review meeting...
136

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

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

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

140. Tracking lead time and cycle time
140

141. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
Story #
time

142. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle TimeLead time
time

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

144. 144
Functionality
time
sp 1 sp 2 sp 3

145. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
Story #
time

146. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
time
Lead time

147. 147
Functionality
time
sp 1 sp 2 sp 3

148. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
Story #
time

149. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
S
time
Lead time

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

151. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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
Story Tracking
Story #
time

152. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
S
M
L
time
Lead time

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

154. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
S
M
L
S
L
M
L
M
time
Lead time

155. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
S
M
L
S
L
M
L
M
time
Lead time

156. 0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
LeadTime and Cycle Time
S
M
L
S
L
M
L
M
Cycle time
time
Lead 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
Johann Arispe Business Analyst
jarispe@thoughtworks.com
Paulo Caroli Agile Coach
pcaroli@thoughtworks.com
Twitter: @paulocaroli

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