Standard Sprint Retrospective

Choose this exercise

Purpose: Document working patterns and system friction from a completed work cycle to select concrete operational changes for the next cycle.

Use it when: Use at the boundary between two work sprints or project iterations when a team needs to adjust its workflow.

Skip it when: Skip during an active production outage or emergency incident response where remediation takes precedence over routine process review.

Group arrangement: Whole group working in parallel silent posting, followed by facilitator-led whole-group sorting and action planning.

Timing: UWT operational timing structured around the core 5-step sprint retrospective process in the source guide.

Materials and tools

• 1 whiteboard or clear wall section marked with three columns: Good, Bad, Action Plan
• 1 pad of 3x3 inch sticky notes per person
• 1 fine-point marker per person
• Timer

Before participants arrive

1. Draw three vertical columns on the board labeled: 'The Good (What worked & why)', 'The Bad (What failed & why)', and 'Action Plan'.
2. Place sticky pads and pens at every seat.
3. Display the sprint goal and dates on the header of the board.

Say this to open

We have 45 minutes to review our completed sprint. Our goal is to examine how we worked, understand why certain things helped or stalled us, and choose practical adjustments for the next cycle. We will post observations anonymously or signed, cluster shared themes, and leave with assigned next steps.

How to run it

1. Set stage and context 5 minutes

   Facilitator delivers the opening script, reminds the room that discussions critique systems and processes rather than individuals, and confirms the specific sprint increment under review.

2. Silent generation on successes 7 minutes

   Participants work silently, writing one observation per sticky note about what went well and why it succeeded. Individuals walk up and place their notes in 'The Good' column as they finish.

3. Silent generation on obstacles 8 minutes

   Participants write what failed, caused friction, or fell behind schedule, adding the underlying cause where possible. Remind people to avoid interpersonal complaints. Notes are posted to 'The Bad' column.

4. Group and analyze themes 10 minutes

   Facilitator reads aloud items from both columns without identifying authors. The room clusters duplicates. For key friction points, ask the room 'why did this happen?' to pinpoint process root causes.

5. Draft concrete action plan 12 minutes

   The group proposes 1 to 3 specific process changes to address top clusters. Each chosen item must have a designated owner and criteria for completion during the next sprint. Facilitator logs them in 'Action Plan'.

6. Checkout and close 3 minutes

   Review the finalized action items. Offer a rapid optional go-around where anyone can state one brief final process observation or pass.

Debrief questions

• Which systemic bottleneck caused the most disruption during this sprint?
• How will we measure whether our agreed action items solved the problem in the next sprint?
• What positive practice did we uncover that we should protect and repeat?

Finished output: A board with clustered sprint observations and 1 to 3 owned, tracked action commitments for the next sprint.

Remote

Set up a digital canvas with the three columns. Participants post virtual sticky notes silently. The facilitator screen-shares the board during clustering and logs action owners directly into the digital workspace.

Hybrid

All participants, in-person and remote, submit sticky notes via a shared digital canvas. In-person members use personal laptops or designate an in-room scribe to mirror physical cards to the digital view. Spoken discussion alternates evenly between in-room and online callers.

Access and participation choices

• Participants may submit notes typed, handwritten, or dictating to a partner.
• Anyone may choose to pass during spoken debriefs and closing comments without justification.
• Writing names on sticky notes is optional.

If the session gets stuck

The Bad column turns into interpersonal complaints or finger-pointing.

Intervene immediately. Reframe the note toward the workflow or environment: ask 'what tool, communication channel, or process gap allowed that error to occur?'

Participants generate a massive list of ten or more action items that cannot all be delivered.

Cap commitments at a maximum of three items. Use a rapid hand vote to choose the three that will have the biggest operational impact.

Terms used here

• Sprint: A fixed timebox, usually between one and four weeks, during which a team completes a set increment of work.
• Increment: A usable, inspectable unit of finished work produced during a sprint.