Retrospective Board

Run Start / Stop / Continue retrospectives and mark outcomes as action items.

Retrospective Board

5:00
min

start

0

No items yet...

stop

0

No items yet...

continue

0

No items yet...

Tip: Mark items as Action to denote action items for follow-up.

Running Effective Retrospectives

What is a Retrospective?

A retrospective (or "retro") is a structured meeting where teams reflect on recent work to identify improvements. Originating from Agile and Scrum methodologies, retrospectives embody the principle of continuous improvement—the idea that teams should regularly examine their processes and behaviors to become more effective over time. While common in software development, retrospectives benefit any team doing iterative work.

The Start/Stop/Continue Framework

This simple yet powerful framework organizes feedback into three actionable categories:

Start

New practices to adopt. What should we begin doing that we aren't doing now? New tools, processes, or behaviors to experiment with.

Stop

Practices to eliminate. What's not working? What wastes time or causes frustration? Be specific about what to discontinue.

Continue

What's working well. Celebrate successes and reinforce positive behaviors. These often get overlooked but are crucial for morale.

How to Run a Great Retrospective

  1. Set the stage (5 min): Welcome everyone, state the retro's purpose, and remind the team that this is a safe space for honest feedback.
  2. Gather data (10-15 min): Have each participant silently add items to Start, Stop, and Continue categories. Use timers to keep pace.
  3. Group and discuss (15-20 min): Cluster similar items, then discuss each cluster. Focus on understanding, not defending.
  4. Vote on priorities (5 min): Each person gets 3 votes to identify the most impactful items to address.
  5. Define action items (10 min): For top-voted items, create specific, assignable action items with owners and due dates.
  6. Close the loop: At the next retro, review action items from last time. Did we follow through? What was the impact?

Creating Psychological Safety

The effectiveness of a retrospective depends entirely on whether team members feel safe being honest. Without psychological safety, people will share only surface-level observations. To foster openness: establish that retros are blame-free zones, have leaders speak last (to avoid anchoring), consider anonymous input for sensitive topics, and always follow through on action items to show that feedback matters.

Alternative Retrospective Formats

Mad/Sad/Glad: Focus on emotions. What made you mad, sad, or glad this sprint? Great for surfacing team morale issues.
Sailboat: Visualize wind (what propels us), anchors (what holds us back), rocks (risks ahead), and the island (our goal).
4 Ls: Liked, Learned, Lacked, Longed For. Emphasizes learning and aspiration alongside critique.
Rose, Bud, Thorn: Highlights (roses), potential (buds), and challenges (thorns). Good for growth-focused teams.

Frequently Asked Questions

What is a sprint retrospective?
A sprint retrospective is an agile ceremony held at the end of each sprint (typically every 1–4 weeks) where the team reflects on what went well, what didn't, and what to improve. It's one of the five Scrum events and is considered the most important for continuous improvement. The output is a small set of actionable improvements the team commits to implementing in the next sprint.
What is the Start/Stop/Continue framework?
Start/Stop/Continue is a simple retrospective format where team members share: things the team should Start doing (new practices), Stop doing (counterproductive habits), and Continue doing (working well). Its simplicity makes it ideal for teams new to retrospectives or when time is limited. For more nuanced discussions, teams may graduate to formats like Mad/Sad/Glad, 4Ls (Liked, Learned, Lacked, Longed For), or Sailboat retrospectives.
How long should a retrospective take?
For a 2-week sprint, allocate 60–90 minutes. For 1-week sprints, 30–45 minutes is sufficient. The meeting should include: setting the stage (5 min), gathering data (15–20 min), generating insights (15–20 min), deciding on actions (10–15 min), and closing (5 min). Keep the focus on 1–3 actionable improvements rather than trying to solve everything at once.
How do I make retrospectives feel safe for the team?
Psychological safety is essential. Establish ground rules: use 'we' language instead of 'you' (blame-free), apply the Prime Directive ('Everyone did the best job they could given what they knew'), keep discussions confidential, and separate retrospectives from performance reviews. Anonymous input (like this tool provides) helps quieter team members share honest feedback without fear of judgment.
What if the same issues keep coming up in retrospectives?
Recurring issues signal a systemic problem. First, check if previous action items were actually implemented—many teams generate great ideas but fail to follow through. Assign a specific owner and deadline to each action item. If an issue persists despite attempts to fix it, escalate it: the problem may be organizational (resource constraints, unclear priorities) rather than team-level, requiring management involvement.

Further Reading on Running Great Retros

Designing Retrospectives That Lead to Change

A practical framework for running retrospectives that result in meaningful, tracked improvements.

From Blame to Insight

How to design prompts and norms that encourage honest reflection without finger-pointing.

Turning Discussion into Action

Techniques to convert retro observations into measurable tasks and make follow-through automatic.

Data-Informed Retrospectives

What metrics help retrospectives, and how to bring data in a way that complements team reflection.

Time & Structure for Short Retros

Practical formats to keep retros compact, inclusive, and action-oriented even with limited time.