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!
Retromat Miroboard Mega Template
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Constellation - Opening (#52)

Let the participants affirm or reject statements by moving around
Source: Lyssa Adkins via Luis Goncalves
Place a circle or sphere in the middle of a free space. Let the team gather around it. Explain that the circle is the center of approval: If they agree to a statement they should move towards it, if they don't, they should move as far outwards as their degree of disagreement. Now read out statements, e.g.
  • I feel I can talk openly in this retrospective
  • I am satisfied with the last iteration
  • I am happy with the quality of our code
  • I think our continuous integration process is mature
Watch the constellations unfold. Ask questions about people's observations, such as which constellations were surprising.
This can also be a closing activity (#53).
►
◄
Gather data

Appreciative Inquiry (#65)

Lift everyone's spirit with positive questions
Source: Doug Bradbury, adapted for SW development by Corinna Baldauf
This is a round-based activity. In each round you ask the team a question, they write down their answers (gives everyone time to think) and then read them out to the others.
Questions proposed for Software Development teams:
  1. When was the last time you were really engaged / animated / productive? What did you do? What had happened? How did it feel?
  2. From an application-/code-perspective: What is the awesomest stuff you've built together? What makes it great?
  3. Of the things you built for this company, which has the most value? Why?
  4. When did you work best with the Product Owner? What was good about it?
  5. When was your collaboration best?
  6. What was your most valuable contribution to the developer community (of this company)? How did you do it?
  7. Leave your modesty at the door: What is the most valuable skill / character trait you contribute to the team? Examples?
  8. What is your team's most important trait? What sets you apart?

('Remember the Future' (#37) works well as the next step.)
►
◄
Generate insights

Company Map (#68)

Draw a map of the company as if it was a country
Source: Judith Andresen
Hand out pens and paper. Pose the question 'What if the company / department / team was territory? What would a map for it look like? What hints would you add for save travelling?' Let participants draw for 5-10 minutes. Hang up the drawings. Walk through each one to clarify and discuss interesting metaphors.
►
◄
Decide what to do

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.
►
◄
Close the retrospective

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.