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

Check out the Mega Template
Plan-ID:
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

Tell a Story with Shaping Words (#93)

Each participant tells a story about the last iteration that contains certain words
Source: Philip Rogers
Provide everyone with something to write down their story. Then introduce the shaping words, which influence the story to be written:
  • If the last iteration could have been better:
    You set a couple of shaping words, e.g. such as 'mad, sad, glad' or 'keep, drop, add'. Additionally they have to write their story in first person. This avoids blaming others.
  • If the last iteration was successful:
    The team can either choose their own set of words or you can provide random words to unleash the team's creativity.
Now each participant writes a story of no more than 100 words about last iteration. They have to use each shaping word at least once. Timebox this to 5-10 minutes.
When everyone's finished, they read out their stories. Afterwards lead a discussion about common themes of the stories.

Learning Matrix (#9)

Team members brainstorm in 4 categories to quickly list issues
Source: Agile Retrospectives
After discussing the data from Phase 2 show a flip chart with 4 quadrants labeled ':)', ':(', 'Idea!', and 'Appreciation'. Hand out sticky notes.
  • The team members can add their input to any quadrant. One thought per sticky note.
  • Cluster the notes.
  • Hand out 6-10 dots for people to vote on the most important issues.
This list is your input for Phase 4.

Low Hanging Fruit (#63)

Visualize promise and ease of possible courses of actions to help pick
Source: Tobias Baldauf
Reveal a previously drawn tree. Hand out round index cards and instruct participants to write down the actions they would like to take - one per card. When everyone's finished, collect the cards, shuffle and read them out one by one. Place each 'fruit' according to the participants' assessment:
  • Is it easy to do? Place it lower. Hard? More to the top.
  • Does it seem very beneficial? Place it more to the left. Value is dubious at best? To the right.
The straightforward choice is to pick the bottom left fruit as action items. If this is not consensus, you can either have a short discussion to agree on some actions or dot vote.

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.