Retromat: Inspect & Adapt Ceremony Example: 52-65-41-38-109

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

Constellation - Opening (#52)

Let the participants affirm or reject statements by moving around
Source: Lyssa Adkins via Luis Goncalves

Place a circle or sphere in the middle of a free space. Let the team gather around it. Explain that the circle is the center of approval: If they agree to a statement they should move towards it, if they don't, they should move as far outwards as their degree of disagreement. Now read out statements, e.g.

I feel I can talk openly in this retrospective
I am satisfied with the last iteration
I am happy with the quality of our code
I think our continuous integration process is mature

Watch the constellations unfold. Ask questions about people's observations, such as which constellations were surprising.
This can also be a closing activity (#53).

►

◄

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

Park Bench (#41)

Group discussion with varying subsets of participants
Source: Diana Larsen

Place at least 4 and at most 6 chairs in a row so that they face the group. Explain the rules:

Take a bench seat when you want to contribute to the discussion
One seat must always be empty
When the last seat is taken, someone else must leave and return to the audience

Get everything going by sitting on the 'bench' and wondering aloud about something you learned in the previous phase until someone joins. End the activity when discussion dies down.
This is a variant of 'Fish Bowl'. It's suited for groups of 10-25 people.

►

◄

Decide what to do

Dot Voting - Keep, Drop, Add (#38)

Brainstorm what behaviors to keep, drop & add and pick the top initiatives
Source: Agile Retrospectives

Divide a flip chart into boxes headed with 'Keep', 'Drop' and 'Add'. 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

Know your neighbour - Closing (#109)

How does your left neighbour feel about the retrospective
Source: Inspired by Fabián Lewkowicz

Ask each team member to guess if their left neighbour thinks this retrospective was a good use of their time and why. Their neighbour confirms or corrects their guess.

If you have set the stage with activity #108, make sure to go around the other direction this time.

►

◄

(#)

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.