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

Emoticon Project Gauge (#32)

Help team members express their feelings about a project and address root causes early
Source: Andrew Ciccarelli
Prepare a flipchart with faces expressing various emotions such as:
  • shocked / surprised
  • nervous / stressed
  • unempowered / constrained
  • confused
  • happy
  • mad
  • overwhelmed
Let each team member choose how they feel about the project. This is a fun and effective way to surface problems early. You can address them in the subsequent phases.

Analyze Stories (#5)

Walk through each story handled by the team and look for possible improvements
Source: Corinna Baldauf
Preparation: Collect all stories handled during the iteration and bring them along to the retrospective.
In a group (10 people max.) read out each story. For each one discuss whether it went well or not. If it went well, capture why. If not discuss what you could do differently in the future.
Variants: You can use this for support tickets, bugs or any combination of work done by the team.

Learning Matrix (#9)

Team members brainstorm in 4 categories to quickly list issues
Source: Agile Retrospectives
After discussing the data from Phase 2 show a flip chart with 4 quadrants labeled ':)', ':(', 'Idea!', and 'Appreciation'. Hand out sticky notes.
  • The team members can add their input to any quadrant. One thought per sticky note.
  • Cluster the notes.
  • Hand out 6-10 dots for people to vote on the most important issues.
This list is your input for Phase 4.

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.