Retromat: Analysis Discussion Structure: 84-135-118-39-14

◄

Last Retro's Actions Table (#84)

Assess how to continue with last retro's actions
Source: Sven Winkler

Create a table with 5 columns. The first column lists last retro's action items. The other columns are headed 'More of', 'Keep doing', 'Less of' and 'Stop doing'. Participants place 1 sticky note per row into the column that states how they want to proceed with that action. Afterwards facilitate a short discussion for each action, e.g. asking:

Why should we stop doing this?
Why is it worth to go further?
Are our expectations satisfied?
Why do opinions vary that much?

►

◄

Gather data

Avoid Waste (#135)

Tackle the 7 Wastes of Software Development
Source: Tony O'Halloran

This activity facilitates a broad discussion around waste, using the 7 Wastes of Software Development from Lean Software Development by Mary and Tom Poppendieck.

Prepare the room with 7 flip-chart sheets, each representing a category of waste. Be sure to give enough room for small groups to stand around them, so spread the sheets out across the room!

The 7 categories of waste are:

Partially Done Work
Is work going from beginning to end in a single rapid flow? For example; are you building up large amounts of untested or undeployed work? Do you have long-lived feature branches?
Extra Features
Do your customers or users actually need what you’re building?
Relearning
Do you spend a lot of time rediscovering what you (or someone else on your team) already knew at one time?
Handoffs
Is your team truly collaborating, or handing off bits of work to each other, losing tacit knowledge in the process?
Delays
Does work typically spend lots of time stalled awaiting things like environments, someone to be available, or decisions to be made?
Task Switching
Do you find that you lose time to context switching frequently?
Defects
Does your team have a low defect rate? How late in the development process do you find defects? Could this feedback loop be shorter?

To start, briefly describe each of the different types of waste (more in-depth information here). Then pose the core questions:

In which situations do we incur this type of waste?
Where do we do a good job of avoiding this type of waste?

Break into groups of 2-3 people, preferably with a mix of roles in the groups. This helps to build awareness of the waste everyone else is dealing with on your team. Then, each group selects their first topic and spends a short amount of time writing post-its to answer the two questions above. Limit it to 2 or 3 minutes per topic and 2 post-its per person for each topic to avoid getting swamped with data. When the timebox is up, each group cycles to the next category until everyone has had an opportunity to contribute to each.

What themes are emerging? What do participants notice? Use dot-voting to decide which topics are important enough to further discuss in the next phase.

►

◄

Generate insights

Snow Mountain (#118)

Address problematic burndowns and scope creep
Source: Olivier Fortier

This activity is helpful when a team is constantly dealing with additional requests and scope creep. Use the burndown chart of problematic sprints to draw snowy mountains with the same outline. Add a few trees here and there. Print drawings of kids in various sledging situations such as kid sledging down fast, kid sledging and being scared, kid with a sledge looking bored, etc. (You can use Google image search with 'kid sledging drawing').

In teams of 2 or 3, ask the team members to identify which kid's reaction goes with which part of the mountain.
Example: If the mountain is flat, the kid might be bored. If you're facing a wall, the kid might be scared.

You can then discuss the team's reaction facing their own burndowns.

►

◄

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

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf

Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

►

Last Retro's Actions Table (#84)

Avoid Waste (#135)

Snow Mountain (#118)

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

Feedback Door - Numbers (ROTI) (#14)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike