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: 5540ad5aaeb27b3b5e736bc1f258f6028688fcce41713190501157bc73e33ca4

# Scrum Master Retrospective

Team members contrast expectations for the Scrum Master against expectations for the delivery team across four core Scrum events. Together they cluster notes, vote on priorities, and record concrete commitments.

**Time:** 45 minutes. UWT suggested operational duration; evidence source supplies mechanics without total run time.
**People:** 4 to 12. Individual silent generation followed by full-group clustering, dot voting, and action planning.

## Choose this exercise

**Purpose:** Document and align expectations between the Scrum Master and team members across key Scrum events.
**Use it when:** Use when a team wants to reset working agreements, clarify boundaries, or evaluate role ownership during regular Scrum events.
**Skip it when:** Skip if the team does not use Scrum ceremonies or if active interpersonal conflict requires mediated dispute resolution rather than role alignment.

## Materials and tools

- 1 shared wall, whiteboard, or virtual canvas divided into 4 columns: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
- Blue sticky notes (or digital equivalent) for SM expectations, at least 1 pad per 4 people
- Yellow sticky notes (or digital equivalent) for team expectations, at least 1 pad per 4 people
- Fine-tip markers, 1 per person
- Round voting dot stickers, 4 per person

## Before participants arrive

1. Draw four columns on the board labeled: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
2. Write the prompt key in clear sight: Blue = 'I expect from the Scrum Master', Yellow = 'I expect from the team'.
3. Provide blue sticky notes, yellow sticky notes, and markers at every seat.

## Say this to open

Welcome. Today we will align how our Scrum Master and our team support each other across our four regular events. For each event, write what you expect the Scrum Master to handle on blue notes, and what you expect the team itself to own on yellow notes. Keep observations specific and actionable.

## How to run it

### 1. Introduce columns and review prior actions (5 minutes)

The facilitator states the four events and color key. If the team held a previous role check-in, review prior action items for 3 minutes to confirm what changed. Anyone may pass on speaking during this check.

### 2. Write notes silently (10 minutes)

Participants write sticky notes individually without speaking. Use blue notes for expectations of the Scrum Master. Use yellow notes for expectations of the team. Participants post notes directly into the corresponding event columns as they finish.

### 3. Cluster and clarify (10 minutes)

The facilitator reads each note aloud briefly. The group groups identical or overlapping notes together. Clarifications are allowed, but evaluate or debate only after all notes are clustered.

### 4. Vote and discuss top themes (12 minutes)

Give each participant 4 voting dots to place on the items most critical to address, maximum 1 dot per event column. Discuss the top 1 or 2 vote-getters per event. Formulate clear agreements on who does what.

### 5. Record actions and rate the session (8 minutes)

Record 1 or 2 specific, agreed action items with named owners. Close with a quick rating: each person holds up 1 to 5 fingers to rate session openness and practical value. The facilitator records the average and closes.


## Debrief questions

- Where did our expectations for the Scrum Master differ most from our expectations for ourselves?
- Which Scrum event has the clearest split of responsibilities right now, and which is most blurred?
- What is one concrete change we agreed to test in our next sprint?

**Finished output:** A shared board displaying clustered expectations across four Scrum events, plus 1 to 2 documented action items with designated owners.

## Remote

Set up a digital board with four columns. Provide blue cards for Scrum Master expectations and yellow cards for team expectations. Participants mute and post cards simultaneously during silent writing. Use built-in digital voting tools for dot distribution. Debrief using raised virtual hands or typed comments in chat.

## Hybrid

In-person members use physical sticky notes while a designated scribe mirrors them onto the shared digital board, or all participants use personal laptops to write directly on the digital board. Display the digital board on a main room screen so in-person and remote participants view the exact same clustered items. Voice turns alternate between remote and room participants.

## Access and participation choices

- Participants may submit notes anonymously via digital boards or folded paper handed to the facilitator.
- Any participant may choose to vote without sharing verbal commentary or decline the closing finger-rating poll.

## If the session gets stuck

**All sticky notes focus on Scrum Master tasks with zero team accountability notes.**

Pause before clustering. Ask everyone to write at least one yellow note describing what the team must supply so the Scrum Master can succeed in that event.

**Feedback becomes personal criticism rather than role expectations.**

Refocus the prompt on the ceremony itself. Reframe comments by asking what behavior or artifact is needed in that specific meeting.


## Terms used here

- Scrum Master (SM): The team role responsible for guiding Scrum adoption, facilitating events, and removing impediments.
- Daily Scrum: A 15-minute daily inspect-and-adapt meeting for developers to synchronize work toward the Sprint Goal.

## Sources and adaptation

Observed in EasyRetro template library as Scrum Master Retrospective Template.

Retained the four-event column structure, blue/yellow color coding, clustering, dot voting, action review, and closing rating from the EasyRetro template. UWT structured the sequence into timed facilitator steps, set a 45-minute baseline, added neutral prompts, and established remote/hybrid procedures.

[EasyRetro](https://easyretro.io/templates/scrum-master-retrospective/)

Current run sheet: https://unitedwetransform.com/exercises/scrum-master-retrospective/