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.
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.)
What could sub-groups improve when interacting with others? Source:
Identify sub-groups within the participants that interacted during the iteration, e.g. developers/testers, clients/providers, PO/developers, etc. Give participants 3 minutes to silently write down what they think their group did that negatively impacted another group. One person should be part of one group only and write stickies for all groups they don't belong to - 1 sticky per issue.
Then in turn all participants read their stickies and give them to the corresponding group. The affected group rates it from 0 ('It was not a problem') to 5 ('It was a big problem'). Thus you get insights and shared understanding about problems and can select some of them to work on.
Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'. Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.
A good debriefing deepens understanding, learning and sharing. Preparation: Download and assemble the Debriefing Cube and cards.
During the retrospective, roll the cube. Then draw a card from the category it shows and use it to prompt a discussion. Repeat as time permits.
This will broaden your debriefing options and is especially great for groups without a facilitator to enable them to effectively debrief on their own.