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

425 views
375 views

Published 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 then decided they needed iterations back.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
425
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

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

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

×