Sprint Retrospective Board

Collect retro cards in What Went Well, What to Improve and Action Items columns, upvote them, and download a ranked Markdown summary for the sprint.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Sprint Retrospective Board?

The Sprint Retrospective Board is a three-column retro: What Went Well, What to Improve and Action Items. You add the team and sprint number, then add cards one at a time by choosing a column, choosing the author from the team list and typing the text. Each card has a thumbs-up button for voting and a delete button.

Cards inside each column are sorted by votes, so the topics the team cares most about rise to the top. An Additional Notes box holds anything that does not fit on a card. Download Summary produces a Markdown file with the team, sprint, every card grouped by column in vote order, and the notes.

The board, team list and notes are saved in this browser as you go, so a refresh keeps them, but there is no real-time sync. It works best on one shared screen with a facilitator typing, and the Markdown summary is the record you share. Reset Retrospective clears cards and notes, including the saved copy, but keeps the team list.

  • Three columns: What Went Well, What to Improve, Action Items
  • Card authors from a team list you build
  • Thumbs-up voting with cards sorted by votes
  • Additional Notes section
  • Markdown summary download
Read the guide: Standups, Retrospectives and Project Dashboards: Running the Scrum Ceremonies

Updated

How to use the Sprint Retrospective Board

  1. Enter the Team Name and Sprint Number. Click Add Member to add each person; the two placeholder members can stay for anonymous cards.
  2. In Add Retrospective Item, pick the Category and the Author, type the card text and click the plus button.
  3. Let the team vote with the thumbs-up button on each card. Cards reorder by votes within their column.
  4. Write follow-ups or context in Additional Notes, agree owners for the top Action Items, then click Download Summary to save the Markdown file.

Worked example

What the downloaded summary looks like

Input

Team: Payments, Sprint: 14
What Went Well: "CI under 8 minutes" (3 votes, Ana)
Action Items: "Add flaky-test owner rotation" (1 vote, Raj)

Output

# Payments Sprint 14 Retrospective - <date>

## What Went Well

- CI under 8 minutes (3 votes) - *Ana*

## Action Items

- Add flaky-test owner rotation (1 vote) - *Raj*

Columns with no cards are left out, cards are listed by vote count, and the file name is retrospective-YYYY-MM-DD.md. Paste it into a wiki page or the sprint ticket so next sprint's retro can check the action items.

Background and insight

The sprint retrospective is one of the five Scrum events. The Scrum Guide timeboxes it to a maximum of three hours for a one-month sprint, usually shorter for shorter sprints, and its purpose is to plan ways to increase quality and effectiveness. Norm Kerth's 2001 book Project Retrospectives gave the practice its Prime Directive: everyone did the best job they could, given what they knew at the time.

Teams rotate formats to stop retros going stale. Start / Stop / Continue, the 4Ls (Liked, Learned, Lacked, Longed for) and Mad / Sad / Glad are the common ones. This board has fixed columns rather than templates, but the formats map onto it: Continue and Glad go under What Went Well; Stop, Lacked and Mad under What to Improve; Start under Action Items. Prefixing a card with "Learned:" or "Longed for:" keeps the 4Ls distinction visible.

The most useful column is the last one. A retro that produces a long list of problems and no owned, specific action items tends to repeat next sprint. Two or three action items, each with a name and a date, beat ten vague intentions.

Common use cases

  • End-of-sprint retros

    Run the standard went well, improve and actions retro on a shared screen and leave with a Markdown record.

  • Project or incident look-backs

    Use the same columns after a launch or an incident to separate what worked from what to change.

  • Rotating retro formats

    Run Start / Stop / Continue or Mad / Sad / Glad by mapping each prompt to a column.

  • Small teams without a retro tool

    Get a structured board and a summary without accounts, licences or setup.

Tips and limitations

  • There is no real-time collaboration. One person types while the team talks, or people take turns at one machine.
  • Votes are unlimited and not tied to a person. For dot voting, agree a budget (say three votes each) and count aloud.
  • Cards and notes autosave to this browser only. Download the summary to share it or to keep it after you reset the board.
  • Reset Retrospective clears cards and notes, and their saved copy, immediately without a confirmation step.
  • Write action items as "who does what by when". The summary is only as useful as the actions in it.

Sources and further reading

  1. The Scrum Guide, Scrum Guides. The Sprint Retrospective and its three-hour maximum for a one-month sprint
  2. Project Retrospectives: A Handbook for Team Reviews, Dorset House Publishing. Norm Kerth's 2001 book
  3. The Prime Directive, Agile Retrospective Resource Wiki. The text of Kerth's Prime Directive

Frequently asked questions

What are the three columns in this retrospective board?

What Went Well, What to Improve and Action Items. It is the classic retro layout: celebrate what worked, name what did not, and agree specific changes. Other formats can be run by mapping their prompts onto these three columns.

Can I run a Start Stop Continue retrospective with this tool?

Yes, by mapping the prompts. Put Continue cards in What Went Well, Stop cards in What to Improve and Start cards in Action Items. There is no built-in template that renames the columns, so tell the team the mapping at the start.

How does voting work on retro cards?

Each card has a thumbs-up button that adds one vote per click. Votes are not limited per person and are not anonymous, so agree a rule such as three votes each. Cards are sorted by vote count inside each column and in the downloaded summary.

Can several people add cards at the same time?

No. The board runs in one browser tab with no server or sync. Use it on a shared screen with a facilitator typing, or collect cards in chat first and enter them together.

How long should a sprint retrospective take?

The Scrum Guide sets a maximum of three hours for a one-month sprint and says shorter sprints usually need less. Many teams with two-week sprints run 45 to 90 minutes, spending most of the time on the improve column and agreeing action items.

Is there an in-depth guide to the Sprint Retrospective Board?

Yes. “Standups, Retrospectives and Project Dashboards: Running the Scrum Ceremonies” covers the background, how it works, common pitfalls and worked examples. Read the full guide.