All meeting agenda templates
Free meeting template

Sprint Retrospective Template

A sprint retrospective is a 45-minute meeting at the end of each sprint where the team looks at how it worked, not what it built. It ends with one or two changes the team will try in the next sprint, each with an owner.

Agenda

45 min · 5 parts

  1. 0:00Set the stage5 minRecap the sprint and its goal, and agree to talk openly
  2. 5:00What went well10 minWhat to keep doing
  3. 15:00What to improve15 minWhat slowed us down, and why
  4. 30:00Ideas10 minExperiments to try in the next sprint
  5. 40:00Actions5 minPick one or two, with owners
Use this template

Free to start. Guests join from a link, no account needed.

Length
45 min
How often
At the end of every sprint, after the sprint review and before the next planning.
Who attends
The whole Scrum team: developers, the product owner and the Scrum Master, who usually facilitates.
You leave with
One or two changes the team will try in the next sprint, each with an owner.

The agenda, part by part

How to run a sprint retrospective

  1. 1. Set the stage

    5 min

    Remind everyone of the sprint goal and what happened: what shipped, what slipped, anything unusual. Restate the ground rule that the retro is about the process, not about blaming people.

    Ask: In one word, how did this sprint feel?

  2. 2. What went well

    10 min

    Give everyone a few minutes to write what worked before anyone speaks, then group similar notes. Naming what went well protects good habits from being lost when the team changes something else.

    Ask: What helped us most this sprint?

  3. 3. What to improve

    15 min

    Collect what got in the way, then pick the two or three themes with the most votes and ask why each happened. The longest part of the retro belongs here, because a fix is only as good as the cause it targets.

    Ask: What would we do differently if we ran this sprint again?

  4. 4. Ideas

    10 min

    For each theme, ask for small experiments the team could try in one sprint. Small and reversible beats ambitious and vague.

    Ask: What's the smallest change that would make a difference?

  5. 5. Actions

    5 min

    Vote and keep the top one or two ideas. Give each an owner and add it to the next sprint's backlog, so it competes for time like any other work.

    Ask: Who owns this, and how will we know it worked?

Retrospective questions to ask

  • What should we start, stop and continue doing?
  • Where did we lose the most time this sprint?
  • Did we meet the sprint goal? What helped or got in the way?
  • What surprised us?
  • Which handoff was the hardest?
  • Did last retro's action make a difference?
  • What would make the next sprint more enjoyable?

Example: a retro after a sprint that missed its goal

A six-person team missed its sprint goal because two stories waited days for review.

Notes

  • Went well: pairing on the payment bug; the demo was ready a day early.
  • To improve: pull requests waited up to three days for review (5 votes).
  • Cause: everyone reviews at the end of the day, after their own work.
  • Idea: a 30-minute review slot after standup.

Action items

  • Ana: add a daily review slot after standup, from Monday.
  • Team: check review wait times at the next retro.

Ways to adapt it

Start, stop, continue

Replace went well and to improve with three columns. It works well for teams new to retros because every note already suggests an action.

Remote or async retro

Collect notes in a shared doc the day before, so the call goes straight to grouping, voting and actions. 30 minutes is often enough.

Release or quarter retro

For a longer period, add a timeline part where the team marks the highs and lows week by week, and allow 60 to 90 minutes.

Common mistakes

  • Leaving with a long list of actions.

    Instead: Commit to one or two. A team that finishes one change per sprint improves faster than one that starts five.

  • Talking about people instead of the process.

    Instead: Ask what made a mistake easy to make, not who made it. Say the ground rule out loud at the start.

  • Never checking last retro's actions.

    Instead: Open each retro by reviewing what the team tried last time and whether it worked.

  • Running the same format every sprint.

    Instead: Change the questions every few sprints so the conversation doesn't become routine.

Sprint retrospective vs sprint review

The sprint review looks at the product: the team shows what it built and stakeholders give feedback on it. The retrospective looks at the team: how it worked and what to change. The review comes first, with stakeholders; the retro follows, with the team only.

Run it in Edworking

Your agenda keeps the meeting on time

Start a video meeting from any template. Edworking turns the agenda into the structure of the call, so nobody has to watch the clock.

Live agenda

A timer for every part

Everyone sees the agenda and how long is left in each part, with a clear moment when the meeting moves on.

AI notes

Notes that follow the agenda

AI takes the notes part by part and writes the summary and action items when the call ends.

Tabs in the call

Your work on screen, no sharing

Open docs, tasks and files as tabs in the call. Everyone sees the same thing without anyone sharing a screen.

Guests

Anyone can join from a link

Free to start. Clients, candidates and guests join from a link, with no account needed.

See how video calls work in Edworking

Frequently asked questions

The Scrum Guide sets a maximum of three hours for a one-month sprint. For a two-week sprint, 45 minutes to an hour is usually enough.

One workspace. Flat team pricing. Start free today.

Get Started Now