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!
OMG! Print Retromats are back! Get yours fresh off the printer

More about the Retromat Print Edition

(Looking for the ebook?)
Replaced by JS

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
  • Address concerns, e.g. by writing it down and setting it - physically and mentally - aside
  • In this retrospective - If you were a car, what kind would it be?
  • What's something that caused problems last sprint?
  • If you could change one thing about the last sprint what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

Like to like (#6)

Participants match quality cards to their own Start-Stop-Continue-proposals
Source: Agile Retrospectives
Preparation: ca. 20 quality cards, i.e. colored index cards with unique words such as fun, on time, clear, meaningful, awesome, dangerous, nasty
Each team member has to write at least 9 index cards: 3 each with things to start doing, keep doing and stop doing. Choose one person to be the first judge. The judge turns the first quality card. From their own cards each member chooses the best match for this word and places it face down on the table.The last one to choose has to take their card back on their hand. The judge shuffles all submitted cards, turns them one by one and rules the best fit = winning card. All submitted cards are discarded. The submitter of the winning card receives the quality card. The person left of the judge becomes the new judge.
Stop when everyone runs out of cards (6-9 rounds). Whoever has the most quality cards wins. Debrief by asking for takeaways.
(Game is based on 'Apples to Apples')

Undercover Boss (#58)

If your boss had witnessed the last iteration, what would she want you to change?
Source: Love Agile
Imagine your boss had spent the last iteration - unrecognized - among you. What would she think about your interactions and results? What would she want you to change?
This setting encourages the team to see themselves from a different angle.

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.

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives
Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.

(#)


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.