Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using Retrospectives to build better Agile teams

2,620 views

Published on

Retrospectives are a vital part of a successful agile development process. They provide the opportunity for the team to pause on a regular basis to assess progress and process, adjust and make improvements, rather than waiting until the end of a project to gather up lessons learnt.

This presentation explains why the Retrospective is a key tool in anyone’s iterative development toolkit. It gives an overview of Agile Iteration Retrospectives, their importance and how to structure them.

Published in: Technology, Business
  • Be the first to comment

Using Retrospectives to build better Agile teams

  1. 1. Agile Retrospectives<br />Anthony Boobier<br />Email: anthony.boobier@optimation.co.nz<br />
  2. 2. “Here is Edward Bear, coming downstairs now, bump, bump, bump, bump, on the back of his head, behind Christopher Robin. It is as far as he knows, the only way of coming downstairs, but sometimes he feels that there really is another way, if only he could stop bumping for a moment and think of it”<br />A.A. Milne, Winnie-the-Pooh. London: Puffin Books, 1926<br />Quote used by Norm Kerth<br />
  3. 3. What is it?<br /><ul><li>Inspect and Adapt are critical parts of Agile Process but…
  4. 4. They are methods focussed on Product
  5. 5. Retrospective is team-focussed
  6. 6. Way of ensuring we Inspect and Adapt the following
  7. 7. Methods
  8. 8. Engineering Practices
  9. 9. Teamwork</li></li></ul><li>Preparation<br /><ul><li>Team Working Agreements
  10. 10. Keep focus
  11. 11. Needs to be a safe environment
  12. 12. Attendees: Team, Scrumaster
  13. 13. Should the customer attend? That depends…</li></li></ul><li>Ensure it has Structure<br />Set the Stage<br />Gather Data<br />Generate Insights<br />Decide what to do<br />Close the Retrospective<br />
  14. 14. Set The Stage !<br />Set a theme for the Retrospective<br />A word for the iteration<br />EPIC, OK, TRUCKING-ON, MOMENTUM, RUNNING, INTERRUPTED, MARVELLOUS, RUSHED, PROMISING, PAINFUL, PROGRESS, BOGGY,EXCELLENT, ZOOM, FRUSTRATING, SLOW<br />Assess Actions from previous retrospective<br />Reminders and Re-enforcers<br />
  15. 15. Gather Data<br /><ul><li>Things that happened and how we responded
  16. 16. People see things very differently
  17. 17. Key events timeline
  18. 18. What did we commit to delivering?
  19. 19. Stories delivered
  20. 20. Test cases passed
  21. 21. Defects raised</li></li></ul><li>Generate Insights !<br />What were the patterns? Why were things the way they were?<br />
  22. 22. Decide what to do<br /><ul><li>What do we want to do in our next iteration to meet our goal?
  23. 23. Be realistic
  24. 24. Pick no more than 3 things
  25. 25. Use Dot voting
  26. 26. Sprint plan
  27. 27. Implementation backlog</li></li></ul><li>Benefits: Building Winning Teams<br />
  28. 28. Further Reading<br />Agile Retrospectives: Making Good Teams Great. Esther Derby & Diana Larsen<br />Project Retrospectives: A Handbook for Team Reviews. Norman L. Kerth<br />Collaboration Explained. Jean Tabaka<br />

×