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

Temperature Reading (#22)

Participants mark their 'temperature' (mood) on a flipchart
Source: Unknown
Prepare a flipchart with a drawing of a thermometer from freezing to body temperature to hot. Each participant marks their mood on the sheet.

Lines of Communication (#86)

Visualize how information flows in, out and around the team
Source: Tarmo Aidantausta
Is information not flowing as well as it needs to? Do you suspect bottlenecks? Visualize the ways information flows to find starting points for improvements. If you want to look at one specific flow (e.g. product requirements, impediments, ...) check out Value Stream Mapping (#79). For messier situations try something akin to Cause-Effect-Diagrams (#25).
Look at the finished drawing. Where are delays or dead ends?

Remember the Future (#37)

Imagine the next iteration is perfect. What is it like? What did you do?
Source: Luke Hohmann
'Imagine you could time travel to the end of the next iteration (or release). You learn that it was the best, most productive iteration yet! How do your future selves describe it? What do you see and hear?' Give the team a little time to imagine this state and jot down some keywords to aid their memory. Then let everyone describe their vision of a perfect iteration.
Follow up with 'What changes did we implement that resulted in such a productive and satisfying future?'Write down the answers on index cards to use in the next phase.

Problem Solving Tree (#96)

Got a big goal? Find the steps that lead to it
Source: Bob Sarni, described by Karen Greaves
Hand out sticky notes and markers. Write the big problem you want to solve onto a note and stick it to the top of a wall or big board. Ask the participants to write down ideas of what they can do to solve the problem. Post them one level below the original problem. Repeat this for each note on the new level. For every idea ask whether it can be done in a single iteration and if everyone understands what they need to do. If the answer is no, break it down and create another level in the problem solving tree.

Once you have lower levels that are well understood and easy to implement in a single iteration, dot vote to decide which to tackle in the next iteration.

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


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.