4Ls
45 min- Liked
- Learned
- Lacked
- Longed For
Best for: Releases, project phases, mixed-role groups
10 formats
A sprint retro looks at the last two weeks. These formats look at a whole release, project phase, quarter or year, when there's more to remember and more people involved. Most have four or five columns, take 45 to 60 minutes, and work best when notes go on the board long before the meeting.
Best for: Releases, project phases, mixed-role groups
Best for: Seeing what drives and drags the team
Best for: Long goals with a clear end point
Best for: The end of a project phase
Best for: Long sprints where memories blur
Best for: Stepping back from sprint-level detail
Best for: The end of an OKR cycle
Best for: Right after shipping a release
Best for: Closing out a project, win or lose
Best for: The last retro of the year
Ask what you're closing.
Nobody remembers week two of a three-month project on the day of the retro. Open the board when the phase starts, not when it ends, and ask people to add a note whenever something goes notably well or badly. In Retro Rabbit the board stays open until you start the review, and notes can go in from the board itself or the Team Room's Quick Notes box.
Before the meeting, gather what people will need: the original goals, release notes, incident links and the dates of big decisions. Then the meeting can go to causes and lessons instead of piecing together what happened.
Big retros produce long lists. Pick two or three action items with owners and let the rest go. Unfinished items stay visible in later retros in the same Team Room, under Old / Unresolved Items. On Pro AI (and during the free trial), CarrotIQ's Sprint Summary gives you a written summary of each column to share with people who weren't there. For running the meeting itself, see the complete guide to sprint retrospectives.
A sprint retro covers one or two weeks and usually leads to small process changes. A project retro covers months, involves more roles and produces lessons for the next project, so it needs more time and notes collected along the way.
Plan 45 to 60 minutes for a group of up to about ten people. For bigger groups, collect notes and votes async first and spend the meeting only on the top-voted themes.
Invite them to a Release Retro or Project Post-Mortem when their decisions shaped the outcome. Keep it team-only when you need people to talk openly about how they worked together.
Try any of these with your team
Your team adds notes during the sprint, CarrotIQ groups and summarizes them and suggests action items, and unfinished items carry into the next retro.
14-day free trial ยท No credit card