Retrospective template
A retrospective agenda that ends with two or three real changes
This free retrospective agenda follows five stages: set the stage, gather data, generate insights, decide what to do and close. It fits a 60-minute meeting after a sprint or project, keeps blame out of the room and limits the outcome to a few actions that each have an owner, a first step and a date.
Copy this retrospective agenda
The timings below are for 60 minutes. For 90 minutes, add the extra time to stages 2 and 3; the decision stage rarely needs more than 15 minutes.
Retrospective · [Team] · [Sprint or period]
60 minutes · Facilitator: [name] · Notes: [name]
Board: [link]
Ground rule (read aloud): we are looking for ways to
improve how we work, not for someone to blame.
1. Set the stage (0–5 min)
- The goal of this retro in one sentence:
- Check-in: one word for this sprint.
- Last retro's actions: done / not done / dropped?
2. Gather data (5–20 min)
- Timeline: releases, incidents, surprises, changes in scope or people.
- Silent writing, 5 minutes. Each person adds notes: Went well / Didn't go well / Puzzled us
3. Generate insights (20–35 min)
- Group similar notes into themes.
- Vote: 3 votes each, on any theme.
- For the top 2 themes: why did this happen? Keep asking "why" until you reach something the team can change.
4. Decide what to do (35–50 min)
- At most 2–3 actions.
- Each one: owner, first step, date, and how we will know it worked.
5. Close (50–60 min)
- Read the actions back.
- Retro on the retro: one thing to keep and one to change about this meeting.
- Thank people for being candid.What makes a retrospective action stick?
An action sticks when it is small enough to start this week and someone owns it by name. “Communicate better” fails that test; “post release notes in the team channel before every deploy” passes it.
Action: [specific change in how we work]
Owner: [one person]
First step: [what happens this week]
Due: [date]
Check at the next retro: [the signal that shows it worked]Put the actions where the team already looks — the tracker, the sprint board or the stand-up notes — and open the next retrospective with them. Record the outcome with the meeting minutes template if your team keeps formal notes.
How do you keep retrospectives from getting stale?
Change the prompts in stage 2 every few sprints while keeping the five stages. The structure protects the outcome; the prompts keep people thinking.
Start, stop, continue
What should we start doing, stop doing and keep doing? Quick and concrete; good for a team new to retros.
Liked, learned, lacked, longed for
Four columns that bring out learning and missing support, not only problems. Useful after a project with new tools or people.
Sailboat
Wind is what pushed us forward, anchors held us back, rocks are risks ahead. A visual board that helps quieter people join in.
Timeline only
After an incident or a long release, spend most of the time building a shared timeline. Insights often appear once the order of events is clear.
In a remote retro, silent writing matters even more: give everyone five quiet minutes to add notes before anyone speaks, so the first opinion does not set the tone.
Where Meeto helps with remote retrospectives
Meeto gives the retro a recurring slot on one link, a shared screen everyone can draw on and, on paid plans, notes that list decisions and action items. Plan the length around the Free time limit.
- Schedule it with the sprint. Under Custom, choose every 2 weeks on the sprint's last day and end the series after the number of sprints left, or on the project end date. One link works for every retro.
- Work on the board together. The facilitator shares the board; participants group themes by drawing rectangles, ellipses, arrows and text over the shared screen. The presenter can turn drawing off.
- Collect votes without a poll. Meeto has no polls or breakout rooms. Vote on the board itself, or ask everyone to draw a mark next to their three themes.
- Keep the actions. Chat messages disappear when the meeting ends, so copy anything useful from the chat to the board before closing.
| Plan | What to plan for |
|---|---|
| Free | Up to 10 participants. The call stops after 60 minutes once two people are present, with warnings at 5 and 1 minutes — plan 55 minutes, not 60. |
| Pro and Team | Up to 25 participants and no time limit for up to 2 simultaneous meetings, so a 90-minute project retro runs to the end. |
| AI summary | Pro and Team, 10 hours a month: a short summary, key points, decisions and action items with a full transcript. |
If the team agrees to an AI summary, the host starts it and every participant sees that it is on. Some teams speak less freely with notes running; ask first, and choose “Only me” when the facilitator will clean up the actions before sharing them. For more on screen tools, see screen sharing with annotations.
Frequently asked questions
How long should a retrospective be?
About an hour for a two-week sprint, and up to 90 minutes after a longer project or a difficult release. Shorter retros tend to skip the insight stage and jump from complaints straight to vague actions.
Who should facilitate the retrospective?
Someone who can stay neutral about the outcome. Many teams rotate the role; a person from another team works well after a tense period. The manager can join as a participant, but should not run the discussion about their own decisions.
How many action items should a retro produce?
Two or three at most, each with one owner and a date. A long list feels productive but rarely gets done, and unfinished actions make the next retrospective less trusted.
What if the same problems come up every time?
Check whether last time's actions were actually done. If they were and the problem stayed, the action addressed a symptom; spend the insight stage asking why the problem keeps returning, or bring in the person who can change the underlying constraint.
Can people add notes anonymously?
Meeto does not collect anonymous input. If your team needs anonymity, gather the notes in a board or form tool that supports it before the call and share that board on screen during the meeting.
Put it to work
Open your Meeto account to set it up, or explore the working product first.