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

Check out the Retromat ebook!
Replaced by JS

Last Retro's Actions Table (#84)

Assess how to continue with last retro's actions
Source: Sven Winkler
Create a table with 5 columns. The first column lists last retro's action items. The other columns are headed 'More of', 'Keep doing', 'Less of' and 'Stop doing'. Participants place 1 sticky note per row into the column that states how they want to proceed with that action. Afterwards facilitate a short discussion for each action, e.g. asking:
  • Why should we stop doing this?
  • Why is it worth to go further?
  • Are our expectations satisfied?
  • Why do opinions vary that much?

Hit the Headlines (#119)

Which sprint events were newsworthy?
Source: Thomas Guest
Collect some news headlines in advance and take them to the retrospective to serve as examples. Try to gather a mixture of headlines: factual, opinion, review. Place the headlines where everyone can see them. Hand out sticky notes. Give team members 10 minutes to come up with their own headlines describing newsworthy aspects of the sprint. Encourage short, punchy headlines.
Stick the completed headlines to a whiteboard. If any cover the same news item, combine them. If any are unclear, ask the reporter for details. Vote on which news items to discuss and analyse in more depth.

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.

Three by Three (#125)

Build on each other's ideas to create a great action item
Source: Simon Tomes
This silent brainstorming technique helps the team come up with truly creative solutions and gives quiet people equal footing:

  • Everyone writes 3 sticky notes with 1 action idea each
  • Go around the room and pitch each idea in 15 seconds
  • Gather all stickies so that everyone can see them
  • Each team member adds their name to the sticky note that inspires them the most
  • Take off all ideas without a name on them
Repeat this process 2 more times. Afterwards, everyone can dot vote to determine which action(s) the team is going to implement.

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.