Built for Remote teams
Remote Retrospectives That Keep Everyone Involved
Run a structured remote or hybrid retrospective with a shared host screen and a private participant view on every device.
A practical RetroRally guide · Updated August 2026
The facilitation challenge
Remote calls magnify unequal airtime, lag, side conversations, and screen fatigue. A shared board alone does not prevent the fastest typer or loudest speaker from defining the problem.
What a good session should produce
- Join by link or room code without participant accounts
- Quiet writing on each person’s phone or browser
- Simultaneous reveals and private votes
- A host clock visible in the shared screen
- Reconnect support when a device refreshes
A practical workflow
- Share two surfaces. Present the host screen in the call and send the participant room link in chat.
- Write in silence. Mute discussion during input rounds so location and audio confidence do not determine influence.
- Reveal together. Use synchronized stage changes so nobody is working from an outdated board.
- Discuss one issue. Keep cameras optional and invite short clarification before opinions.
- Record the mission. Give the action an owner and date that remain visible after the call.
Suggested agenda
- 2 min technical check
- 4 min mood
- 8 min private input
- 5 min reactions
- 12 min options and discussion
- 4 min decision and owner
Common failure modes
- Using screen share as the only way to contribute
- Reading while participants are still typing
- Letting chat become a second unsynchronised board
- Skipping a reconnect and audio fallback plan
Where RetroRally fits
Boss Battle is the format currently playable in RetroRally. It combines an anonymous-to-the-room mood check and issue collection with impact ranking, one concrete solution per player, discussion, private voting, and an owned mission. See every stage or try the live room.
Continue learning
Browse questions by team situation, compare facilitation templates, or use the complete sprint retrospective agenda.