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

Appreciative Goal (#36)

State an affirmative goal for the session
Source: Diana Larsen
Concentrate on positive aspects instead of problems by setting an affirmative goal, e.g.
  • Let's find ways to amplify our strengths in process and teamwork
  • Let's find out how to extend our best uses of engineering practices and methods
  • We'll look at our best working relationships and find ways to build more relationships like that
  • We'll discover where we added the most value during our last iteration to increase the value we'll add during the next

Proud & Sorry (#33)

What are team members proud or sorry about?
Source: Agile Retrospectives
Put up two posters labeled 'proud' and 'sorry'. Team members write down one instance per sticky note. When the time is up have everyone read out their note and post it to the appropriate poster.
Start a short conversation e.g. by asking:
  • Did anything surprise you?
  • What patterns do you see? What do they mean for you as a team?

Force Field Analysis (#115)

Analyse the factors that support and hinder a particular initiative
Source: Derek Neighbors, via Joel Edwards
State the topic that the team will explore in depth (deployment processes, peer-programming, Definition of Done, ...). Break the room into groups of 3-4 people each. Give them 5-7 minutes to list all contributing factors, drivers and actions that make up the topic. Go around the room. Each group reads 1 of their sticky notes and puts it up inside the force field until no group has any items left. Cluster or discard duplicates. Repeat the last 2 steps for factors that inhibit or restrain the topic from being successful or being as effective as it could be. Review all posted items. Add any that are missing.

To identify the most influential factors, everybody gets to 4 votes - 2 for contributing factors, 2 for inhibitors. Tally the votes and mark the top 2x2 factors with big arrows. Spend the last 15-20 mins of the session brainstorming ways to increase the top driving factors and decrease the top restraining factors.

Circle of Questions (#11)

Asking and answering go around the team circle - an excellent way to reach consensus
Source: Agile Retrospectives
Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!

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.