RetroSyncoperator's guide · § 9 · for scrum masters · rev. 0.4
§ 9.A · SCRUM MASTERS

Run retros teams
actually look forward to.

As the facilitator, your job is to keep things moving, safe, and useful. RetroSync handles the structure so you can focus on the conversation.

Fig. 9.A.0 — The four facilitation needs below, plus the three templates that carry most sprint retros.
9.A.1What a scrum master needs

Four things. None of them is a slide deck.

Every facilitator we've talked to comes back to the same four needs. The product is shaped around them.

§ 9.A.1.a
A.
Phase pacing without policing
Brainstorm → group → vote → discuss flows automatically. Move the team forward without watching the clock.
§ 9.A.1.b
B.
Anonymous when it matters
Toggle anonymity per board so quieter teammates and dissenting views land safely.
§ 9.A.1.c
C.
Recaps that send themselves
One-click AI summary of themes, decisions, and actions. Paste into Slack or email in seconds.
§ 9.A.1.d
D.
Action follow-through
Owners and due-bys live in the board; reminders nudge between sessions so you facilitate, not chase.
A working Scrum MasterHypothetical, but soon.
user since v. 0.3

The first retro tool that made me feel less like a project manager and more like a coach. The team noticed the difference too.

9.A.3Templates that fit a sprint cadence

Start with the three that work for most teams.

Full catalogue is in § 5. Pick one to begin; the team will fork its own version within two sprints.

5.A.1ClassicWent well · didn't · try next. The fallback every team knows.most sprintsuse →
5.A.2SailboatWind · anchors · rocks · land. For talking about team velocity.monthlyuse →
5.A.3Mad · Sad · GladTalk about how the sprint felt before fixing what went wrong.rough sprintsuse →
§ 9.A — For scrum masters · Free during beta

Make your next retro the one teams remember.

Free during beta. No credit card. 60-second setup.

Try the demo