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!

Preparing your first remote retrospective? This might help.
Plan-ID:
Replaced by JS

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
  • Address concerns, e.g. by writing them down and setting them - physically and mentally - aside
  • What's something that caused problems last iteration?
  • If you could change one thing about the last iteration what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

Tell a Story with Shaping Words (#93)

Each participant tells a story about the last iteration that contains certain words
Source: Philip Rogers
Provide everyone with something to write down their story. Then introduce the shaping words, which influence the story to be written:
  • If the last iteration could have been better:
    You set a couple of shaping words, e.g. such as 'mad, sad, glad' or 'keep, drop, add'. Additionally they have to write their story in first person. This avoids blaming others.
  • If the last iteration was successful:
    The team can either choose their own set of words or you can provide random words to unleash the team's creativity.
Now each participant writes a story of no more than 100 words about last iteration. They have to use each shaping word at least once. Timebox this to 5-10 minutes.
When everyone's finished, they read out their stories. Afterwards lead a discussion about common themes of the stories.

Pessimize (#74)

If we had ruined the last iteration what would we have done?
Source: Judith Andresen
You start the activity by asking: 'If we had completely ruined last iteration what would we have done?' Record the answers on a flip chart. Next question: 'What would be the opposite of that?' Record it on another flip chart. Now ask participants to comment the items on the 'Opposite'-chart by posting sticky notes answering 'What keeps us from doing this?'. Hand out different colored sticky notes to comment on the comments, asking 'Why is it like this?'.

Low Hanging Fruit (#63)

Visualize promise and ease of possible courses of actions to help pick
Source: Tobias Baldauf
Reveal a previously drawn tree. Hand out round index cards and instruct participants to write down the actions they would like to take - one per card. When everyone's finished, collect the cards, shuffle and read them out one by one. Place each 'fruit' according to the participants' assessment:
  • Is it easy to do? Place it lower. Hard? More to the top.
  • Does it seem very beneficial? Place it more to the left. Value is dubious at best? To the right.
The straightforward choice is to pick the bottom left fruit as action items. If this is not consensus, you can either have a short discussion to agree on some actions or dot vote.

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


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.