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

Know your neighbour - Opening (#108)

How did your right neighbour feel during the iteration
Source: Fabián Lewkowicz
Ask each team member to briefly describe how their right neighbour felt during the iteration. Their neighbour confirms or corrects the guess.
Once all participants shared their best guess about how their teammates felt, you get an idea of how connected they are, how communication is flowing in your team and if people are aware of the feelings expressed, in some way, by others.

Consider closing with activity #109.

Lines of Communication (#86)

Visualize how information flows in, out and around the team
Source: Tarmo Aidantausta
Is information not flowing as well as it needs to? Do you suspect bottlenecks? Visualize the ways information flows to find starting points for improvements. If you want to look at one specific flow (e.g. product requirements, impediments, ...) check out Value Stream Mapping (#79). For messier situations try something akin to Cause-Effect-Diagrams (#25).
Look at the finished drawing. Where are delays or dead ends?

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.

Merge (#21)

Condense many possible actions down to just two the team will try
Source: Lydia Grawunder & Sebastian Nachtigall
Hand out index cards and markers. Tell everyone to write down the two actions they want to try next iteration - as concretely as possible (SMART). Then everyone pairs up with their neighbor and both together must merge their actions into a single list with two actions. The pairs form groups of 4. Then 8. Now collect every group's two action items and have a vote on the final two.

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