This was a rather short, yet very dense experience report that accompanies a paper, to tell the story of a team that evolved from textbook Scrum to something much alike Lean Software Development and then decided they needed iterations back.

1. Nowadays, we're
not doing Scrum

2. Neither XP

3. Neither XP
Or FDD

4. Neither XP
Or FDD
Or Kanban

5. Or Lean Software Development
Neither XP
Or FDD
Or Kanban

6. Or Lean Software Development
Neither XP
Or FDD
Or Kanban
Or Crystal

7. So...
you're not agile?

8. Of course we are!

9. Of course we are!
In our own way!

10. “Not all those who
wander are lost.”

11. There and back again
Cecilia Fernandes
@cecifernandes

12. What is Caelum?

13. What is Caelum?

14. What is Caelum?

15. What is Caelum?
teaching

16. What is Caelum?
innovation
teaching

17. What is Caelum?
collaboration
innovation
teaching

18. improvement
What is Caelum?
collaboration
innovation
teaching

19. improvement
What is Caelum?
collaboration
fun!
innovation
teaching

20. Caelum FAQ
Is agile a company policy?

21. Caelum FAQ
How many project teams are there?
Is agile a company policy?

22. Caelum FAQ
How many project teams are there?
Is agile a company policy?
Are there non-senior
team members?

23. Caelum FAQ
How many project teams are there?
Is agile a company policy?
What do you love the most
about Caelum?
Are there non-senior
team members?

24. Caelumweb2

25. 2008~2010

26. But...
Deploy => ...

27. But...
Deploy =>

28. Hmm... what if...

29. Hmm... what if...
One-click deploy

30. Hmm... what if...
One-click deploy

31. Less fear
Less rollbacks
One-click deploy
Shorter offline time
Less errors

32. Most importantly...
One-click deploy
=>

33. Most importantly...
One-click deploy
=>

34. Release planning

35. Release planning

36. But...
Sprint #n failed
Sprint #m failed
...

37. But... what about the
Sprint Burndown?

38. But... what about the
Sprint Burndown?
Story partials burn down
points
days
expected real

39. But... what about the
Sprint Burndown?
Story partials burn down
Lie r!
points
days
expected real

40. But... what about the
Sprint Burndown?
Story partials burn down
Lie r!
points
Everything was
“almost” done
days
expected real

41. Hmm...
task points Sprint Burndown
vs.
story points Sprint Burndown

42. Hmm...
Lier!
task points Sprint Burndown
vs.
story points Sprint Burndown

43. Hmm...
Lier!
task points Sprint Burndown
vs.
story points Sprint Burndown
Better...

44. But...
story points Sprint Burndown

45. But...
We already
have this
Information!
story points Sprint Burndown

46. White board
To do Doing Done

47. White board
To do Doing Done

48. White board
To do Doing Done

49. Burn down

50. Burn down

51. Scrum Master

52. Scrum Master
I never
have
anything
to do!

53. Scrum Master
How about
managing
the process?

54. Scrum Master
How about
managing
the process?
The team
does that!

55. Scrum Master
And who
solves
impediments?

56. Scrum Master
And who
solves
impediments?
There are
none!

57. Scrum Master
Education
Impediments

58. Scrum Master
Education
Everyone has to know
the reasons
Impediments

59. Scrum Master
Education
Everyone has to know
the reasons
Impediments
Autonomy to solve...
anything!

60. Scrum Master
Education
Everyone has to know
the reasons
I quit!
Impediments
Autonomy to solve...
(being a Scrum
anything!
Master, I mean)

61. Scrum Master

62. Scrum Master

63. Team size over time
2008 2009 2010 2011 2012
3 7 11 4 ...

64. Team size over time
2008 2009 2010 2011 2012
3 7 11 4 ...
New project starting!
Less new features
More maintenance

65. 4 people
on the team
Pairing
(most of the time)

66. Daily?
4 people
on the team
Pairing
(most of the time)

67. Daily?
4 people
on the team
Pairing
(most of the time)

