Blog | Books | Membership | 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!

Preparing your first remote retrospective? This might help.
There's a new Retromat book geared towards beginners!

Check out "Plans for Retrospectives"

(Looking for the Print Retromat?)
Replaced by JS

Outcome Expectations (#81)

Everyone states what they want out of the retrospective
Source: Inspired by Jim & Michele McCarthy
Everyone in the team states their goal for the retrospective, i.e. what they want out of the meeting. Examples of what participants might say:
  • I'm happy if we get 1 good action item
  • I want to talk about our argument about unit tests and agree on how we'll do it in the future
  • I'll consider this retro a success, if we come up with a plan to tidy up $obscureModule
[You can check if these goals were met if you close with activity #14.]

[The Meet - Core Protocol, which inspired this activity, also describes 'Alignment Checks': Whenever someone thinks the retrospective is not meeting people's needs they can ask for an Alignment Check. Then everyone says a number from 0 to 10 which reflects how much they are getting what they want. The person with the lowest number takes over to get nearer to what they want.]

Learning Wish List (#128)

Create a list of learning objectives for the team
Source: Tim Ottinger
Hand out pens and paper. Each participant writes down what they wish their coworkers would learn (as a team - no need to name individual people). When everyone is done, collect all items on a board and count how often each one appears. Pick the top three things as learning objectives, unless the team's discussion leads somewhere else.

Brainwriting (#66)

Written brainstorming levels the playing field for introverts
Source: Prof. Bernd Rohrbach
Pose a central question, such as 'What actions should we take in the next iteration to improve?'. Hand out paper and pens. Everybody writes down their ideas. After 3 minutes everyone passes their paper to their neighbour and continues to write on the one they've gotten. As soon as they run out of ideas, they can read the ideas that are already on the paper and extend them. Rules: No negative comments and everyone writes their ideas down only once. (If several people write down the same idea, that's okay.)
Pass the papers every 3 minutes until everyone had every paper. Pass one last time. Now everyone reads their paper and picks the top 3 ideas. Collect all top 3's on a flip chart for the next phase.

Chaos Cocktail Party (#61)

Actively identify, discuss, clarify and prioritize a number of actions
Source: Suzanne Garcia via Malte Foegen
Everyone writes one card with an action that they think is important to do - the more specific (SMART), the better. Then team members go around and chat about the cards like in a cocktail party. Every chat pair discusses the actions on their two cards. Stop the chatting after 1 minute. Each chat pair splits 5 points between the two cards. More points go to the more important action. Organize 3 to 5 rounds of chats (depending on group size). At the end everyone adds up the points on their card. In the end the cards are ranked by points and the team decides how much can be done in the next iteration, pulling from the top.

Addendum: In many settings you might want to randomly switch the cards in the beginning and between discussions. In this way, neither of the point splitting parties has a stake in which of the cards gets more points. This is an idea by Dr. Sivasailam “Thiagi” Thiagarajan via Paul Tevis

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.