Retromat: Scrum Retrospective Ideas: 31-146-10-99-16

◄

Check In - Draw the Iteration (#31)

Participants draw some aspect of the iteration
Source: Corinna Baldauf, adapted from Thorsten Kalnin, Olivier Gourment; Thomas Guest

Distribute index cards and markers. Set a topic, e.g. one of the following:

How did you feel during the iteration?
What was the most remarkable moment?
What was the biggest problem?
What did you long for?
If the last iteration had been a circus performance, what part did you play? Juggler, funambulist, clown, knife-thrower, ...

Ask the team members to draw their answer. Post all drawings on a whiteboard. For each drawing let people guess what it means, before the artist explains it.
Metaphors open new viewpoints and create a shared understanding.

►

◄

Gather data

Roles and Responsibilities (#146)

Clarify expectations and responsibilities for each role on the team
Source: Role-Up

Many conflicts arise from unclear expectations. Talking about individual people can feel like an attack. That’s why this activity focusses on expectations towards roles.

Create a table with one column per role in the team. (Limit it to 7 columns. If there are more than 7 roles, leave out roles that have little conflict.) The rows of the table are:  

Role name
This role is responsible for …
This role is NOT responsible for …

Leave enough space between the bottom rows so that people who aren’t sure whether something is a role’s responsibility have an unofficial inbetween space to post them. Hand out pens, as well as yellow and orange sticky notes.

Ask everyone to write yellow sticky notes listing the responsibilities for each role – 1 responsibility per note. Set a timer for 8 minutes and read the room to see if you can stop early or have to give more time. Post all the sticky notes but don’t discuss them yet.

Repeat this process with the non-responsibilities on orange sticky notes.

The team now dot-vote on which topics they want to talk about. Give enough time to read all the sticky notes and distribute 7 votes.

Start with the topic with the most votes. Invite the people who voted for it to share why they want to talk about it. Try to clarify expectations team members have about a role’s responsibilities. Write down clarifications or agreements the team make. Repeat for the next highest voted topic until time runs out.

►

◄

Generate insights

Brainstorming / Filtering (#10)

Generate lots of ideas and filter them against your criteria
Source: Agile Retrospectives

Lay out the rules of brainstorming, and the goal: To generate lots of new ideas which will be filtered after the brainstorming.

Let people write down their ideas for 5-10 minutes
Go around the table repeatedly always asking one idea each, until all ideas are on the flip chart
Now ask for filters (e.g. cost, time investment, uniqueness of concept, brand appropriateness, ...). Let the group choose 4.
Apply each filter and mark ideas that pass all 4.
Which ideas will the group carry forward? Does someone feel strongly about one of the ideas? Otherwise use majority vote.

The selected ideas enter Phase 4.

►

◄

Decide what to do

Planning Poker Voting (#99)

Use your Planning Poker cards for un-influenced voting
Source: Andreas Ratsch

If you've got very influential and / or shy team members you can re-use Planning Poker cards to vote simultaneously:

Write all suggested actions on sticky notes and put them onto a wall. Hand out an ordered deck of Planning Poker cards to each participant. Count the proposals and remove that many cards from the back of the card decks. If you've got 5 suggestions you might have cards '1', '2', '3', '5', and '8'. This depends on your deck (some have a '1/2' card). It doesn't matter, as long as all participants have the same set of values.

Explain the rules: Choose a card for each suggestion. Choose a low value if the action is not worth doing in your opinion. Choose a high value if the action is worth starting next iteration.

Give them a minute to sort out their internal ranking and then present the first suggested action. Everybody chooses a card and they reveal them at the same time. Add the numbers from all cards and write the sum onto the action. Remove the used poker cards. Repeat this for all actions. If you have more actions than poker values the players can show 'no card' (counting 0) for the appropriate number of times.

Implement the action with the highest sum in the next iteration. Add more actions only if there's team consensus to do so.

►

◄

Close the retrospective

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives

Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.

►

Check In - Draw the Iteration (#31)

Roles and Responsibilities (#146)

Brainstorming / Filtering (#10)

Planning Poker Voting (#99)

Helped, Hindered, Hypothesis (#16)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike