Sprint Retrospective

Sprint Retrospective

October 5, 2017 Agile 0

A good Sprint Retrospective is an interesting thing. The goal of a ‘Retro’ is to arrive at one to three improvement stories for the team so that it can be more productive in the future.

Be careful you don’t fall in a Retro-trap where you basically group-whine for an hour, feel cathartic and have the feeling it was a great retrospective together. It might be great for your emotions or team-building, but if it happens a lot you won’t see any measurable progress.

Therefore, it’s nice to have a sort of guide to help you through the Retrospective. The stuff I see online are always very emotional, ‘fun’ or playful – which are characteristics I don’t always think are suited for a professional environment. (‘You have to give a compliment to the person next to you! yay!‘ – ugh.). This is my own ‘Professional Retro-playbook’ based on the Retromat structure. (Even though I think most exsercises on there feel like they’ve been invented by a first-year, soft-shelled HR-psychologist hybrid)


Retrospective Playbook

Goal Retrospective:

·        Inspect how the last Sprint went with regards to people, relationships, process and tools.

·        Identify and order the major items that went well and potential improvements.

·        Create a plan for implementing improvements to the way the Scrum Team does its work.

Set the stage (Scrum Master)
Reason for Retro
Gather data
What worked well?


What didn’t work so well?


Generate insights
What could be improved?


Decide what to do
What will we commit to in the next sprint?


How will we commit?


Create User Stories with High Priority
Close the Retrospective