During the retrospective team reviews what went well (keep) and
what went poorly (improvement).
When mentioning improvement it means that for each “issue” team has
to write action items (voting for them) and the best action items
will be recorded to be examined in the next retrospective.
Indeed, I used to show the performance of the sprint before starting the
retrospective. Nowadays, I added a previous step at the first instances of retrospective,
which is how was the performance of the team about the methodology.
Later I only conduct retrospectives driven the attention to the issues but without
changing the way to do them until I heard about Retr-o-mat (thanks to Ariel Ber)
Retrospectives are my favourite agile meeting and because of that I’m always searching
for new ideas.
Retr-o-mat split in five stages the retrospective:
- Set the stage
Set the goal; Give people time to “arrive” and get into the right mood
- Gather data
Help everyone remember; Create a shared pool of information (everybody sees the world differently)
- Generate insight
Why did things happen the way they did?; Identify patterns; See the big picture
- Decide what to do
Pick a few issues to work on and create concrete action plans of how you’ll address them
- Close the retrospective
Clarify follow-up; Appreciations; Clear end; How could the retrospectives improve?
The author of Retr-O-Mat is Corinna Baldauf and if you want to follow her twitter is
Head to the website of Retr-O-Mat and enjoy it!!!
Last but not least, “if you want to learn more about agile retrospectives, subscribe to this program”