All tools

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 servers

Went 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

What is Sprint Retrospective Board?

A sprint retrospective is the Scrum ceremony held at the end of each sprint where the team reflects on what went well, what did not, and what to improve. The most widely used format is Start/Stop/Continue — what should the team start doing, stop doing, and continue doing. Other popular formats include 4Ls (Liked, Learned, Lacked, Longed For), which surfaces both positive and aspirational feedback, and Mad/Sad/Glad, which frames the retro around emotional responses and is particularly effective when team morale is a concern. The goal of every retrospective is actionable outcomes: each retro should produce one to three concrete improvement items with named owners, not just a venting session. Teams that treat the retro as a place to surface feelings without committing to change find the ceremony loses credibility and attendance within a few sprints.

How to use

  1. Select a retro format — Start/Stop/Continue for general use, 4Ls for learning-focused teams, Mad/Sad/Glad when morale or emotions need attention.
  2. Open the board and have each team member add observations to the relevant columns during the note-adding phase (10 minutes, no discussion yet).
  3. Group similar or duplicate items together to reduce noise before voting.
  4. Run a dot-vote: each participant gets 3–5 votes to spend on items they find most important — they can stack all votes on one item.
  5. Discuss the top-voted items in order, spending the most time where votes are concentrated.
  6. For each discussion point, assign a concrete action item to a named owner with a due date before the next sprint.

Why it matters

Teams that run regular, action-focused retrospectives improve sprint velocity over time because they systematically eliminate the friction that slows them down. The biggest anti-pattern in retros is discussing the same problems sprint after sprint without resolution — if the same issue appears on the board three sprints in a row, it signals a systemic problem that needs escalation beyond the retro. Retrospectives also build psychological safety when facilitated well: when team members see that raising a concern leads to a real change, they trust the process and participate more candidly. Teams that skip retros accumulate unaddressed dysfunction that eventually derails sprints entirely.

Pro tip

Time-box the retro strictly: 45 minutes for a 2-week sprint. Spend 10 minutes adding items, 5 minutes grouping, 5 minutes dot-voting, 25 minutes discussing top-voted items and assigning owners. Never end a retro without named owners for each action item — 'the team' owning something means no one owns it, and the item will reappear on next sprint's board unchanged.

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).