Sprint Retrospective Template

Liked captures what genuinely worked and should happen again, stated specifically rather than as a vague good vibes note. Learned captures new information the team picked up during the sprint, about the product, the process, or a teammate's way of working. Lacked names what was missing, a tool, a piece of information, or an earlier conversation that would have prevented friction. Longed for names what the team wishes existed but does not yet, distinct from Lacked because it points forward rather than describing a gap in what already existed.

An example board entry from a sprint that shipped a delayed feature: Liked, the mid sprint check in caught a scope misunderstanding two days early instead of at demo. Learned, the design handoff format the team tried this sprint saved real review time. Lacked, nobody flagged the third party API's rate limit until integration testing, which cost two days. Longed for, a shared checklist of external dependencies to verify before sprint planning, not after.

Use the 4Ls format specifically when a team's retrospectives have gone stale on Start, Stop, Continue, since the two formats surface different things: Start Stop Continue pushes toward immediate action items, while 4Ls makes room for learning and unmet wishes that do not yet have a clear fix attached. Rotate between formats every few sprints rather than defaulting to one permanently, so the reflection habit itself does not become routine enough to tune out.

Fill in each quadrant as a live group exercise, with individual silent writing first before group discussion, which surfaces more honest input than an open floor discussion where the first person to speak anchors everyone else. Convert at least one item from Lacked or Longed for into a concrete action with an owner before the retrospective ends; a board full of honest reflection that produces zero committed changes has the same effect on team trust as skipping the retrospective entirely.

The most common mistake is filling in all four quadrants and adjourning without picking any action item, which teaches the team that retrospectives are a venting ritual rather than a mechanism that changes how the next sprint runs. A second common mistake is letting the same unresolved item appear in Lacked sprint after sprint with no one ever owning a fix, which is a clearer signal about team dynamics than the retrospective format itself.

Builders Camp's Project Management for Product bootcamp covers this ritual as part of planning, dependencies, communication, and risk management for product delivery. The template lives in the Builders Camp templates library, included in every Membership alongside the sprint planning template and the rest of the catalog.