What Is A Sprint Retrospectives


Published on

This is a short introduction to the practice of Sprint Retrospective in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

What Is A Sprint Retrospectives

  1. 1. Sprint Retrospectives An Introduction
  2. 2. Planning Meeting Review Meeting Retrospective SPRINT
  3. 3. Sprint Retrospectives <ul><li>All team members reflect on the past sprint </li></ul><ul><li>Make continuous process improvement </li></ul><ul><li>Two main questions are asked in the sprint retrospective: </li></ul><ul><ul><li>What went well during the sprint? </li></ul></ul><ul><ul><li>What could be improved in the next sprint? </li></ul></ul><ul><li>1 hour per week – recommended </li></ul>
  4. 4. Types of Retrospectives <ul><li>Sprint End Retrospectives </li></ul><ul><li>Big End of Project Retrospectives </li></ul><ul><li>Event Retrospectives </li></ul>
  5. 5. Should Product Owner be in Retrospectives? <ul><li>Yes, if needed </li></ul><ul><li>It is recommended that Product Owner part of meeting be done first and then the team discusses freely what went right or wrong </li></ul>
  6. 6. Role of Scrum Master <ul><li>Opinion 1 : The scrum master is not in this meeting to provide answers, but to facilitate the team’s search for better ways for the scrum process to work for it. </li></ul><ul><li>Opinion 2 : Scrum Master can answer questions, especially if the team feels, she is not doing enough to remove obstacles. It helps if Scrum Master provides answers for the same herself. </li></ul>
  7. 7. Ground Rules <ul><li>No interruptions </li></ul><ul><li>No raising of voice or tempo </li></ul><ul><li>Safety Check </li></ul><ul><li>Silence Zones </li></ul>
  8. 9. The Prime Directive <ul><li>Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand. </li></ul>
  9. 10. Approaches <ul><li>SSC Approach </li></ul><ul><li>Worked/ Not Worked Approach </li></ul><ul><li>Appreciative Inquiry </li></ul>
  10. 11. Appreciative Inquiry – Gather Data <ul><li>Tell us a story about a time this week when you felt particularly energized by our work. </li></ul><ul><li>What did you value most about your contributions this week? </li></ul><ul><li>What did you value most about the work we’ve done together? </li></ul><ul><li>What metaphor describes this iteration (release or project) best? </li></ul>
  11. 12. Appreciative Inquiry - Insights <ul><li>Imagine we could time travel to the end of the next release. </li></ul><ul><ul><li>When we arrive there and converse with our future selves, we hear that it was the most productive, most satisfying effort we’ve ever worked on. What do you see and hear in that future time? </li></ul></ul><ul><li>What changes did we implement now that resulted in such productive and satisfying work in the future? </li></ul>
  12. 13. Appreciative Inquiry – Try Next <ul><li>Pull out common ideas. Look for patterns, common threads, and compelling ideas, then consider why these hold significance for the team. </li></ul><ul><ul><li>Which ideas and actions build on our successes, meet the situational (or customer) needs, and tap our greatest energy? </li></ul></ul><ul><ul><li>What are we best positioned to try next? </li></ul></ul><ul><ul><li>What do we really want to try (or sustain)? </li></ul></ul><ul><ul><li>Choose three small actions the team [and leaders] </li></ul></ul>