A structured retrospective format to identify practices to start, stop, and continue for the next sprint.
Adjust the columns and settings before you start.
Find the right fit
Use this format when you want to gather focused feedback on team practices, behaviors, and processes after a sprint.
Do not use this format if the team is still facing major issues or conflicts that need to be addressed separately.
Use these prompts to collect specific observations. One idea per note keeps the discussion easy to follow.
What new practices should we try next sprint?
What is taking up time or hindering results?
What is working well and should be maintained?
A suggested flow for this board. Reserve time at the end to agree on what happens next.
Explain the purpose of the retrospective and how the Start, Stop, Continue format works.
Facilitate a brainstorming session for each column. Encourage team members to share their thoughts about what to start, stop, and continue.
Group similar items and allow team members to vote on the most important items in each column.
For the top voted items, define specific action items that the team will implement in the next sprint.
Review the action items and ask team members to reflect on the session. Confirm roles for any experiments.
Facilitator’s example
Team members feel overwhelmed by current processes and unclear on priorities.
Assign one team member to streamline the code review process by implementing a checklist. Evaluate the effectiveness by measuring the average code review time after the next sprint.
Openly discuss the disagreement and try to find common ground. If needed, vote on the item to reach a conclusion.
Assign specific owners to each action item and review progress in the next retrospective.
This format is best for small to medium teams; for larger teams, consider breaking into smaller groups.
Focus on the top 3-5 items per column to avoid overwhelming the team.