Running the same retrospective every two weeks quickly becomes stale. Switching up the format keeps conversations fresh, surfaces different insights, and prevents the ceremony from turning into a routine checklist. Below are four lightweight structures you can rotate, plus practical tips for making each retro actionable.
Start / Stop / Continue
The default format asks the team what to start doing, stop doing, and continue doing. Its strength lies in simplicity: anyone can jump in without a steep learning curve, making it ideal for brand‑new squads or when you need a quick pulse check. Because the questions are the same each sprint, patterns emerge quickly, but after a few cycles the discussion can feel predictable and may miss deeper emotions or systemic issues.
4Ls (Liked, Learned, Lacked, Longed for)
This variant expands the conversation to four lenses: what the team liked, what they learned, what they lacked, and what they longed for. By explicitly naming “lacked” and “longed for,” the retro surfaces emotional signals and unmet needs that a pure action‑item list might hide. It works well after a particularly hard sprint when fatigue or frustration is high, giving space to name the difficulties before jumping to solutions.
Sailboat (Wind, Anchors, Rocks, Island)
Using a visual metaphor, the sailboat format maps out what pushes the team forward (wind), what holds it back (anchors), hidden risks (rocks), and the ultimate goal (island). Teams that think visually or enjoy collaborative whiteboards—physical or virtual—find this structure engaging. The metaphor encourages participants to think in terms of forces rather than isolated tasks, often revealing systemic blockers that aren’t obvious in a plain list.
Mad / Sad / Glad
An emotion‑first framing, this format asks participants to share what made them mad, sad, or glad during the sprint. By putting feelings front and center, the retro captures morale directly, which is especially valuable after a release or a crunch period. The emotional data can then be translated into concrete actions, such as improving communication channels or celebrating successes more visibly.
Do / Avoid
Do
- Rotate formats every few sprints to avoid fatigue and keep perspectives fresh.
- Convert every identified action item into a backlog ticket or a clear owner, so the retro produces tangible work.
- Review the previous retro’s action items at the start of the new session to close the loop and demonstrate accountability.
Avoid
- Running the same format indefinitely; repetition dulls engagement.
- Letting the retro devolve into a complaint session without committing to follow‑up actions.
- Skipping the retro when the sprint went well; wins also need to be examined and reinforced.
Keep the retrospective dynamic, turn insights into work, and the ceremony will remain a catalyst for continuous improvement.
Top comments (0)