How to Run a Retrospective: The Complete Guide (+ Agenda)

Most teams run retrospectives. Far fewer run ones that change what happens next sprint, and the difference is almost always facilitation, not the format you pick. This guide walks through how to run a retrospective end to end: what it is for, the five phases a good session moves through, a ready-made agenda you can copy, how to choose a format, and the anti-patterns that quietly kill the habit.

What a retrospective is

A retrospective is the moment a team stops to ask a deceptively simple question: how are we working, and how could we work better? It is a regular, protected slot, usually at the end of a sprint or a piece of work, where the people who did the work look back together and agree on what to change.

Its job is narrow and concrete: find the one or two things slowing the team down, and agree on a change. That is it. A retro is not a status meeting, not a blame session, and not a place to re-plan the backlog. Get the habit right and the “culture of continuous improvement” everyone talks about takes care of itself, because the team can see its own decisions showing up in how the next sprint runs.

The five phases of a retrospective

The most durable structure comes from Esther Derby and Diana Larsen’s Agile Retrospectives, which frames every good session as five phases:

Set the stage. Open the room, state the goal, and make it safe to speak.
Gather data. Get everyone’s view of what actually happened on the table, facts and feelings both.
Generate insights. Look for patterns and root causes behind the data, not just symptoms.
Decide what to do. Turn the best insight into one or two concrete, owned actions.
Close. Confirm the actions, thank the team, and check how the retro itself went.

The phases matter more than any single template. Whatever format you run, it should move the team through these five steps in order. Skipping “gather data” straight to “decide what to do” is how retros end up solving the loudest person’s pet problem instead of the real one.

The five phases of a retrospective shown as a timed agenda.

A 60-minute retrospective agenda

Sixty minutes is enough for a focused sprint retro. Here is a worked agenda that maps straight onto the five phases:

0:00 to 0:05, Set the stage (5 min). Restate the goal in one line, read the prime directive, and ask a short check-in question to warm the room.
0:05 to 0:20, Gather data (15 min). Everyone adds their own notes silently first, then you make the board visible. Silent writing stops the discussion anchoring on whoever speaks first.
0:20 to 0:35, Generate insights (15 min). Group the related notes, dot-vote on what matters most, and dig into the top one or two. Keep asking “why” until you reach something the team can actually change.
0:35 to 0:50, Decide what to do (15 min). Agree on one or two actions. Each gets a single owner and a date.
0:50 to 1:00, Close (10 min). Read the actions back, thank the team, and take a quick temperature on the session itself.

Adjust the split for your team: a tense sprint may need more time in “gather data”, a smooth one can spend it on “decide what to do”. The point is to keep every phase timeboxed so you always reach agreed actions before the hour is up.

Plan your retrospective: a pre-retro checklist

A good session is mostly won before anyone joins the call. Run through this checklist in the day before your retro. It doubles as a handover if someone else is facilitating.

Review last retro’s actions. Pull up the previous session’s commitments and note which landed. This is the first thing you will cover.
Pick a format. Choose the one that fits this sprint, not your habit (see the next section).
Book the time and the people. Protect a full slot on the calendar and make sure the whole team, and only the team, is invited.
Prep the board and questions. Set up the columns or template in advance and write your check-in question so you are not improvising at the start.
Decide how input is collected. Plan for silent, written input first, anonymous if the topic is sensitive.
Have the prime directive ready. Know how you will open and set the tone for safety.
Plan for actions. Decide where actions will be recorded and who confirms owners and dates before you close.

Choosing a format

The single biggest unlock is silent, written input before any discussion. When everyone adds their notes first, the loudest voice stops setting the agenda and the quieter, more careful observations actually get heard.

The format should match what the team needs this week. A few reliable starting points:

Start Stop Continue is fast and action-oriented. Good for steady teams that just want to tune their process.
Mad Sad Glad surfaces the emotional temperature after a hard or unusual sprint, when how people feel is the story.
Starfish widens the lens to five signals (keep, more, less, start, stop), useful when “start / stop” feels too blunt.
Sailboat frames goals, risks, and headwinds as a single picture, good for a longer look at what is helping and holding the team back.

When in doubt, vary it. A team that runs the same format every sprint stops seeing new things. Browse the full set of retrospective templates to match the format to the moment.

Facilitation tips

The facilitation matters more than the format. Three things carry most of the weight:

Open with the prime directive. Remind everyone that, regardless of what we discover, everyone did the best job they could with what they knew at the time. It is not a platitude. It is the sentence that makes it safe to raise the real problem.

Keep the opening short. Under five minutes. The goal is psychological safety, not a second status meeting. If people feel safe, the honest material surfaces on its own.

