Sprint Restrospective

Attendees: Whole Scrum team (including dev team, ScrumMaster and Product owner)

Duration: 1 hour

When: Last day of a sprint after all the stories are ‘Done’

Why:

  1. Inspect & Adapt
  2. Improve
  3. Learn
  4. Process Improvements

What:

  1. Scrum Master facilitates
  2. Scrum Team discusses ‘what went well’, ‘what can be improved’ and ‘New Ideas / suggestions’
  3. For what went well – appreciate and encourage the team / team members.
  4. For what can be improved – team inspects and tries to come up with solutions or process improvements
  5. Welcome suggestions
  6. Continuous improvement is the main idea behind sprint retrospectives.

Helpful Tip(s):

  1. Sprint Retrospective should not be used as a forum to blame each other.
  2. Try to keep the Sprint retrospective closed to only the scrum team members as that will give them a comfortable environment to communicate their views.
  3. Bring up the ‘suggestions’ or ‘what could be improved’ cards from the last retrospective and get the scrum team’s views on how the team has improved on those.
  4. Keep changing the format of the sprint retrospectives once in a while, otherwise people may get bored soon. For more ideas to run retrospectives please visit: Retrospective Ideas

 

Like my blog? 

 

One thought on “Sprint Restrospective

Leave a Reply

Your email address will not be published. Required fields are marked *