Retrospectives your team is honest in
Anonymous cards revealed together, hidden dot voting, eleven formats, and action items that come back at the next retro. Free for your whole team.
A retrospective only works if people say what they really think, and if something changes afterwards. Scrums is built around both: a format that protects honest input, and action items that don't get lost between one retro and the next.
How a retro runs in Scrums
- Icebreaker. A warm-up question to start the conversation. The facilitator can shuffle for another or write their own.
- Review. Open action items from earlier retros, with their owners and status, so the team sees what got done before it writes anything new.
- Reflect. Everyone writes privately. Other people's cards are face-down: neither their words nor their authors leave our server until the reveal. You can see how many people are still writing.
- Group. Cards are revealed together. Drag similar ones into topics, or let Auto-group cluster them for you, on our own server, with no outside AI service involved.
- Vote. Dot voting with the same budget for everyone and a cap per topic. Tallies stay hidden until voting closes, so nobody follows the crowd.
- Discuss. Topics in order of votes, each with one thread for the conversation and its action items. Every action item has an owner, a due date and a status.
- Summary. The ranked topics, the action items and who came, saved as a page for the team, and ready to export as Markdown, CSV or PDF.
Anonymous by default
Retros in Scrums are anonymous unless the facilitator chooses otherwise, and once anyone has written a card, anonymity can't be switched off. In anonymous retros, comments in the discussion can be anonymous too. It's the simplest way to get the feedback people would otherwise keep to themselves. Why it matters
Eleven formats, and your own
Start with a classic like Start · Stop · Continue, change the angle with Sailboat or 4 Ls, or look back on a whole project with Plan vs. Actual. Each format below has its own guide: what it's for, how to run it, and its questions. Teams can also make their own templates, and an organization's admins can share templates with every team in it.
Action items that get done
The most common complaint about retros is that nothing changes. In Scrums, action items carry into the next retro's Review step, each person sees theirs in My action items, and an email reminder arrives when one is nearly due. Five habits that close the loop
For the facilitator
A countdown timer that's the same on every screen and chimes at the end, a ready meter that shows who has finished, buttons to move between steps, and a voice call inside the meeting for remote teams. Hand over to someone else at any point, and if your connection drops, anyone can take over.
Try a retro in your browser with a sample team, no account needed, or sign up free.
Questions
Is it really free?
Yes. Every feature is included for your whole team, with no credit card and no trial clock.
How anonymous is an anonymous retro?
While people write, other people's cards are face-down, and the cards' authors never leave our server, even after the reveal. Facilitators can't see who wrote what either.
Do people need an account?
Everyone in a retro signs in, so action items have owners and summaries reach the right people. Signing up takes a minute, with an email address or a Google account. To look around first, the demo needs no account at all.
Retro formats
- The 4 Ls retrospective: Liked, Learned, Lacked, Longed for. Four questions that help a team reflect on a sprint, a project or an event. How to run a 4Ls retrospective well.
- The Keep, Add, Less, More retrospective: Keep, Add, Less, More (KALM) tunes how your team works by degree instead of all-or-nothing. What goes in each column and how to run it.
- The Mad, Sad, Glad retrospective: A retrospective about how the team feels: what made people mad, sad and glad. How to run it safely and turn feelings into useful action.
- The Plan vs. Actual retrospective: Compare what you planned with what happened, find out why they differ, and decide what to keep and what to change next time.
- The project wrap-up retrospective: Look back on a finished project: the goals you met, what slowed you down, what you learned, and who deserves credit for it.
- The Quick Review retrospective: A short retro for straight after a release, launch or incident. Three columns, Sustain, Improve and Fix now, catch what people noticed while it's fresh.
- The Rose, Bud, Thorn retrospective: Roses for highlights, buds for ideas with potential, thorns for pain points. A short, friendly retro format, and how to run it well.
- The sailboat retrospective: Wind, anchors, rocks and an island. A retro about what moves your team toward its goal, what holds it back, and the risks ahead.
- The starfish retrospective: Keep doing, less of, more of, stop doing and start doing. Five arms for feedback with more nuance than a plain start and stop.
- The Start, Stop, Continue retrospective: Three questions about how your team works: what to start doing, what to stop, and what to keep. How to run it so the cards turn into change.
- The Went Well, To Improve, Ideas retrospective: A simple, balanced retro: what went well, what to improve, and ideas to try next. How to run it so it ends in experiments, not complaints.