About | Donate | Books
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!
Run great agile retrospectives: Get all activities and more for your ebook reader!

Check out the Retromat ebook!
Current Plan ID:
Replaced by JS

Retrospective Cookies (#27)

Take the team out to eat and spark discussion with retrospective fortune cookies
Source: Adam Weisbart
Invite the team out to eat, preferably Chinese if you want to stay in theme ;) Distribute fortune cookies and go around the table opening the cookies and discussing their content. Example 'fortunes':
  • What was the most effective thing you did this iteration, and why was it so successful?
  • Did the burndown reflect reality? Why or why not?
  • What do you contribute to the development community in your company? What could you contribute?
  • What was our Team's biggest impediment this iteration?
You can order retrospective cookies from Weisbart or bake your own, e.g. if English is not the team's native language.

Take a Walk (#28)

Go to the nearest park and wander about and just talk
Source: Corinna Baldauf
Is there nice weather outside? Then why stay cooped up inside, when walking fills your brain with oxygen and new ideas 'off the trodden track'. Get outside and take a walk in the nearest park. Talk will naturally revolve around work. This is a nice break from routine when things run relatively smoothly and you don't need visual documentation to support discussion. Mature teams can easily spread ideas and reach consensus even in such an informal setting.

Take a Walk (#28)

Go to the nearest park and wander about and just talk
Source: Corinna Baldauf
Is there nice weather outside? Then why stay cooped up inside, when walking fills your brain with oxygen and new ideas 'off the trodden track'. Get outside and take a walk in the nearest park. Talk will naturally revolve around work. This is a nice break from routine when things run relatively smoothly and you don't need visual documentation to support discussion. Mature teams can easily spread ideas and reach consensus even in such an informal setting.

Invite a Customer (#56)

Bring the team into direct contact with a customer or stakeholder
Source: Nick Oostvogels
Invite a customer or internal stakeholder to your retrospective.Let the team ask ALL the questions:
  • How does the client use your product?
  • What makes them curse the most?
  • Which function makes their life easier?
  • Let the client demonstrate their typical workflow
  • ...

Feedback Sandwich (#111)

Learn how to raise constructive criticism with your team mates in a trusting and positive way
Source: Diana Hennessy
Try this activity to help teams that are only ever saying nice things to each other and seem reluctant to raise concerns about each other. If they are always keeping the peace, they miss growth opportunities and issues may fester. Feedback Sandwich is a way to learn how to give and receive potentially critical feedback. It goes like this:

Team members sit in a circle and take turns receiving the feedback. The team member who's turn it is is not allowed to say anything until each person finishes their 3 points. Once finished, the person receiving the feedback can only say 'Thank You'. Each takes turns receiving the feedback until all team members have participated.

Several days before the retro, you send out the following information to team members so that they can prepare:
'Think about the below questions for each of your team mates and prepare an answer before the session:
  1. What is something you really admire/respect about this person or something you think they do really well in a professional capacity?
  2. What is something you think is a weakness for this person? (Perhaps something they don't do so well, need to work on etc.)
  3. What is something you feel this person shows promise in, but could perhaps work on a little more to truly shine at it?
These questions are quite open in that you can draw on both technical and soft skills for each team member. So it might be that you choose to highlight a specific technical strength/weakness, or you might comment on someone's professional conduct, approachability, teaching skills, communication skills, etc.

Disclaimer: This activity is not about being nasty, or mean. It's intended to help the team get to know each other better and to improve on how we work individually and as a group. The idea is not to cause offence, but rather to understand how your team sees you and perhaps take something away to work on. It is up to you what you take away from it, you are free to ignore people's suggestions if you do not agree with them. Please deliver your feedback kindly and remember to thank your team for their feedback about you.'

Sacred Cow (#131)

What is the organization clinging to that doesn't make sense anymore?
Source: Ani Angelini
This activity is great for shaking up routine in places that do things the way they've always done them. Introduce it by telling the story of the sacred cows, preferably the long epic version here. Here's the gist:

'In some cultures cows were sacred, never to be killed for food or any other reason. The cows roamed free, leading a happy life and usually died of old age. With rare exceptions such as one fateful spring in a city far, far away ...

This particular city came under siege by a superior enemy force. All the citizens withdrew into the safety of the city walls but there was nothing going in or out of the city. Days turned into weeks and the citizens grew hungry and desperate. There was hardly any food left. They did, however, have a lot of sacred cows. Unfortunately, the idea of killing a sacred cow was taboo and also a horrible crime.

But these were not ordinary times. If the attackers were to succeed they would certainly kill the cows. So wasn’t it a better if the soldiers ate some of the cows to defend the town and maybe safe the people and the rest of the cows? In the end, the town had to re-evaluate their stance on cows. They thought and acted in ways that were unthinkable before. And it worked. They saved their town and the people in it. Not all the cows, though.’

Hand out sticky notes and ask the participants to write down the sacred cows of their organisation: Things they have always done a certain way without ever asking why.

Go around the group and invite the team to describe their ‘cows’. For big groups, it works best if they break into smaller groups for the discussion and share conclusions later with everyone.

Now it’s time to grab the bull by its horns. What can you do to slaughter a sacred cow? Every person / group proposes 2-3 actions / experiments. When all suggestions are on the table everyone has to sign at least one initiative as a supporter. Initiatives without supporters are discarded.

To close the retrospective, invite the group to gather in a round. Set the timer to 10 minutes and prepare a token. Ask them to share what they've gotten from the retrospective. Sharing is voluntary: if someone wants to share they have to ask for the token.

(#)


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

As Integral Coach and Agile Coach, Timon 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.