Which retrospective format should I use?

Start/Stop/Continue is action-oriented and good for mature teams. What Went Well/Delta is simple and works anywhere. Mad/Sad/Glad surfaces emotions and suits teams working through friction. Rotate formats occasionally so retros do not become rote.

Why is the action items section separate?

A retrospective without action items is just a vent. The separate section forces the team to convert observations into concrete, owned commitments with due dates. Without an owner and a date, action items quietly evaporate before the next sprint.

How long should a retrospective be?

For a two-week sprint, 45 to 60 minutes is typical. Spend most of it gathering and discussing, then reserve the last 10 to 15 minutes to agree on a small number of action items. Two or three real commitments beat a long list nobody acts on.

Who should facilitate the retrospective?

Rotate the facilitator so it does not always fall to the same person and everyone learns to run one. The facilitator keeps time, ensures quieter voices are heard, and steers the group from observations toward agreed actions rather than dominating the discussion.

How do we make sure action items actually happen?

Assign a single owner and a due date to each, keep the list short, and review last sprint's action items at the start of the next retro. Carrying unfinished actions forward visibly creates accountability and stops the team from repeating the same problems.

Sprint Retrospective Template Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Turn reflection into action, not a vent

A retrospective is the engine of continuous improvement, but only if it ends in commitments. Too many retros gather complaints and then dissolve with nothing changing. This builder gives you a clear format for gathering observations and a separate, deliberate action item section so every retro leaves the team with a short list of owned, dated changes.

How it works

You pick one of three classic formats. Start/Stop/Continue asks what to begin doing, what to quit, and what is working. What Went Well/Delta separates wins from things to change. Mad/Sad/Glad surfaces how the sprint felt, which can reveal friction the other formats miss. Selecting a format sets the column headers and the prompt under each, so the team knows exactly what to put where.

You can pre-fill columns with points you already know or leave them blank for a live session. The action items section is always present and separate: each item has a description, an owner, and a due date. The tool exports the whole thing as Markdown, with the columns laid out as sections and the action items as a table.

Tips and example

Run the gather phase silently first so people are not anchored by whoever speaks first, then discuss themes. In a Start/Stop/Continue retro you might land on: Start writing test plans before coding, Stop merging without a second review, Continue the new deploy checklist. Then convert the top one or two into action items — “Add test-plan step to the PR template, owner Sam, due Friday” — and review them next time.