How to Run a Sprint Retrospective by Setting the Stage Effectively
This skill teaches you how to open a sprint retrospective by creating psychological safety, establishing working agreements, and defining the session's focus so the rest of the meeting is productive and inclusive.
To set the stage for a sprint retrospective, welcome participants, state the session's timebox and goal, and establish working agreements such as the Vegas Rule or no-blame language. Use a brief check-in activity—like a one-word mood check—to gauge energy levels, build psychological safety, and ensure every voice is heard before diving into data gathering.
Outcome: Your retrospectives start with full engagement, clear expectations, and a psychologically safe environment—leading to more honest discussion and better outcomes in every subsequent phase of the Five-Step Retrospective Framework.
Prerequisites
- Basic understanding of Scrum or iterative development cycles
- Familiarity with the purpose of a retrospective
- Access to a meeting space (physical or virtual) with a whiteboard or collaborative tool
Overview
Setting the stage is the critical first phase of the Five-Step Retrospective Framework. It happens in the first five to fifteen minutes of the session, yet it disproportionately influences everything that follows. When done well, participants feel safe to speak candidly, understand what the session will cover, and commit to shared norms. When skipped or rushed, teams default to surface-level feedback and dominant voices take over.
If you want to learn how to run a sprint retrospective that actually produces change, start here. The opening minutes determine whether the conversation will be honest or performative. Setting the stage isn't just an icebreaker—it's a deliberate act of facilitation design that establishes the container for productive reflection.
This skill covers three interconnected elements: creating a welcoming environment, defining the retrospective's focus and timebox, and agreeing on ground rules. Mastering this opening phase makes every downstream step—gathering data, generating insights, and deciding on actions—significantly more effective.
How It Works
Setting the stage works by lowering the psychological barriers to honest participation before any substantive discussion begins. Human beings are wired to assess social safety before sharing vulnerable information. When a facilitator explicitly signals that the environment is non-judgmental and that every perspective matters, participants shift from self-protective mode to collaborative mode.
The mechanism has three layers. First, a check-in activity gives every person a low-stakes reason to speak early. Research on group dynamics shows that people who speak within the first few minutes of a meeting are significantly more likely to contribute throughout. Second, framing the session's focus reduces cognitive load—participants stop wondering "what are we even doing here?" and instead channel energy toward the specific topic at hand. Third, working agreements create shared accountability. When the team collectively agrees to norms like "assume positive intent" or "one conversation at a time," enforcement becomes a group responsibility rather than a facilitator burden.
This phase also sets the emotional tone. A facilitator who opens with curiosity and warmth gets a fundamentally different retrospective than one who opens by reading the sprint velocity chart. The stage-setting phase primes the team's emotional register for the rest of the session.
Step-by-Step
Step 1: Prepare the space before anyone arrives
Whether your retrospective is in-person or remote, the physical or virtual environment sends signals before you say a word. Arrange chairs in a circle rather than classroom-style. For remote sessions, open your collaborative board (Miro, FigJam, or a shared doc) with a warm welcome message and clear visual structure. Have the agenda visible. Remove distractions—close unnecessary tabs, silence notifications, and ask participants to do the same.
Prepare any materials you'll need for your check-in activity: sticky notes, markers, a pre-built template, or a shared poll. Having everything ready communicates respect for the team's time and signals that this session is intentional, not improvised.
Tip: For remote teams, open the video call 2-3 minutes early and greet people individually as they join. This casual warmup mimics the hallway chatter that naturally sets the stage in co-located settings.
Step 2: Welcome participants and state the purpose
Open by thanking people for being there—this is genuine, not perfunctory. Then state the retrospective's specific focus clearly. A good framing statement sounds like: "Today we're reflecting on Sprint 14, specifically how our new deployment process affected our delivery flow. We have 60 minutes."
Avoid vague openings like "let's talk about what went well and what didn't." The more specific your focus, the more targeted and useful the conversation will be. If you're using a retrospective template, briefly walk through the structure so participants know what to expect.
Tip: If a major incident or team conflict happened during the sprint, acknowledge it directly. Saying "I know the outage on Wednesday was stressful—this is a space to talk about that openly" is far more effective than pretending it didn't happen.
Step 3: Establish or review working agreements
Working agreements are the behavioral norms the team commits to for the duration of the session. For a new team, co-create these from scratch. For an established team, display the existing agreements and ask if anyone wants to add or modify them.
Common working agreements include: the Vegas Rule (what's said here stays here), no blame—focus on systems not individuals, one speaker at a time, assume positive intent, and mobile phones on silent. Write these visibly on a whiteboard or shared document.
The key is that the team owns these agreements rather than having them imposed by the facilitator. Ask: "Are we all willing to commit to these for the next hour?" Getting explicit verbal or visual consent (thumbs up) transforms abstract norms into a social contract.
Tip: Limit working agreements to 4-6 items. Too many rules create a legalistic atmosphere that undermines the psychological safety you're trying to build.
Step 4: Run a check-in activity
The check-in is a brief, low-stakes activity that ensures every participant speaks at least once in the first few minutes. This is not an icebreaker for fun—it's a facilitation technique with a specific purpose: equalizing participation.
Popular check-in formats include:
- One-word check-in: Each person shares one word describing their current mood or energy level.
- ESVP: Participants anonymously indicate if they're an Explorer, Shopper, Vacationer, or Prisoner. This gives you real-time data on engagement levels.
- Confidence thermometer: Everyone rates their confidence that the team can improve on a scale of 1-5.
- Sprint in one sentence: Each person summarizes the sprint in a single sentence.
Whichever format you choose, go around the room (or screen) systematically. Don't let people pass—gentle persistence ("take your time, we'll come back to you") is better than letting silence become avoidance.
Tip: If the ESVP check-in reveals a significant number of Prisoners or Vacationers, pause and address it. Ask the group: "What would make this session more valuable for you?" Ignoring disengagement early guarantees a flat retrospective.
Step 5: Clarify the timebox and transition to data gathering
Before moving to the next phase, confirm the timebox for the full session and give a brief roadmap: "We'll spend about 15 minutes gathering data, 15 minutes looking for patterns, 15 minutes deciding on actions, and 5 minutes closing." This removes uncertainty about pacing and empowers participants to manage their own contributions.
Then make a clean transition: "Now that we're aligned on how we'll work together, let's move into gathering data." A crisp transition signals that the stage-setting phase served its purpose and the real work begins now.
Tip: Write the time allocations visibly so you can point to them later if discussion runs long. It's easier to say "we agreed to 15 minutes for this phase" than to arbitrarily cut people off.
Examples
Example: Setting the stage for a remote team after a difficult sprint
A distributed team of 7 developers just completed a sprint where a critical production bug consumed most of their capacity. Morale is low, and two team members have privately told the Scrum Master they feel the retrospective will just be 'venting.' The retrospective is 60 minutes on Zoom with a Miro board.
The facilitator opens the Miro board 5 minutes early with a welcoming note: 'Thanks for showing up. This sprint was tough, and this session is about learning, not blame.' As people join, she greets each person by name and asks a casual question.
At start time, she frames the session: 'Today we're looking specifically at how the P1 bug affected our sprint, what our incident response revealed about our systems, and what we'd change. We have 60 minutes.'
She displays four working agreements: Vegas Rule, no individual blame, cameras on if comfortable, and one conversation at a time. She asks: 'Anything to add or change?' One developer adds 'let's timebox venting to 10 minutes max.' The team agrees.
For the check-in, she uses a 'battery level' activity: each person drags a slider on Miro from 0% to 100% to show their energy level and adds one word about their mood. Results show the team averaging 35% energy with words like 'drained' and 'frustrated'—but also 'hopeful.'
She acknowledges the data: 'I see a lot of low batteries. That makes sense given the week. Let's use this time to figure out one thing we can change so the next hard sprint feels more manageable.' Then she transitions: 'Let's start by building a timeline of the sprint.'
The explicit acknowledgment of difficulty, combined with the no-blame agreement and energy check, gives the team permission to be honest without spiraling into finger-pointing.
Example: First retrospective with a newly formed team
A new cross-functional team of 5 (2 developers, 1 designer, 1 QA, 1 product owner) has just completed their first two-week sprint together. Team members come from different departments and don't know each other well. The retrospective is in-person in a conference room, 45 minutes.
The facilitator arrives 10 minutes early and arranges chairs in a circle with no table barrier. He places sticky notes, markers, and a whiteboard with the agenda visible.
He opens: 'Welcome to our very first retrospective as a team. The goal today is to reflect on Sprint 1 and start building the habit of continuous improvement together. We have 45 minutes.'
Since this is a new team, he co-creates working agreements from scratch: 'What ground rules would help everyone feel comfortable speaking honestly?' He writes suggestions on the whiteboard as people offer them. The team lands on: speak from your own experience, what's said stays here, and it's okay to disagree respectfully. He asks for a thumbs-up commitment from everyone.
For the check-in, he uses 'Two truths and a wish': each person shares two things that are true about the sprint and one thing they wish had been different. This doubles as a light data-gathering warm-up while ensuring everyone speaks.
The designer, who tends to be quiet in meetings, shares: 'I got my first real sprint experience, the team was patient with my questions, and I wish I'd been included in story refinement earlier.' This single contribution surfaces a real process improvement opportunity that the team might not have heard without the structured check-in.
The facilitator summarizes themes he's hearing and transitions to the data-gathering phase.
Best Practices
Rotate the check-in activity every few retrospectives to prevent staleness—use a resource like choosing retrospective activities for fresh ideas.
Arrive at least 5 minutes early to prepare the space, test technology, and greet early joiners individually—this small investment pays enormous dividends in participant comfort.
Name the retrospective's specific focus out loud rather than defaulting to a generic 'what went well / what didn't' frame; specificity produces actionable insights.
Revisit working agreements every 4-6 sprints or whenever team composition changes; stale agreements lose their power as social contracts.
Watch for non-verbal cues during the check-in—crossed arms, cameras off, or one-word answers from usually talkative people may signal that extra safety-building is needed before proceeding.
Keep the stage-setting phase to no more than 15% of total retrospective time; it should feel warm and efficient, not drawn out.
Common Mistakes
Skipping the check-in to 'save time' and jumping straight into data gathering.
Correction
The check-in takes 3-5 minutes and directly increases participation quality for the remaining 55 minutes. Skipping it is a false economy. People who haven't spoken early in a meeting are statistically less likely to contribute later—especially introverts and junior team members.
Using the same icebreaker every sprint until the team visibly dreads it.
Correction
Rotate check-in activities regularly. Keep a repertoire of 5-6 formats and match the activity to the team's current energy and context. A team coming off a crisis sprint needs a different opener than one celebrating a successful launch.
Stating working agreements but never enforcing them during the session.
Correction
Working agreements only work if you reference them in real time. When someone starts blaming an individual, gently point to the 'focus on systems, not people' agreement. The stage-setting phase creates the social contract; enforcement throughout the session gives it teeth.
Opening with metrics, dashboards, or velocity charts before establishing psychological safety.
Correction
Data has its place—in the gathering data phase. Leading with numbers puts people in defensive mode, especially if the numbers look bad. Set the emotional stage first, then introduce objective data once the team is in a reflective mindset.
Allowing the manager or most senior person to speak first during the check-in.
Correction
Have the facilitator go first (modeling vulnerability), then proceed in a non-hierarchical order—random, alphabetical, or reverse seniority. When the VP speaks first, everyone else calibrates their response to match, killing candor.
Other Skills in This Method
Closing Retrospectives Effectively
How to wrap up a retrospective by summarizing decisions, appreciating contributions, and gathering feedback on the retro process itself.
Deciding What to Do: Prioritizing Retrospective Action Items
Methods for helping the team select, prioritize, and commit to specific, actionable improvements they will implement in the next iteration.
Choosing Retrospective Activities and Exercises
How to select and facilitate engaging activities like Sailboat, Mad/Sad/Glad, or Timeline for each phase of the five-step retrospective.
Building Sprint Retrospective Templates
How to design reusable retrospective templates that map activities to each of the five phases for consistent and efficient facilitation.
Tracking Retrospective Action Items Across Sprints
Practices for following up on retrospective commitments, measuring improvement progress, and ensuring accountability between sprint cycles.
Generating Insights from Retrospective Data
How to facilitate analysis of gathered data to uncover root causes, patterns, and meaningful insights that go beyond surface-level observations.
Gathering Data During Sprint Retrospectives
Techniques for collecting objective facts, events, metrics, and team sentiments from the past iteration to create a shared understanding of what happened.
Related Skills from Other Methods
Frequently Asked Questions
How long should setting the stage take in a sprint retrospective?
Setting the stage should take 5-15 minutes depending on the total retrospective length. For a 60-minute session, aim for about 10 minutes. For a 90-minute session, you can invest up to 15 minutes. The key is to be efficient—every minute here should earn back engagement time later.
What are the best check-in activities for retrospectives?
The best check-in depends on context. For quick energy reads, try a one-word mood check or battery level. For gauging engagement, use ESVP (Explorer/Shopper/Vacationer/Prisoner). For new teams, use 'two truths and a wish' to build familiarity. Rotate activities every few sprints to keep them fresh.
How do I run a sprint retrospective when the team is remote?
For remote retrospectives, prepare your digital collaboration tool before the call, greet people individually as they join, and use visual check-in activities like emoji reactions, slider polls, or virtual sticky notes. Ask for cameras on when comfortable, and use structured turn-taking to ensure quieter participants are heard.
What working agreements should a retrospective have?
Common retrospective working agreements include the Vegas Rule (confidentiality), no individual blame, one speaker at a time, assume positive intent, and phones away. The most effective agreements are co-created by the team rather than imposed by the facilitator, and they should be limited to 4-6 items.
How do I handle disengaged participants at the start of a retrospective?
Use a structured check-in activity that requires every person to contribute—even a single word. If the ESVP check-in reveals widespread disengagement, address it directly by asking what would make the session more valuable. Sometimes acknowledging 'I can see energy is low' is enough to shift the dynamic.
Can I skip setting the stage if my team has been doing retrospectives for months?
No. Even experienced teams benefit from a brief stage-setting phase. You can shorten it to 3-5 minutes, but skipping the check-in and working agreements review leads to gradual erosion of psychological safety and participation quality over time. Consistent rituals maintain trust.