Start Stop Continue Retrospective Template

Decide what to start, stop, and keep doing next sprint. Try the live demo, then use this three-column board to turn team feedback into one or two owned improvements.

30–45 min3–10 people3 columns

Adjust the columns and settings before you start.

Created by Alexandr Voloshyn
OfficialRecommended

Find the right fit

When to use it

Start Stop Continue is a retrospective format with three questions: what should we try, what should we stop, and what already works? Use it after a sprint when the team needs practical changes to its day-to-day work. Start with Continue to protect useful habits, then discuss Stop and Start. The example below follows one team whose pull requests waited too long for review.

When to choose another format

If a production incident needs a timeline and evidence, use an incident review first. If people feel unsafe speaking openly, agree on how feedback will be handled before asking for cards. Three columns cannot resolve a conflict on their own.

Questions that guide the conversation

Use these prompts to collect specific observations. One idea per note keeps the discussion easy to follow.

Start

What new habit could make the next sprint easier? Propose something small enough to try.

Example cards

  • Rotate a review buddy so every pull request has a first reviewer.
  • Ask QA to review acceptance criteria before we start a story.
  • Reserve ten minutes after stand-up to unblock waiting reviews.

Stop

What should we stop doing because it adds delay or friction? Describe the behavior, not the person.

Example cards

  • Stop leaving review requests in chat without an assigned reviewer.
  • Stop starting another story while an almost-finished one waits for review.
  • Stop adding late scope without agreeing what leaves the sprint.

Continue

What helped this sprint and deserves to stay? Name a useful habit and its effect.

Example cards

  • Keep small pull requests: they made review discussions clearer.
  • Keep the short end-of-sprint demo that helped QA spot edge cases.
  • Keep pairing on risky changes before opening a pull request.
Start Stop Continue demo board with sample feedback in three columns.
Illustrative demo: the cards describe review delays and habits the team wants to protect. These are sample data, not customer results.

From reflection to a next step

30–45 min

A suggested flow for this board. Reserve time at the end to agree on what happens next.

  1. 1

    Set a shared focus 5 min

    Agree on the sprint and the question: what made delivery easier or harder? Explain the three columns and keep feedback about work, not personalities.

  2. 2

    Write before discussing 10 min

    Give everyone quiet time to add observations. One idea per card; nobody has to fill every column. Use concrete examples instead of “communicate better.”

  3. 3

    Group signals and choose a discussion 10 min

    Read the cards, clarify meaning and group related observations. Each participant has three votes across the whole board. Votes choose discussion priorities; they do not decide who is right.

  4. 4

    Agree on one or two experiments 10 min

    Discuss the strongest signal and choose a change the team can control. Create an action item with an owner. Describe what will be tried and what the team will look at next sprint.

  5. 5

    Close the loop 5 min

    Read the actions back to the team and agree when to review them. Start the next retrospective by checking what happened before adding new improvements.

Read the complete retrospective facilitation guide

Facilitator’s example

Make the next step small enough to happen

A specific observation

“Three pull requests waited more than a day for their first review. We started more work while those stories stayed unfinished.”

A clear experiment

“For the next sprint, Maya coordinates a rotating review buddy. Each pull request gets a first reviewer that day. At the next retrospective, we compare the number of reviews that waited more than a day.”

An action item in the demo with an owner and the review-buddy experiment.
Turn a discussion into an owned experiment. At the next retrospective, review what changed before choosing another improvement.
Explore retrospective action item examples and follow-up

Make the conversation useful

  • Start with Continue so a good habit is not lost while discussing problems.
  • Ask “What happened?” before “What should we change?” A solution is easier to choose when the observation is clear.
  • Protect time for action items. A full board is useful only if the team can explain what happens next.

Before you start

Are Start Stop Continue and Stop Start Continue different?

They use the same three categories. You can change the discussion order without changing the method. Starting with Continue can make it easier to name what the team wants to protect.

What if people disagree about a card?

Ask for examples and let both people explain what they observed. Separate facts from assumptions. Use votes to choose a topic to discuss, not to declare one person right. Agree on a small experiment if the cause is still uncertain.

How many actions should we leave with?

Choose one or two across the whole board. Give each an owner and a review point. Keep other ideas visible for later instead of promising more changes than the team can carry out.

How can I try this template?

Open the live demo to explore a sample board. Use Create to prepare your own retrospective with this template’s columns and settings. You can adjust them before creating the meeting.

More retrospective templates

All templates
OfficialRecommended
Sprint reflection
45–45 min

What Went Well Retrospective

NamedAction items3 votes
8 uses 52 retros
UsePreview
OfficialRecommended
Sprint reflection
45–60 min

4Ls Retrospective

NamedAction items3 votes
2 uses 2 retros
UsePreview
OfficialRecommended
Sprint reflection
45–45 min

Rose, Bud, Thorn Retrospective

NamedAction items3 votes
2 uses 2 retros
UsePreview