There and back again (as presented at Agile 2012, Dallas, TX)

  • 244 views
Uploaded on

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 …

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.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
244
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Nowadays, werenot doing Scrum
  • 2. Neither XP
  • 3. Neither XPOr FDD
  • 4. Neither XPOr FDD Or Kanban
  • 5. Or Lean Software Development Neither XPOr FDD Or Kanban
  • 6. Or Lean Software Development Neither XPOr FDD Or Kanban Or Crystal
  • 7. So...youre not agile?
  • 8. Of course we are!
  • 9. Of course we are! In our own way!
  • 10. “Not all those whowander 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? innovationteaching
  • 17. What is Caelum?collaboration innovationteaching
  • 18. improvementWhat is Caelum?collaboration innovationteaching
  • 19. improvementWhat is Caelum?collaboration fun! innovationteaching
  • 20. Caelum FAQ Is agile a company policy?
  • 21. Caelum FAQHow many project teams are there? Is agile a company policy?
  • 22. Caelum FAQHow many project teams are there? Is agile a company policy?Are there non-senior team members?
  • 23. Caelum FAQHow 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 timeLess errors
  • 32. Most importantly... One-click deploy =>
  • 33. Most importantly... One-click deploy =>
  • 34. Release planning
  • 35. Release planning
  • 36. But...Sprint #n failedSprint #m failed...
  • 37. But... what about theSprint Burndown?
  • 38. But... what about theSprint Burndown? Story partials burn down points days expected real
  • 39. But... what about theSprint Burndown? Story partials burn down Lie r! points days expected real
  • 40. But... what about theSprint Burndown? Story partials burn down Lie r! pointsEverything 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 solvesimpediments?
  • 56. Scrum Master And who solvesimpediments? There are none!
  • 57. Scrum MasterEducationImpediments
  • 58. Scrum MasterEducation Everyone has to know the reasonsImpediments
  • 59. Scrum MasterEducation Everyone has to know the reasonsImpediments Autonomy to solve... anything!
  • 60. Scrum MasterEducation 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 time2008 2009 2010 2011 2012 3 7 11 4 ...
  • 64. Team size over time2008 2009 2010 2011 2012 3 7 11 4 ... New project starting! Less new features More maintenance
  • 65. 4 peopleon the teamPairing(most of the time)
  • 66. Daily?4 peopleon the teamPairing(most of the time)
  • 67. Daily?4 peopleon the teamPairing(most of the time)
  • 68. Daily?Everyoneknows whatthe othersare doing
  • 69. Daily?Everyoneknows whatthe othersare doingEveryone has to ask!
  • 70. DailyDiscipline!
  • 71. Daily Scrum
  • 72. Daily Scrum
  • 73. Clients nextdoorContinuous delivery
  • 74. Review meetingDo I really have to be at the review?
  • 75. Review meetingDo I really have to be at the review? I know what you did! Ive been using it for a week!
  • 76. Review meetingDo I really have to be at the review? I know what you did! Ive been using it for a week! And I talk to you everyday!
  • 77. Review meeting
  • 78. Review meeting
  • 79. Cant wait!I dontget it...
  • 80. Cant wait!I dont You deliver newget it... software all the time...
  • 81. Cant wait!I dont You deliver newget it... software all the time... Why cant you get new requests as frequently?
  • 82. Cant wait!I dont You deliver newget it... software all the time... Why cant you get new requests as frequently? These are small and important
  • 83. Cant wait!
  • 84. Sprints arentworking for us anymore...
  • 85. Yeah... its gettingSprints arent On our way too.working for us anymore...
  • 86. Yeah... its gettingSprints arent On our way too.working for us Well be glad to switch to a anymore... flowish method
  • 87. Flow
  • 88. Flow
  • 89. It worked!
  • 90. Scrum but...
  • 91. Not Scrum at all!
  • 92. Not Scrum at all!and...
  • 93. It worked!Changesmade sense
  • 94. It worked!Changesmade sense were well thought
  • 95. It worked! Changescame fromretrospectives
  • 96. 1 week
  • 97. 2 weeks
  • 98. 3 weeks
  • 99. 4 weeks
  • 100. Missing something...
  • 101. Chronic problems?
  • 102. Never happen!
  • 103. Hmm! So we can...
  • 104. Drop retrospectives!
  • 105. It got bad...
  • 106. And worse...
  • 107. Terrible, really!
  • 108. Nothing happening
  • 109. Less pressure
  • 110. Except for bugs
  • 111. Metrics?
  • 112. Velocity!
  • 113. Flow without metrics -
  • 114. What happened?
  • 115. What happened? (we figured out later...)
  • 116. No iterations
  • 117. No iterations => no goal
  • 118. No iterations => no goal =>less motivation
  • 119. Less motivation => upset team
  • 120. Less motivation => upset team ... how to fix it?
  • 121. Look for other motivation!
  • 122. Lets go faster!
  • 123. and faster
  • 124. and faster!
  • 125. Agile processes promote sustainable development.
  • 126. Agile processes promote sustainable development.This team, though...
  • 127. More points =>
  • 128. Less points =>
  • 129. Stress++
  • 130. It got bad
  • 131. Seriously bad
  • 132. Did they notice?
  • 133. Did I say...
  • 134. “I can see a problem...
  • 135. …it must bejust me, tho...”
  • 136. Was it the only problem?
  • 137. challenges--
  • 138. challenges--isolation++
  • 139. challenges-- communication--isolation++
  • 140. challenges--technical debt++ communication-- isolation++
  • 141. challenges--technical debt++ communication-- bugs++ isolation++
  • 142. “but the PO wants us to deliver points!” My precioussss points
  • 143. Did they ever ask?
  • 144. No!
  • 145. That brought serious consequences
  • 146. That brought serious consequences challenges--technical debt++ communication-- bugs++ isolation++
  • 147. How do we change it?
  • 148. How do we change it?We need goals andwe need to retake retrospectives!
  • 149. How do we change it?We need goals andwe need to retake We can make a calendar retrospectives! and demand that the client group similar stories for us
  • 150. How do we change it?We need goals andwe 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!
  • 151. Unfortunately, the timebox herealso got in our wayMore about it on the paper!
  • 152. Unfortunately, the timebox herealso got in our wayMore about mo re it on the A lot paper!
  • 153. The message I wish you got from this talk is...More about mo re it on the A lot paper!
  • 154. Good solutions... emerge!
  • 155. It doesnt matter the
  • 156. Does it workfor your team?
  • 157. Is it animprovement?
  • 158. Thats what matters!
  • 159. Improving has to bea neverending story
  • 160. Just...
  • 161. Just... Cecilia Fernandes @cecifernandes