Column 1
Start
What new behavior or practice would help the team?
Example cards
- Start refining risky stories before sprint planning.
- Start pairing on unfamiliar services.
- Start checking action items at stand-up once a week.
Start Stop Continue turns reflection into three direct choices. It works best when a team already understands the situation and needs clear decisions about behaviors, meetings, or delivery practices.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
Column 1
What new behavior or practice would help the team?
Example cards
Column 2
What creates waste, confusion, or avoidable friction?
Example cards
Column 3
What is already valuable and should be protected?
Example cards
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint or project being reviewed, restate the purpose of each column, and remind everyone to describe observable events.
Give everyone uninterrupted time to add one specific observation per card across every column.
Read the cards column by column and let authors add context without debating solutions yet.
Combine cards that describe the same pattern, then vote for the themes that would most improve the next iteration.
Explore causes, consequences, and tradeoffs behind the highest-voted themes while making space for dissenting evidence.
Turn the strongest insight into a small action with an owner, deadline, and signal the team can review next time.
Let each participant choose one personal working habit before selecting a team action.
Focus every card on recurring meetings, attendance, preparation, and decisions.
Scope prompts to discovery, handoffs, quality checks, and release flow.
Before the retro
Use a quick, low-pressure choice round before the retrospective begins.
It is a three-column retrospective that asks which practices the team should begin, remove, and preserve in the next iteration.
Good cards describe controllable behavior, such as starting early risk reviews, stopping mid-sprint scope changes, or continuing small pull requests.
Choose one or two changes with clear owners. A long action list usually weakens follow-through.
Allow 30–40 minutes for a team of three to twelve, including silent writing, voting, discussion, and action selection.
Open the ready-made columns, invite the team, collect observations, vote, and leave with an owned improvement.