68. Daily?
Everyone
knows what
the others
are doing

69. Daily?
Everyone
knows what
the others
are doing
Everyone has to ask!

70. Daily
Discipline!

71. Daily Scrum

72. Daily Scrum

74. Clients next
door
Continuous delivery

75. Review meeting
Do I really have to
be at the review?

76. Review meeting
Do I really have to
be at the review?
I know what you
did! I've been using
it for a week!

77. Review meeting
Do I really have to
be at the review?
I know what you
did! I've been using
it for a week!
And I talk
to you
everyday!

78. Review meeting

79. Review meeting

80. Can't wait!
I don't
get it...

81. Can't wait!
I don't You deliver new
get it... software all the
time...

82. Can't wait!
I don't You deliver new
get it... software all the
time...
Why can't you get
new requests as
frequently?

83. Can't wait!
I don't You deliver new
get it... software all the
time...
Why can't you get
new requests as
frequently?
These are small
and important

84. Can't wait!

85. Sprints aren't
working for us
anymore...

86. Yeah... it's getting
Sprints aren't On our way too.
working for us
anymore...

87. Yeah... it's getting
Sprints aren't On our way too.
working for us We'll be glad
to switch to a
anymore... flowish method

88. Flow

89. Flow

90. It worked!

91. Scrum but...

92. Not Scrum at all!

93. Not Scrum at all!
and...

94. It worked!
Changes
made sense

95. It worked!
Changes
made sense
were well
thought

96. It worked!
Changes
came from
retrospectives

99. 1 week

100. 2 weeks

101. 3 weeks

102. 4 weeks

103. Missing something...

104. Chronic problems?

105. Never happen!

106. Hmm! So we can...

107. Drop retrospectives!

108. It got bad...

109. And worse...

110. Terrible, really!

111. Nothing happening

112. Less pressure

113. Except for bugs

114. Metrics?

115. Velocity!

116. Flow without metrics
-

117. What happened?

118. What happened?
(we figured out later...)

119. No iterations

120. No iterations
=>
no goal

121. No iterations
=>
no goal
=>
less motivation

122. Less motivation
=>
upset team

123. Less motivation
=>
upset team
...
how to fix it?

124. Look for other
motivation!

125. Let's go faster!

126. and faster

127. and faster!

128. Agile processes
promote
sustainable
development.

129. Agile processes
promote
sustainable
development.
This team, though...

130. More points
=>

131. Less points
=>

132. Stress++

133. It got bad

134. Seriously
bad

135. Did they notice?

136. Did I say...

137. “I can see a
problem...

138. …it must be
just me, tho...”

139. Was it the only
problem?

140. challenges--

141. challenges--
isolation++

142. challenges--
communication--
isolation++

143. challenges--
technical debt++
communication--
isolation++

144. challenges--
technical debt++
communication--
bugs++
isolation++

145. “but the PO wants us
to deliver points!”
My
precioussss
points

146. Did they ever ask?

147. No!

148. That brought serious
consequences

149. That brought serious
consequences
challenges--
technical debt++
communication--
bugs++
isolation++

150. How do we change it?

151. How do we change it?
We need goals and
we need to retake
retrospectives!

152. How do we change it?
We need goals and
we need to retake We can make a calendar
retrospectives! and demand that the client
group similar stories for us

153. How do we change it?
We need goals and
we need to retake We can make a calendar
retrospectives! and demand that the client
group similar stories for us
Or... we can
have iterations
back!

154. Unfortunately,
the timebox here
also got in our way
More about
it on the
paper!

155. Unfortunately,
the timebox here
also got in our way
More about
mo re
it on the A lot
paper!

156. The message I wish
you got from this
talk is...
More about
mo re
it on the A lot
paper!

157. Good solutions...
emerge!

158. It doesn't matter the

159. Does it work
for your team?

160. Is it an
improvement?

161. That's what
matters!

162. Improving has to be
a neverending story

163. Just...

164. Just...
Cecilia Fernandes
@cecifernandes