DEV Community

keyur shah
keyur shah

Posted on

Retro Formats Beyond Start/Stop/Continue

Running the same retrospective every two weeks quickly becomes stale. Switching up the format keeps conversations fresh, surfaces different insights, and helps the team stay engaged.

Start / Stop / Continue

The default format asks team members what they should start doing, stop doing, and continue doing. It’s straightforward, low‑effort, and works well for newly formed teams that need a clear, simple structure. After a few sprints the pattern can feel predictable, and deeper issues may stay hidden.

4Ls (Liked, Learned, Lacked, Longed for)

This four‑column approach adds an emotional dimension: what the team liked, what it learned, what it lacked, and what it longed for. It surfaces feelings that pure action items miss, making it useful after a particularly hard sprint when frustration or fatigue may be present. The “Lacked” and “Longed for” columns help surface resource or process gaps that might otherwise be ignored.

Sailboat (Wind, Anchors, Rocks, Island)

A visual metaphor maps the team’s situation onto a sailboat: wind pushes forward, anchors hold back, rocks represent hidden risks, and the island is the sprint goal. Teams that think visually appreciate the tangible layout, whether on a physical whiteboard or a virtual canvas. The format encourages discussion of both positive forces and hidden impediments in a single view.

Mad / Sad / Glad

An emotion‑first framing asks participants to share what made them mad, sad, or glad during the sprint. This format is especially effective after a release or a period of crunch, capturing the team’s morale directly. By naming emotions first, the conversation can transition naturally into actionable improvements.

Do / Avoid

Do

  • Rotate formats every few sprints to avoid fatigue.
  • Turn every action item into a backlog ticket or a tracked item, not just a note.
  • Review the previous retro’s action items before starting a new session.

Avoid

  • Running the same format indefinitely.
  • Letting the retro turn into a complaint session with no concrete actions.
  • Skipping retros when the sprint went well; successes also need reflection.

Keep the retrospective dynamic, and the team will continuously uncover new opportunities for growth.


Book a call

Top comments (0)