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!

Preparing your first remote retrospective? This might help.
Run great agile retrospectives: Get all activities and more for your ebook reader!

Check out the Retromat ebook!

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

Retro Wedding (#89)

Collect examples for something old, new, borrowed and blue
Source: Jordan Morris, via Todd Galloway
Analogue to an anglo-american wedding custom ask the team to give examples for the following categories:
  • Something Old
    Positive feedback or constructive criticism on established practice
  • Something New
    Positive feedback or constructive criticism on experiments in progress
  • Something Borrowed
    Tool/idea from another team, the Web or yourself for a potential experiment
  • Something Blue
    Any blocker or source of sadness
One example per sticky note. There's only one rule: If someone contributes to the 'Something Blue' column, s/he must also have a positive comment in at least 1 other column.

Everyone posts their stickies in the appropriate column on the board and describes it briefly.

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.

SMART Goals (#13)

Formulate a specific and measurable plan of action
Source: Agile Retrospectives
Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'.
Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.

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.