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

Emoticon Project Gauge (#32)

Help team members express their feelings about a project and address root causes early
Source: Andrew Ciccarelli
Prepare a flipchart with faces expressing various emotions such as:
  • shocked / surprised
  • nervous / stressed
  • unempowered / constrained
  • confused
  • happy
  • mad
  • overwhelmed
Let each team member choose how they feel about the project. This is a fun and effective way to surface problems early. You can address them in the subsequent phases.

Timeline (#4)

Participants write down significant events and order them chronologically
Source: Agile Retrospectives
Divide into groups with 5 or less people each. Distribute cards and markers. Give participants 10min to note down memorable and / or personally significant events. It's about gathering many perspectives. Consensus would be detrimental. All participants post their cards and order them. It's okay to add cards on the fly. Analyze.
Color Coding can help to see patterns, e.g.:
  • Emotions
  • Events (technical, organization, people, ...)
  • Function (tester, developer, manager, ...)

Brainstorming / Filtering (#10)

Generate lots of ideas and filter them against your criteria
Source: Agile Retrospectives
Lay out the rules of brainstorming, and the goal: To generate lots of new ideas which will be filtered after the brainstorming.
  • Let people write down their ideas for 5-10 minutes
  • Go around the table repeatedly always asking one idea each, until all ideas are on the flip chart
  • Now ask for filters (e.g. cost, time investment, uniqueness of concept, brand appropriateness, ...). Let the group choose 4.
  • Apply each filter and mark ideas that pass all 4.
  • Which ideas will the group carry forward? Does someone feel strongly about one of the ideas? Otherwise use majority vote.
The selected ideas enter Phase 4.

Planning Poker Voting (#99)

Use your Planning Poker cards for un-influenced voting
Source: Andreas Ratsch
If you've got very influential and / or shy team members you can re-use Planning Poker cards to vote simultaneously:

Write all suggested actions on sticky notes and put them onto a wall. Hand out an ordered deck of Planning Poker cards to each participant. Count the proposals and remove that many cards from the back of the card decks. If you've got 5 suggestions you might have cards '1', '2', '3', '5', and '8'. This depends on your deck (some have a '1/2' card). It doesn't matter, as long as all participants have the same set of values.

Explain the rules: Choose a card for each suggestion. Choose a low value if the action is not worth doing in your opinion. Choose a high value if the action is worth starting next iteration.

Give them a minute to sort out their internal ranking and then present the first suggested action. Everybody chooses a card and they reveal them at the same time. Add the numbers from all cards and write the sum onto the action. Remove the used poker cards. Repeat this for all actions. If you have more actions than poker values the players can show 'no card' (counting 0) for the appropriate number of times.

Implement the action with the highest sum in the next iteration. Add more actions only if there's team consensus to do so.

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