Running retrospectives remotely
By Scrumagic Team Last reviewed 6 min read
In short
A remote retrospective loses the sticky notes, the body language and the corridor chat, and gains a few things: easy silent writing, a record by default and flexible formats. The Guide's purpose and rules do not change. The work is to keep safety, energy and follow-through on a screen. This post gives a setup, a time plan and the usual failures, including what to do across time zones.
The retrospective is the event that depends most on trust and the least on technology, and a video call is poor at carrying trust. That is the central difficulty of running it remotely. The good news is that the format itself transfers easily, and that a few parts of it work better online.
What stays the same
The Guide's description is unchanged. The Retrospective concludes the Sprint, with a maximum of three hours for a one-month Sprint and usually shorter for shorter ones. Its purpose 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 the Definition of Done, identifies assumptions that led it astray, and discusses what went well, what problems it met and how they were or were not solved. It chooses the most helpful changes, and may add them to the next Sprint Backlog.
For a remote team, "individuals and interactions" includes the call itself. How the team works at a distance is a legitimate subject for the event.
What the screen takes away
- The wall. In a room, a wall of notes lets people read, move and cluster at once. Online, one person controls the view unless the tool is shared.
- Body language. A pause that signals a person has something to say is hard to see on a small tile.
- The side conversation. The quiet remark to a neighbour is gone.
- Informal time. Before and after the formal event, a room has chat. Online, it must be created.
What the screen gives
- Silent writing at no cost. Everyone can type at the same time on a shared board, and the loudest voice does not set the agenda.
- A record by default. The board remains, and can be copied into the Sprint Backlog.
- Easy anonymity. Cards can be anonymous when a topic is sensitive.
- Flexible formats. Voting, timers and templates are built into most tools.
The GOV.UK Service Manual's advice on agile working environments notes that digital boards and communication tools can support a team working across offices or remotely, with clear naming conventions, shared folders and agreed ways of working. A retrospective board is one of those shared tools, and it benefits from the same discipline.
A setup that works
Choose one shared board. Any tool that lets everyone write and vote at once will do. Prepare it in advance with the format already drawn, so that no time is spent setting up.
Send a short brief. The day before, send the purpose, the format and any data you will use, such as the Sprint Goal result or last time's actions. People who see it arrive prepared.
Keep the group small and the time short. Video fatigue is real. An hour is usually a better ceiling than the Guide's maximum, and ninety minutes should be exceptional. Take a short break in the middle of anything longer.
Agree camera and chat norms. Cameras help but should not be forced. A chat channel can carry comments that are not ready to be said aloud.
Use a facilitator and a scribe. The facilitator runs the conversation. Another person records decisions on the board so nothing is lost.
A time plan for 60 minutes
This is an illustrative plan for a remote team of seven using a simple format.
| Time | Activity |
|---|---|
| 0 to 5 | Welcome, purpose, the ground rule that cards describe situations and not people, and a quick check-in word from each person. |
| 5 to 10 | Review last Sprint's actions on the board: done, not done, dropped. |
| 10 to 20 | Silent writing on the chosen prompts. |
| 20 to 30 | Read and cluster. The facilitator reads a card aloud if the author wants it anonymous. |
| 30 to 35 | Vote with a fixed number of dots. |
| 35 to 52 | Discuss the top two clusters. Decide an action, an owner and a date for each. |
| 52 to 58 | Read back the actions. Move them to the Sprint Backlog. |
| 58 to 60 | One-word close, and one thing to change about the retrospective. |
Across time zones
When the team spans many hours, the live event is hard. There are three workable approaches. Choose a time that costs each person an acceptable inconvenience, and rotate who gets the worst slot. Or split the event: the writing and clustering happen asynchronously on the board over a day, and a shorter live session covers the discussion and the actions. Or keep the live event limited to the people with overlap and give the others a way to contribute and to read the outcome.
The asynchronous part works only if people really contribute, so set a deadline and a reminder. The live part should not repeat what was written. A risk of the split version is that those who wrote their cards a day earlier feel their input has gone cold, so bring the cards forward in the discussion.
What goes wrong
- Silence. Nobody speaks after a question. Use a count of three seconds, then a poll or the chat.
- Dominance by the facilitator. On video, a long facilitator monologue fills the time. Ask more, talk less.
- Tool fiddling. Time spent on the tool takes away from the conversation. Rehearse with a new tool.
- Multitasking. Mail and chat distract. A shorter event helps.
- Lost actions. Notes stay on the board and never reach the Sprint Backlog. Move them before the call ends.
- No energy. Online events can drift. Short breaks, a change of prompt and a quick check-in word help.
Checking the remote working itself
A remote team has a subject that a co-located one does not: the remote working. The retrospective is the place to ask how the call habits, the chat norms, the handovers across time zones and the use of the tools are going. Questions such as "when did you last feel out of the loop?" or "what did we decide in chat that nobody else saw?" often lead to the most useful actions for a distributed team. The Guide's reference to individuals, interactions and tools covers all of it.
Safety online
Safety is harder to read online and easier to lose. Use anonymity where a topic needs it. Keep recordings off for this event, because people speak more freely when they are not being recorded. Check in privately with someone who went quiet or seemed upset. See psychological safety in retrospectives for the underlying behaviours.
Two perspectives
Neither source prescribes this, so practice varies.
Scrum Guide
The Scrum Guide sets the Sprint Retrospective as the last event of the Sprint with a maximum of three hours for a one-month Sprint, to plan ways to increase quality and effectiveness, and says nothing specific about remote working.
SBOK®
The SBOK® Guide's Retrospect Sprint meeting is a time-boxed discussion of what went well and what did not, with agreed improvements, and it treats distributed teams through communication and collaboration tools without a remote format.
Same thing, different words
- Sprint Retrospective (Scrum Guide) = Retrospect Sprint (SBOK)
Neither source prescribes a remote format. The setup here is custom that holds to the Guide's purpose.
How to practise it
Run your next retrospective with silent writing on a shared board, and count how many different people contributed cards. In the simulator the retrospective at step 4.2 is done in a shared board format, so you can try the choices before you run them on a real team.
Sources
- The 2020 Scrum Guide, Scrum Guides. Read on 14 October 2026.
- Creating an agile working environment, GOV.UK Service Manual. Read on 14 October 2026.
SBOK® is a registered trademark of its owner. Scrumagic is independent and is not affiliated with the owners of SBOK®.
Nothing opened? This computer may have no email program set up. Write it in Gmail or use the copy button and paste the link into your email.