Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.

Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step.

Reference revision: 757099564112004d6266f8cc55b0df5a5250efcb6f1b8d2cb1cd0d712584dc35

# Standard Sprint Retrospective

Team members write individual reflections on what worked well and what needs improvement from their recent sprint, group their observations, and commit to concrete action items.

**Time:** 45 minutes. EasyRetro standard allocation for a one-week sprint (45 minutes).
**People:** 3 to 12. Individual silent writing followed by full-team clustering and prioritization.

## Choose this exercise

**Purpose:** Produce documented process improvements and clear ownership for the upcoming sprint cycle.
**Use it when:** At the conclusion of a fixed work cycle or sprint, before planning the next cycle.
**Skip it when:** During an active incident or when the team has no control over its own working agreements and processes.

## Materials and tools

- Sticky notes (two distinct colors per person, at least 10 notes total per person)
- Markers or pens (one per person)
- Whiteboard, flip chart, or clear wall space divided into two columns: What Went Well and What Needs Improvement
- Timer or clock visible to the room

## Before participants arrive

1. Draw two vertical columns on the whiteboard labeled 'What Went Well' and 'What Needs Improvement'.
2. Distribute sticky notes and markers to every workstation.

## Say this to open

Today we are running our retrospective for the sprint we just finished. Our goal is to review how we worked together, celebrate what succeeded, and pick concrete adjustments for our next sprint. We will spend 45 minutes moving through reflection, grouping themes, and assigning actions.

## How to run it

### 1. Set the goal and frame (5 minutes)

State the scope of the retrospective, identifying the exact sprint dates and major goals under review. Outline the 45-minute agenda so participants know the time limits.

### 2. Silent individual reflection (10 minutes)

Ask everyone to write observations on sticky notes in silence. Use one color for successes (what went well) and another color for frictions or roadblocks (what needs improvement). Limit one distinct point per note. Aim for 3 to 5 notes per person.

### 3. Post and group insights (15 minutes)

Invite participants up to post their notes in the matching column. Have people read their notes aloud briefly as they place them. As notes appear, invite the room to group related topics into thematic clusters without debating solutions yet.

### 4. Establish action items (10 minutes)

Pick the top two or three clusters that have the highest operational impact. Ask the group for specific changes to try during the next sprint. Formulate each into a concrete action item with an assigned owner and a completion check date.

### 5. Review and close (5 minutes)

Read aloud the agreed action items and their owners. Confirm that no urgent operational blocker was left unaddressed, then officially close the sprint.


## Debrief questions

- Which agreed action item will make the most immediate difference in our next sprint?
- What working practice helped our collaboration the most over the past cycle?
- Did our meeting time limits feel sufficient to cover the main issues?

**Finished output:** A list of agreed action items with designated owners documented on the sprint backlog or team board.

## Remote

Use a digital whiteboard with two pre-built columns labeled 'What Went Well' and 'What Needs Improvement'. Give 10 minutes for silent typing onto digital cards. Facilitate clustering by screen sharing and asking participants to speak sequentially or use hand-raise cues before capturing final action items in the team task tracker.

## Hybrid

Have in-person participants and remote participants add sticky notes simultaneously to the same shared online digital board. Display the digital board on the physical room screen and require all verbal contributions to be miked so remote members hear clearly.

## Access and participation choices

- Participants may submit reflections anonymously or hand sticky notes to the facilitator to read.
- Participants can pass on speaking during the open discussion and contribute only in writing.

## If the session gets stuck

**Discussion derails into venting about issues outside the team's control.**

Intervene and guide the team back to what is directly within their sphere of influence for the upcoming sprint.

**Too many action items are suggested, risking zero follow-through.**

Cap the action plan at two or three realistic items and hold the rest in a parking lot.


## Terms used here

- Sprint: A fixed period of time (typically one to four weeks) during which a team completes a specific set of work.
- Retrospective: A meeting held at the end of a sprint to reflect on performance, process, and tools, and plan improvements.

## Sources and adaptation

Observed in EasyRetro guidance documentation on sprint retrospective structure and duration guidelines.

Retained the 6-step sprint retrospective process (Set Goal, Involve Team, Gather Info, Identify Insights, Establish Plan, Close) and standard one-week sprint duration (45 minutes) from the EasyRetro text. Added explicit timing per step, operational facilitator scripts, materials lists, and hybrid guidelines.

[EasyRetro](https://easyretro.io/sprint-retrospective/how-long-is-a-sprint-retrospective/)

Current run sheet: https://unitedwetransform.com/exercises/how-long-is-a-sprint-retrospective/