Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Plan-ID:
Replaced by JS

Why Retrospectives? (#46)

Ask 'Why do we do retrospectives?'
Source: Pete Roessler
Go back to the roots and start into the retrospective by asking 'Why do we do this?' Write down all answers for everyone to see. You might be surprised.

Expectations (#62)

What can others expect of you? What can you expect of them?
Source: Valerie Santillo
Give each team member a piece of paper. The lower half is blank. The top half is divided into two sections:
  • What my team mates can expect from me
  • What I expect from my team mates
Each person fills out the top half for themselves. When everyone is finished, they pass their paper to the left and start reviewing the sheet that was passed to them. In the lower half they write what they personally expect from that person, sign it and pass it on.
When the papers made it around the room, take some time to review and share observations.

BYOSM - Build your own Scrum Master (#94)

The team assembles the perfect SM & takes different points of view
Source: Fabian Schiller
Draw a Scrum Master on a flipchart with three sections on him/her: brain, heart, stomach.
  • Round 1: 'What properties does your perfect SM display?'
    Ask them to silently write down one trait per note. Let participants explain their notes and put them on the drawing.
  • Round 2: 'What does the perfect SM have to know about you as a team so that he/she can work with you well?'
  • Round 3: 'How can you support your SM to do a brilliant job?'
You can adapt this activity for other roles, e.g. BYOProductOwner.

SMART Goals (#13)

Formulate a specific and measurable plan of action
Source: Agile Retrospectives
Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'.
Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.

Appreciations (#15)

Let team members appreciate each other and end positively
Source: Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'
Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.

(#)


Source:
Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

Created by Corinna Baldauf

Corinna wished for something like Retromat during her Scrummaster years. Eventually she just built it herself in the hope that it would be useful to others, too. Any questions, suggestions or encouragement? You can email her or follow her on Twitter. If you like Retromat you might also like Corinna's blog and her summaries on Wall-Skills.com.

Co-developed by Timon Fiddike

Timon gives Scrum trainings. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. He has used Retromat since 2013 and started to build new features in 2016. You can email him or follow him on Twitter. Photo © Ina Abraham.