Start Stop Continue Retrospective

A simple, action-focused format that helps teams identify what to start doing, what to stop doing, and what is already working well.

What Is the Start Stop Continue Format?

Start Stop Continue (also called SSC) is one of the most widely used retrospective formats in Agile teams. Its power comes from its simplicity: three columns, three clear questions, and a direct path to actionable outcomes.

▶️

Start

New practices, habits, or behaviors the team should begin. Things the team isn't doing yet that could improve the next sprint.

⏹️

Stop

Practices or behaviors that are not helping — or actively causing harm. Things the team should stop doing to improve flow, quality, or morale.

Continue

Things that are working well and should be kept. Behaviors and practices worth protecting as the team moves forward.

Example Cards

Here is what a Start Stop Continue board might look like after a typical software sprint:

▶ Start
Pair programming on complex stories
Writing acceptance criteria before picking up tickets
More sprint refinement sessions
Automated regression tests for new features
⏹ Stop
Last-minute deployments on Fridays
Scope changes mid-sprint without discussion
Skipping PR reviews under time pressure
Carrying over the same blocker sprint after sprint
✅ Continue
Daily standups — they keep us aligned
Sprint demo with stakeholders
Team knowledge-sharing sessions
Rotating the facilitator role

Benefits of Start Stop Continue

  • Immediately actionable — every category maps directly to behaviors and decisions
  • Easy to understand — no special facilitation knowledge required
  • Balanced feedback — the three columns naturally produce both positive and improvement-focused input
  • Works well for remote teams — cards can be submitted before verbal discussion begins
  • Scales to any team size

Best Situations to Use This Format

  • New Agile teams running their first few retrospectives
  • Teams that have gotten into bad habits and need a reset
  • After a particularly chaotic or process-heavy sprint
  • When the team wants clarity on what to change going forward
  • As a default format when the team isn't sure what else to try

Tips for a Successful Session

  • Give everyone 5–10 minutes to write cards silently before revealing them
  • Use anonymous submissions to ensure honest feedback
  • Cluster similar cards and vote on the most important topics
  • Commit to one or two concrete actions from the Stop column — not ten
  • Open the next retro by reviewing last sprint's commitments
💡 Comparing templates? If your team wants more nuance than three columns, consider the Starfish format, which adds "More Of" and "Less Of" for finer-grained feedback. You can also use BugNBrag's custom column feature — the Scrum Master can add any column to fit your team's specific needs.

Try Start Stop Continue with your team

Create a free BugNBrag session and select the Start Stop Continue template.

🚀 Create Free Session
An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.