Blog | Books | About
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!
Join 1500+ subscribers and get new activities & tips for retrospectives in your inbox!

Wondering what content you'll get? Look at past emails | Privacy Policy
Replaced by JS

Take a Stand - Opening (#43)

Participants take a stand, indicating their satisfaction with the iteration
Source: Corinna Baldauf, inspired by Christoph Pater
Create a big scale (i.e. a long line) on the floor with masking tape. Mark one end as 'Great' and the other as 'Bad'. Let participants stand on the scale according to their satisfaction with the last iteration. Psychologically, taking a stand physically is different from just saying something. It's more 'real'.
You can reuse the scale if you close with activity #44.

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.)

Cause-Effect-Diagram (#25)

Find the source of problems whose origins are hard to pinpoint and lead to endless discussion
Source: Henrik Kniberg
Write the problem you want to explore on a sticky note and put it in the middle of a whiteboard. Find out why that is a problem by repeatedly asking 'So what?'. Find out the root causes by repeatedly asking 'Why (does this happen)?' Document your findings by writing more stickies and showing causal relations with arrows. Each sticky can have more than one reason and more than one consequence
Vicious circles are usually good starting points for actions. If you can break their bad influence, you can gain a lot.

Outside In (#124)

Turn blaming others into actions owned by the team
Source: Ralph Miarka and Veronika Kotrba
If your team has a tendency to see obstacles outside of their team and influence and primarily wants others to change, you can try this activity:

Draw a big rectangle on the board and another rectangle inside of it, like a picture frame. Hang all complaints and grievances that surfaced in previous phases into the frame.

Now comes the interesting twist: Explain that if they want anything in the outside frame to change, they will have to do something themselves to affect that change. Ask the team to come up with actions they can do. Put these actions into the inner rectangle (near the outer sticky they are addressing).

Feedback Door - Smilies (#23)

Gauge participants' satisfaction with the retro in minimum time using smilies
Source: Boeffi
Draw a ':)', ':|', and ':(' on a sheet of paper and tape it against the door. When ending the retrospective, ask your participants to mark their satisfaction with the session with an 'x' below the applicable smily.

(#)


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. As Integral Coach and Agile Coach he coaches executives, managers, product owners and scrum masters. 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.