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!
Retromat Miroboard Mega Template
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Postcards (#42)

Participants pick a postcard that represents their thoughts / feelings
Source: Corinna Baldauf
Bring a stack of diverse postcards - at least 4 four times as many as participants. Scatter them around the room and instruct team members to pick the postcard that best represents their view of the last iteration. After choosing they write down three keywords describing the postcard, i.e. iteration, on index cards. In turn everyone hangs up their post- and index cards and describes their choice.
►
◄
Gather data

Mad Sad Glad (#7)

Collect events when team members felt mad, sad, or glad and find the sources
Source: Agile Retrospectives
Put up three posters labeled 'mad', 'sad', and 'glad' (or >:(, :(, :) alternatively). Team members write down one event per color coded card, when they've felt that way. When the time is up have everyone post their cards to the appropriate posters. Cluster the cards on each poster. Ask the group for cluster names.
Debrief by asking:
  • What's standing out? What's unexpected?
  • What was difficult about this task? What was fun?
  • What patterns do you see? What do they mean for you as a team?
  • Suggestions on how to continue?
►
◄
Generate insights

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.
►
◄
Decide what to do

Systemic Consensus (#103)

Check for resistance instead of approval
Source: Georg Paulus, Siegfried Schrotta \& Erich Visotschnig via Corinna Baldauf
Do you have a hotly debated matter with several possible ways to go and the team can't agree on any of them? Instead of trying to find a majority for a way that will create winners and losers, try what happens if you turn the decision inside out:
Draw a table with the voters in the left-most column and proposals on top. Now everybody has to fill in their resistance towards each proposal. 0 means 'no resistance - this is what I want', up to 10, meaning 'shoot me now'. Give the least hated solution a try.
►
◄
Close the retrospective

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. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. 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.