Sprint Retrospective Board
Add sticky notes, vote on items, and export your retro as Markdown. No login, no signup — runs entirely in your browser.
Files processed in your browser — never uploaded to our serversWent Well
No notes yet — type above and press Enter or click Add
To Improve
No notes yet — type above and press Enter or click Add
Action Items
No notes yet — type above and press Enter or click Add
Frequently Asked Questions
No. All data lives entirely in your browser's memory. Nothing is sent to any server. Refresh the page and the board resets.
Click 'Export as Markdown' to copy the full board as formatted Markdown text. Paste it into Notion, Confluence, Slack, or any text editor.
This tool is designed for single-user facilitation — to take notes during a ceremony. For real-time collaboration, each person would need to open their own board and the facilitator can consolidate notes.
'Went Well' captures wins and positives. 'To Improve' captures friction, blockers, and frustrations. 'Action Items' captures concrete next steps the team commits to.
Yes — click the thumbs-up icon on any note to vote for it. Voting helps the team dot-vote and prioritize which topics to discuss first.
A sprint retrospective is an agile ceremony held at the end of each sprint where the team reflects on how they worked together — not what they built, but how they built it. The goal is to identify concrete improvements to carry into the next sprint.
In Scrum, a retrospective is run once per sprint — so every one to four weeks depending on your sprint length. Most teams find a two-week cadence gives enough time to implement changes before the next retro.
This tool runs entirely in your browser without a backend, so it does not support real-time multi-user collaboration. The recommended approach is for the facilitator to run the board on a shared screen during the ceremony and type notes as the team discusses each item.
Click the 'Export as Markdown' button to copy the full board as formatted Markdown. You can then paste it into Confluence, Notion, a GitHub issue, Slack, or any tool that renders Markdown so the notes are preserved for future reference.
The three-column format (Went Well / To Improve / Action Items) is the most widely used and works well for remote teams because it is simple, focused, and easy to explain to new members. For variety, some teams alternate with formats like Start / Stop / Continue or the 4Ls (Liked, Learned, Lacked, Longed For).