TL;DR: To run a retrospective meeting well, follow five stages: set the stage, gather data, generate insights, decide what to do, and close. Keep it short (the Scrum Guide caps a retrospective at three hours for a one-month sprint, and shorter sprints usually mean shorter retros), make it safe to speak honestly, and leave with one to three specific actions that have an owner and a date. Rotate formats such as Start/Stop/Continue, Mad/Sad/Glad or the 4Ls to keep it fresh, and always open the next retro by reviewing last time’s actions.
A retrospective is a regular team meeting to look back at how you worked and decide what to change. Agile teams hold one at the end of every sprint, but any team can use it after a project, a launch or a rough month. This guide shows you how to run a retrospective meeting step by step, with an agenda, formats, questions and the mistakes that make retros feel pointless.
What a retrospective is for
The 2020 Scrum Guide says the purpose of the Sprint Retrospective is “to plan ways to increase quality and effectiveness.” The team inspects how the last sprint went with regard to individuals, interactions, processes, tools and its Definition of Done, discusses what went well and what problems it hit, and identifies the most helpful changes. The guide adds that the most impactful improvements should be addressed as soon as possible and may even be added to the next sprint’s backlog.
Notice what’s missing: blame. A retrospective improves the system the team works in. It isn’t a performance review, and it shouldn’t feel like one.
Before the meeting
- Pick a facilitator. Ideally someone who can stay neutral. Rotating the role spreads the skill.
- Set the timebox. 45 to 90 minutes suits most two-week sprints. The Scrum Guide’s limit is three hours for a one-month sprint.
- Choose a format (see below) and prepare the board, whether that’s sticky notes on a wall or an online whiteboard.
- Bring the facts: what was planned, what shipped, incidents, and the action items from the last retro.
- Invite the right people: the people who did the work. Managers who attend should listen more than talk.
How to run a retrospective meeting: the 5-stage agenda
The most widely used structure comes from Esther Derby and Diana Larsen’s book Agile Retrospectives: Making Good Teams Great. Here’s a practical version for a 60-minute session:
| Stage | Goal | Time (60-min retro) |
|---|---|---|
| 1. Set the stage | Welcome people, state the focus, agree on ground rules | 5 min |
| 2. Gather data | Build a shared picture of what happened | 15 min |
| 3. Generate insights | Find patterns and root causes | 15 min |
| 4. Decide what to do | Pick 1 to 3 actions with owners | 15 min |
| 5. Close | Recap actions and get quick feedback on the retro itself | 5–10 min |
1. Set the stage
Start by reviewing the actions from the previous retro: done, in progress or dropped? Then remind everyone why you’re here. Many teams read Norm Kerth’s Retrospective Prime Directive: “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.” A quick check-in, such as “one word for this sprint,” gets every voice in the room early.
2. Gather data
Give people a few minutes of silent writing first, one idea per sticky note. Silent writing stops the loudest person from setting the agenda. Then put notes on the board and group similar ones. Include facts as well as feelings: a missed deadline and “I felt rushed all week” are both useful data.
3. Generate insights
Dot-vote on the clusters that matter most, then dig into the top one or two. Ask “why” a few times to move from symptoms to causes. A note like “too many bugs in QA” might trace back to unclear acceptance criteria or a release crunch.
4. Decide what to do
This is where most retros fail. Good actions are:
- Few: one to three per retro. Ten actions means none get done.
- Specific: “Add acceptance criteria to every story before sprint planning,” not “communicate better.”
- Owned: one named person, even if the whole team helps.
- Visible: added to the team’s backlog or board, as the Scrum Guide suggests.
If an action needs someone to take on new work, our guide on how to delegate tasks effectively can help you hand it off clearly.
5. Close
Read the actions back, confirm owners, and thank people. Spend two minutes on a “retro of the retro”: on a scale of 1 to 5, was this worth the time? That feedback keeps the meeting improving too.
Retrospective formats to rotate
Using the same format every time leads to the same answers. Rotate through these:
| Format | Prompts | Best for |
|---|---|---|
| Start / Stop / Continue | What should we start, stop and keep doing? | Quick, action-oriented retros |
| Mad / Sad / Glad | What made you mad, sad or glad? | Surfacing feelings after a tough sprint |
| 4Ls | Liked, Learned, Lacked, Longed for | Projects and launches |
| Sailboat | Wind (helps), anchors (slow us), rocks (risks), island (goal) | Looking ahead as well as back |
| Timeline | Plot key events and the team’s mood over time | Long sprints or post-incident reviews |
Atlassian’s Team Playbook retrospective play is another free template if you want a ready-made run sheet.
Good retrospective questions
- What helped us most this sprint?
- Where did we lose the most time?
- What surprised us?
- What did we say we’d do last retro, and did it help?
- If we could change one thing next sprint, what would it be?
- What’s one thing someone else did that made your work easier?
Common mistakes to avoid
- Skipping it when you’re busy. Busy sprints are when you most need it.
- Turning it into a blame session. Talk about processes and decisions, not personalities. For individual issues, use a private conversation; our guide to the SBI feedback model shows how.
- The manager talks first. It anchors everyone. Let the team speak before leaders weigh in.
- No follow-through. If actions vanish, people stop contributing. Review them at the start of every retro.
- Same format forever. Rotate formats to avoid autopilot answers.
Remote retrospective tips
- Use a shared online whiteboard and give people a minute to get familiar with it.
- Ask for cameras on if your team is comfortable, and use anonymous notes for sensitive topics.
- Call on people gently by name so quieter teammates get space.
Retros work best alongside regular one-on-one meetings, which handle individual concerns the group setting can’t.
The bottom line
Knowing how to run a retrospective meeting comes down to a simple loop: look back honestly, find the real cause, commit to a small number of changes, and check whether they worked. Do that every sprint and the meeting stops being a ritual and starts being the way your team gets better.
The Teck Hustlers Editorial Team covers technology, business, finance and gaming news for readers who want the story behind the headline. Every article is researched, written and edited by our in-house team, checked against company announcements, filings and reputable reporting, and updated when new facts emerge. We focus on what each development means for founders, professionals, investors and everyday users. Have a tip or a correction? Reach us through our contact page.
