June 17, 2026 · 9 min read

How to run a sprint retro your team actually enjoys

A live, anonymous sprint retrospective that gets honest input in 15 minutes: a health check, kudos, went-well and improve word clouds, and a quick vote on what to fix first.

By the PollsLive team·Teams & meetingsQ&A

You know the retro that goes quiet. The loudest person talks, three people nod, and the doc fills with polite nothing. The honest stuff - the friction, the near-misses, the thing nobody wants to say to the lead - never makes it onto the board. Here's a format that fixes that, and it runs live, anonymous, and in about 15 minutes.

Tip

You do not need to be technical to follow this guide. Every step uses plain buttons in PollsLive - no coding, no app install for your audience.

We packaged it as a one-click template: open the Sprint Retro template, hit Present live, and share the join code. No accounts for the team, nothing to install.

The PollsLive editor showing the Sprint Retro template deck - a list of pages including a health-check scale, kudos and improve word clouds, a ranking, and an open-mic Q&A.
The Sprint Retro template in the editor. Eight ready-made pages: health check, kudos, went-well, improve, blockers, a ranking of fixes, and an open-mic Q&A.

Why retros go quiet (and how to unstick them)

Most retros fail for one reason: people don't feel safe being blunt, and the format rewards whoever speaks first. The fix is to collect everyone's input at once, anonymously, before anyone discusses it. When answers land as a live word cloud, the quiet engineer and the staff lead carry exactly the same weight - and suddenly the real themes show up on screen.

The 15-minute format

  1. Health check (30s). A 1-5 scale: "How healthy did this sprint feel?" You instantly see the mood before a word is spoken.
  2. Kudos (1 min). A word cloud for shout-outs. Start positive - it changes the whole tone of the room.
  3. What went well (2 min). A word cloud of keep-doing-this. Themes cluster automatically.
  4. What to improve (3 min). The honest one. Anonymous means you get the real answers, not the safe ones.
  5. Blockers (2 min). Open text: "What slowed us down?" - surfaces process drag you'd otherwise miss.
  6. Vote on actions (3 min). Rank the candidate fixes so you leave with a prioritised list, not a wish list.
  7. Open mic (3 min). A moderated Q&A with upvotes for anything left unsaid - the room decides what matters.

What the board actually looked like

Here's a real-shaped run. Priya, an EM on a 9-person squad, opened with the health check while people were still settling in. The number was lower than the standups had suggested - which was exactly the conversation worth having:

Live scale
Join at the PIN 6098

How healthy did this sprint feel? (1 = rough, 5 = great)

5 - Great11% · 1
4 - Good22% · 2
3 - OK22% · 2
2 - Rough33% · 3
1 - Bad11% · 1
Average 2.9 - visibly bumpier than the daily 'fine, fine, fine' suggested.

Kudos came next, and the tone in the room flipped - people grinning at their own names showing up on the wall:

Kudos - who or what made this sprint better?

Sam-saved-the-deploygreat-pairingdesign-handoffJess-on-supportfast-reviewsthe-new-runbookcalm-standups
Shout-outs that would never get said out loud, landing as the biggest words on screen.

Then the honest one. Anonymous, so the answer everyone felt but nobody had raised finally surfaced:

What slowed us down this sprint?

flaky-CIscope-creepwaiting-on-reviewsunclear-ticketstoo-many-meetingsstaging-was-downcontext-switching
'Flaky CI' was felt by half the team - but had never made it onto a board before.

Finally the team ranked the candidate fixes, so they left with a prioritised top-3 instead of a vague intention to 'do better':

Live poll

What should we fix first next sprint?

Stabilise the CI pipeline44% · 4
Tighten ticket-writing / acceptance criteria33% · 3
Cap WIP and reviews SLA22% · 2
Trim the meeting load0% · 0
One clear winner - 'fix CI' became the sprint's first committed action item.

What it feels like in the room

The shift is physical. By the kudos slide people are smiling at the screen; by "what to improve" the cloud is genuinely alive because nobody's name is attached. You stop chairing a meeting and start reading the room. The kind of words that fill these clouds:

  • "finally - anonymous" · "actually honest" · "so fast" · "can we keep doing this?"
  • Kudos that would never be said out loud landing as the biggest words on the wall.
  • A blocker three people quietly felt suddenly showing up in 12-point - and getting fixed next sprint.

We don't publish invented testimonials - but the kudos cloud at the end of a good retro is the most honest review you'll get, and it's right there on the screen.

Turn talk into action (and share it)

  • Prioritised, not hand-wavy. The ranking slide gives you a clear top-3 to commit to.
  • Share the result, not a transcript. Drop the results link into Slack or Teams, or embed it on your team wiki - see integrations.
  • Export when you need rows. One-click Excel export (Pro) feeds your tracker; paste action items straight into Jira/Linear/Notion.

When to use it - and when not

  • Great for: remote and hybrid teams, big groups where airtime is unequal, and any team where honesty has gone a bit quiet.
  • Skip it for: a two-person chat - just talk. The magic is in giving a whole room an equal, anonymous voice.

Open the Sprint retro template and run your next one live - free, no signup, no app for your team.

Use the Sprint retro template

Tip

Keep retro anonymous for the health scale - honest scores need no names attached.

The PollsLive host console Join the room screen with PIN, QR code, and participant count.
Present live opens the host console - share the PIN or QR so people can join.
The PollsLive templates gallery with ready-made polls for classrooms, teams, events, and webinars.
Browse ready-made templates on the Templates tab or at /templates.

Reuse the deck with save poll templates. See /for/teams.