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

Take a Stand - Opening (#43)

Participants take a stand, indicating their satisfaction with the iteration
Source: Corinna Baldauf, inspired by Christoph Pater
Create a big scale (i.e. a long line) on the floor with masking tape. Mark one end as 'Great' and the other as 'Bad'. Let participants stand on the scale according to their satisfaction with the last iteration. Ask people what they notice.
Psychologically, taking a stand physically is different from just saying something. It's more 'real'.
You can reuse the scale if you close with activity #44.

Find your Focus Principle (#123)

Discuss the 12 agile principles and pick one to work on
Source: Tobias Baier
Print the principles of the Agile Manifesto onto cards, one principle per card. If the group is large, split it and provide each smaller group with their own set of the principles.

Explain that you want to order the principles according to the following question: 'How much do we need to improve regarding this principle?'. In the end the principle that is the team's weakest spot should be on top of the list.

Start with a random principle, discuss what it means and how much need for improvement you see, then place it in the middle. Pick the next principle, discuss what it means and sort it relatively to the other principles. You can propose a position depending on the previous discussion and move from there by comparison. Repeat this until all cards are sorted.

Now consider the card on top: This is presumeably the most needed and most urgent principle you should work on. How does the team feel about it? Does everyone still agree? What are the reasons there is the biggest demand for change here? Should you compare to the second or third most important issue again? If someone would now rather choose the second position, why?

Speed Dating (#26)

Each team member explores one topic in depth in a series of 1:1 talks
Source: Thorsten Kalnin
Each participant writes down one topic they want to explore, i.e. something they'd like to change. Then form pairs and spread across the room. Each pair discusses both topics and ponders possible actions - 5 minutes per participant (topic) - one after the other. After 10 minutes the pairs break up to form new pairs. Continue until everyone has talked to everyone else.
If the group has an odd number of members, the facilitator is part of a pair but the partner gets all 10 minutes for their topic.

(The way to make all the pairings come out even is the following: Form two rows facing each other. This is pairing one. Pick one person. This person's position is fixed the entire time. Everybody else rotates one spot after each pairing.)

Impediments Cup (#88)

Impediments compete against each other in a World Cup style
Source: Pascal Martin, inspired by Boris Gloger's 'Bubble Up'
Prepare a flip chart with a playing schedule for quarter-final, semi-final and final. All participants write down actions on a post-it until you have eight actions. Shuffle them and randomly place them on the playing schedule.
The team now has to vote for one of the two actions in each pair. Move the winning action to the next round until you have a winner of the impediments cup.

If you want to take on more than one or two actions you can play the match for third place.

Endless Blessings (#101)

Bless the upcoming iteration with all your good wishes
Source: Bernie DeKoven via Diana Larsen
Stand in a circle. Explain that you will collect good wishes for the next iteration, building on each other's blessings. If you do it for the first time, start the activity by giving the first blessing. Then go around the circle to add to your blessing. Skip over people who can't think of anything. When you are losing steam, ask for another blessing and start another round. Continue until no one can think of blessings anymore.

Example:
You start with 'May we finish all stories next iteration'. Your neighbor continues with 'And may they delight our customers'. Their neighbor wishes 'And may we be able to automatically test all new features'. And so on until ideas for additions to this blessing run out.
Then someone else can start a new round, e.g. with 'May we write beautiful code next iteration'.

(#)


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.