Quick summary
A sprint retrospective is the meeting after the sprint where the people who did the work decide what to change next. Run it in six steps: open with the purpose, collect cards in silence, group them, vote, discuss only the top themes, and close with one to three actions that have an owner and a review date. Forty-five minutes is enough for a two-week sprint. The same agenda answers “how to run a retrospective” when the team is not using Scrum.
What is a sprint retrospective?
A sprint retrospective is a recurring meeting at the end of a sprint. The team looks at how it worked, not at the product backlog. The output is a small change to try before the next retro.
It is not the sprint review. The review is for the increment and the stakeholders. The retro is for the team.
You still need this meeting if you do not call the cycle a sprint. A two-week delivery team, a product trio, or an on-call rotation can use the same steps. That is the whole of “how to run a retrospective” and “how to run retrospective”: same structure, same timebox, same action format.
Who is in the room
Invite the people who did the work: engineering, product, design, and QA when they were on the sprint. The facilitator can be anyone on the team. A Scrum Master is useful, not required.
Keep managers and stakeholders out unless the team has already said their presence is safe. A retro that becomes a status report stops producing honest cards.
Participants should join from a link, without creating an account in the meeting. Account walls burn the first five minutes. See online retrospective tool with no signup.
How long, and when
| Sprint length | Retro length | When |
|---|---|---|
| 1 week | 30–45 minutes | Same day as the review, before planning |
| 2 weeks | 45–60 minutes | Same day as the review, before planning |
| 3–4 weeks | 60–75 minutes | Same day as the review, before planning |
Do not schedule it “sometime next week.” The sprint is still in memory on the day of the review. Waiting until Monday means people reconstruct the sprint from Slack.
How to run a sprint retrospective
1. Set the stage (5 minutes)
Say what the meeting is for, and what it is not. One sentence is enough: “We are here to pick one or two changes for the next sprint. We are not here to rank people.”
If the last retro had actions, spend two minutes on them first: done, still open, or dropped on purpose. Skipping this step teaches the team that actions do not matter. The format is in the action items guide.
2. Collect cards in silence (8–10 minutes)
Pick one board. For a first retro, use Start, Stop, Continue or Went well, To improve, Actions.
Everyone writes at the same time, without talking. Silent writing is what stops the first three speakers from setting the whole agenda. Anonymous mode helps when the topic is a person, a manager, or a repeated incident.
Ask for specific cards. “Standup ran long on three days because we debugged production in it” is a card. “Communication” is not.
3. Group (5 minutes)
Read the cards out loud or let people drag duplicates together. Name each group in a few words. Do not debate solutions yet.
4. Vote (3 minutes)
Give each person three votes. They can stack votes on one theme. The vote is how a quiet person’s card beats a loud person’s monologue.
5. Discuss the top themes (15–20 minutes)
Talk about two or three groups, not the whole board. For each one, ask: what happened, what would we try, and who would notice if it worked?
Stop when you have an action, not when the story is finished.
6. Close with actions (5 minutes)
Write one to three actions. Each one needs:
- one owner
- a concrete change, not a value
- a date you will look at it again, usually the next retro
“Communicate better” is not an action. “Move production debugging out of standup and into a 15-minute incident thread, owned by Sam, reviewed next retro” is an action.
Read the actions back. End on time.
A 45-minute agenda you can paste
| Minutes | Step |
|---|---|
| 0–5 | Purpose, then last retro’s actions |
| 5–15 | Silent cards |
| 15–20 | Group |
| 20–23 | Vote |
| 23–40 | Discuss the top two themes |
| 40–45 | Write actions and stop |
Common ways this meeting fails
- No silence. The retro becomes the same three people talking.
- No vote. The facilitator’s favorite topic wins.
- Too many actions. More than three means none of them fit in the next sprint.
- No review next time. The board is archived and the same card returns.
- Wrong meeting. Product feedback and incident timelines need their own sessions. A sprint retro can note an incident. A blameless retrospective is where you examine it.
If people stop showing up, read how to increase retrospective engagement. If the meeting happens but nothing changes, read how to improve a sprint retrospective.
Frequently asked questions
How to run a sprint retrospective?
Use six steps in 45 minutes for a two-week sprint: set the stage, write cards in silence, group, vote, discuss the top themes, and leave with one to three owned actions. Review the previous actions in the first five minutes.
How to run a retrospective?
Use the same six steps even if the team does not run Scrum. The meeting still needs silent input, a vote, and an owner. Change the board columns to match the work, not the job titles.
How to run retrospective?
Same answer: a timeboxed board, silent cards, a vote, and one to three actions. Skip the slideshow. Do not wait for a certified facilitator.
Who should facilitate?
Anyone on the team can facilitate. Rotate it. The facilitator protects the timebox and the vote. They do not supply the conclusions.
What if the team is remote?
Share one link. Keep cameras optional, cards mandatory. Silent writing matters more when people are on mute. A timer still ends the meeting.
Try NextRetro free and run this agenda on a Start-Stop-Continue board. Participants join from the link.