Draw out the quiet voices. The loudest person is rarely the one with the most important observation. Silent writing before discussion, anonymous input where needed, and dot-voting all move the session away from “whoever talks most wins” and toward what the team actually thinks. Run it so the quietest person in the room can still set the agenda.

Common anti-patterns

Retros fail in predictable ways. Naming them is half the fix.

It turns into blame. The moment the session is about who caused a problem, the honest material dries up and does not come back. The prime directive and anonymous input exist precisely to keep the focus on the system, not the person.

Nothing follows through. This is the big one. A retrospective without follow-through teaches the team that nothing changes, and attendance and candor both fall. Aim for one or two actions, each with a single owner and a date, and review them at the start of the next retro. Shared ownership is no ownership.

The same format every time. Running Start Stop Continue every sprint for a year turns the retro into a form to fill in. Rotate the format to keep the team actually looking.

A retrospective without follow-through teaches the team that nothing changes. The follow-through is the whole point.

Remote retrospectives

A distributed team can run a retrospective just as well as a co-located one, and often better, because a shared online board levels the field. The mechanics shift slightly:

Make silent, written input the default. It is already the strongest move in the room, and remotely it also solves the “everyone talks over each other on the call” problem.
Use one shared board everyone can see and edit. Anonymity is easier online, which helps candor.
Watch the energy. Remote sessions tire people faster, so keep it timeboxed and consider a light game to open. See online retrospective games for ideas that work over video, and the retrospective games guide for how to fold them into a session.

The five phases and the agenda above work unchanged remotely. The facilitation, not the location, is still what decides whether it lands.

Run your next retrospective in TeamRetro

TeamRetro runs the whole flow above out of the box: silent independent brainstorming, anonymous grouping and dot-voting, a timeboxed agenda, and actions tracked retro to retro so last session’s commitments are the first thing you see next time. Pick a format, invite the team, and run your next retrospective with the follow-through built in.

Frequently asked questions

What are the five phases of a retrospective?

The five phases come from Esther Derby and Diana Larsen’s Agile Retrospectives: set the stage, gather data, generate insights, decide what to do, and close. Set the stage opens the room and makes it safe to speak. Gather data gets everyone’s view of what happened onto the table. Generate insights looks for the patterns and root causes behind that data. Decide what to do turns the best insight into one or two owned actions. Close confirms the actions and checks how the session itself went. Almost every retrospective format is a different way of moving a team through these same five steps.

How long should a retrospective be?

For a typical two-week sprint, 60 minutes is a good default and enough for a focused session. Shorter teams or shorter sprints can run a tight 30 to 45 minutes; a longer look back over a quarter or a major release can justify 90 minutes or more. The length matters less than the discipline: protect the full slot, keep each phase timeboxed, and finish with agreed actions rather than running over on discussion. A retro that regularly overruns usually needs a tighter agenda, not more time.

What is the prime directive of a retrospective?

The prime directive is a line, written by Norm Kerth, that facilitators read at the start of a retrospective to set the tone: regardless of what we discover, we understand and truly believe that everyone did the best job they could with what they knew at the time, their skills and abilities, the resources available, and the situation at hand. Its purpose is to shift the session away from blame and toward improving the system the team works in. When people trust that the room is not about fault, they raise the real problems, which is the only way a retro produces useful actions.

What’s a good agenda for a first retrospective?

Keep a first retrospective simple and safe. Use a 60-minute slot: 5 minutes to set the stage and read the prime directive, 15 minutes for everyone to add notes silently and share them, 15 minutes to group and dot-vote on what matters most, 15 minutes to agree on one or two actions with named owners and dates, and 10 minutes to close and check how it went. Choose an approachable format like Start Stop Continue or Mad Sad Glad so the team is not learning a complex framework and reflecting at the same time. The goal of a first retro is a safe, useful habit, not a perfect one.

How do you run a remote retrospective?

Run a remote retrospective on one shared online board that everyone can see and edit, and lean even harder on silent, written input first. Have each person add their notes independently, anonymously if the topic is sensitive, before any discussion, so the call does not become whoever unmutes first. Then group the notes, dot-vote, and dig into the top items together, exactly as you would in person. Keep it timeboxed because remote sessions tire people faster, and record actions with owners and dates in the same place so they carry over to next time. The five phases and a standard 60-minute agenda work unchanged over video.

Keep going

The Scrum Master’s retrospective guide: the long-form, chapter-by-chapter companion to this overview.
Browse retrospective templates: ready-to-run formats for your next session.
Retrospective games guide: light activities that open a session and keep remote teams engaged.