Retromat: Inspect & Adapt Plan Ideas: 136-65-145-39-15

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.org – by Corinna Baldauf

Plan-ID:

New random retrospective plan
Search activities for ID or keyword

Close

Search titles, summaries & descriptions

◄

Set the stage

Surprise! (#136)

How do the toys in Kinder Surprise Eggs represent participants?
Source: Unknown via Andreas Drexhage

Prepare by buying a Kinder Surprise Egg (or something similar with a surprise toy inside) for each participant.

Hand out the eggs at the beginning of the retrospective. Eating the chocolate is optional, but everybody needs to open their egg and assemble the toy. Ask “How does your toy represent your role in this iteration?”

Give everyone a minute to think. Then go around the group for everyone to present their toy and how they relate to it.

►

◄

Gather data

Appreciative Inquiry (#65)

Lift everyone's spirit with positive questions
Source: Doug Bradbury, adapted for SW development by Corinna Baldauf

This is a round-based activity. In each round you ask the team a question, they write down their answers (gives everyone time to think) and then read them out to the others.
Questions proposed for Software Development teams:

When was the last time you were really engaged / animated / productive? What did you do? What had happened? How did it feel?
From an application-/code-perspective: What is the awesomest stuff you've built together? What makes it great?
Of the things you built for this company, which has the most value? Why?
When did you work best with the Product Owner? What was good about it?
When was your collaboration best?
What was your most valuable contribution to the developer community (of this company)? How did you do it?
Leave your modesty at the door: What is the most valuable skill / character trait you contribute to the team? Examples?
What is your team's most important trait? What sets you apart?

('Remember the Future' (#37) works well as the next step.)

►

◄

Generate insights

Braver (#145)

What does courage look like? What would the team do if they were bolder?
Source: Johanna Amlacher

Put up four posters with the following questions:

Which person in the team do you find courageous and how does courage show itself?
When have you felt insecure and wished you were braver?
What helps you to be brave?
What bold idea would you try as a team if you were 10 times bolder?

For each question do a round of:

4 minutes of quiet time to answer the question on sticky notes
Ask people to read out and post their answers. (In a large group you can use 1-2-4-All to discuss answers in smaller groups first.)
Cluster similar answers

(We do it in several rounds to slowly warm up the participants to tackle the last question.)

After the last round, look at all the answers and facilitate a discussion. Ask participants what is standing out for them? What's unexpected? What patterns do they see? What do these patterns mean for them as a team?

Then ask the team to rate themselves on a scale of 1-10: How brave do they think they are? Followed by: What would be possible if they were one step higher on the scale?

Based on everything they’ve talked about, what would they like to try that’s somewhat bold yet safe enough?

►

◄

Decide what to do

Dot Voting - Worked well, Do differently (#39)

Brainstorm what worked well & what to do differently and pick the top initiatives
Source: Agile Retrospectives

Head 2 flip charts with 'Worked well' and 'Do differently next time' respectively. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.

►

◄

Close the retrospective

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 trainings for scrum master certification and product owner certification. He also 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. Connect with him on LinkedIn, BlueSky, Mastodon, FB, Insta, Threads.