How to Run a Sprint Retrospective: A Practical Guide for Scrum Teams

The sprint retrospective is where good teams become great teams. It's the one ceremony dedicated entirely to improvement—yet many teams treat it as an afterthought or skip it entirely when deadlines loom.

That's a mistake. Research from the State of Agile Report consistently shows that teams practicing regular retrospectives report higher satisfaction and better delivery outcomes.

In this guide, you'll learn how to run sprint retrospectives that actually lead to meaningful change—not just another meeting where people vent and nothing happens.

What is a Sprint Retrospective?

A sprint retrospective is a recurring meeting where the Scrum team reflects on their process and identifies improvements for the next sprint. According to the Scrum Guide, it's one of the five Scrum events and should happen at the end of every sprint.

The retrospective focuses on three key questions:

1. What went well? — Celebrate successes and identify what to keep doing
2. What didn't go well? — Surface problems without blame
3. What will we improve? — Commit to specific actions

Unlike sprint reviews (which focus on the product), retrospectives focus on the process—how the team works together.

Who Attends the Retrospective?

The retrospective is for the Scrum Team:

• Developers (everyone who builds the product)
• Scrum Master (facilitates the session)
• Product Owner (optional but recommended)

Stakeholders and management should not attend. Their presence changes the dynamic and makes team members less likely to speak openly about problems.

If you're a manager who wants insight into team health, ask the Scrum Master for a summary—don't insert yourself into the retro.

How Long Should a Retrospective Last?

The Scrum Guide suggests:

• 1 hour for a 2-week sprint
• 2 hours for a 4-week sprint

In practice, most teams find 45-60 minutes works well for a 2-week sprint. Shorter than that, and you won't have time for meaningful discussion. Longer, and energy fades.

Pro tip: Schedule retrospectives at the end of the sprint but before sprint planning. This gives the team time to decompress and ensures improvements can be incorporated into the next sprint.

The Basic Retrospective Format

The simplest format works for most teams:

1. Set the Stage (5 minutes)

• Welcome everyone
• State the purpose: "We're here to improve how we work"
• Review the previous retro's action items

2. Gather Data (15-20 minutes)

Use a structured format to collect input. The classic approach:

What went well? Team members share wins, successes, and things to continue

What didn't go well? Surface problems, frustrations, and blockers. Focus on process, not individuals.

What should we change? Ideas for improvement

Give everyone time to write their thoughts before sharing. This prevents groupthink and ensures quieter team members contribute.

3. Generate Insights (15 minutes)

• Group similar items together
• Vote on the most important topics to discuss
• Dig into root causes: "Why did this happen? What's the underlying issue?"

4. Decide What to Do (10 minutes)

• Pick 1-3 action items (not more!)
• Assign an owner to each action
• Make actions specific and achievable within one sprint

5. Close the Retro (5 minutes)

• Summarize the action items
• Thank everyone for participating
• Optionally: quick round of appreciation

Five Retrospective Formats to Try

Variety keeps retrospectives fresh. Here are proven formats:

1. Start, Stop, Continue

Simple and effective:

• Start: What should we begin doing?
• Stop: What should we stop doing?
• Continue: What's working that we should keep?

Best for: Teams new to retrospectives

2. Mad, Sad, Glad

Emotion-focused format:

• Mad: What frustrated you?
• Sad: What disappointed you?
• Glad: What made you happy?

Best for: Teams that struggle to express feelings about work

3. 4Ls (Liked, Learned, Lacked, Longed For)

Comprehensive reflection:

• Liked: What did you enjoy?
• Learned: What did you discover?
• Lacked: What was missing?
• Longed For: What do you wish you had?

Best for: Teams focused on growth and learning

4. Sailboat

Visual metaphor:

• Wind (pushing forward): What helped us move faster?
• Anchors (holding back): What slowed us down?
• Rocks (risks ahead): What dangers do we see coming?
• Island (goal): What are we working toward?

Best for: Teams that respond well to visual thinking

5. One Word

Ultra-fast check-in:

• Each person shares one word describing the sprint
• Discuss the patterns that emerge

Best for: Time-constrained retros or as an opening activity

Common Retrospective Problems (and How to Fix Them)

Problem: The Same Issues Come Up Every Sprint

Symptoms: "Didn't we talk about this last time?"

Root cause: Action items aren't being completed or aren't addressing the real problem.

Fix:

• Review previous action items at the start of every retro
• Make actions smaller and more specific
• Assign clear owners with deadlines
• If an issue persists 3+ sprints, escalate it

Problem: One Person Dominates the Discussion

Symptoms: The same voices speak while others stay silent.

Fix:

• Use written brainstorming before discussion
• Go around the room and give everyone a turn
• Try anonymous voting on topics
• Privately coach dominant individuals

Problem: It Feels Like a Blame Session

Symptoms: Finger-pointing, defensiveness, people shutting down.

Fix:

• Establish ground rules: "We're examining the process, not individuals"
• Use "we" language instead of "you"
• Focus on systems and processes, not people
• The Scrum Master should redirect personal attacks

Problem: Nothing Ever Changes

Symptoms: Great discussions, zero follow-through.

Fix:

• Limit to 1-3 action items maximum
• Make each action SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
• Track actions visibly (board, doc, or tool)
• Start next retro by reviewing previous actions

Problem: People Don't Want to Attend

Symptoms: Eye rolls, "do we have to?", low energy.

Fix:

• Vary the format to keep it fresh
• Show that actions actually lead to change
• Keep it time-boxed and respect the schedule
• Make it safe—if people fear consequences, they won't engage

Retrospectives for Remote Teams

Running retrospectives remotely requires extra attention to engagement:

Use a Digital Whiteboard

Tools like Miro, FigJam, or dedicated retro tools let everyone contribute simultaneously. This is more engaging than taking turns on a video call.

Keep Cameras On

Non-verbal cues matter. Seeing faces helps the facilitator read the room and adjust.

Use Anonymous Input

Remote settings can feel less safe. Let people submit items anonymously, especially for sensitive topics.

Be More Deliberate About Turn-Taking

In person, people naturally find moments to speak. Remotely, the facilitator needs to actively invite input: "Sarah, what's your take on this?"

Consider Async + Sync Hybrid

For globally distributed teams:

1. Async (24 hours before): Everyone adds items to a shared board
2. Sync (30-45 min): Discuss, vote, and decide on actions

Action Items That Actually Work

The difference between retros that improve things and retros that don't? The quality of action items.

Bad action item: "Communicate better"

Good action item: "Add a 5-minute sync at 10am daily to surface blockers. Owner: Jamie. Review next retro."

Bad action item: "Fix the flaky tests"

Good action item: "Spend 2 hours this sprint identifying the 3 most flaky tests. Create tickets for each. Owner: Alex."

Every action item should answer:

• What specifically will change?
• Who is responsible?
• When will it be done or reviewed?

Getting Started

Your next sprint retrospective can be better than your last. Here's a quick checklist:

• [ ] Schedule 45-60 minutes at sprint end
• [ ] Choose a format (Start/Stop/Continue is a safe default)
• [ ] Prepare a space (physical or digital whiteboard)
• [ ] Review previous action items
• [ ] Facilitate discussion, then converge on 1-3 actions
• [ ] Assign owners and follow up next sprint

The best teams aren't the ones that never have problems—they're the ones that surface problems quickly and fix them systematically. That's what retrospectives enable.

---

Running estimation before your retrospective? Try ScrumDeck for fast, focused planning poker sessions.