Retro Rabbit

10 formats

Project Retrospective Templates

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.

  • Mountain Climber

    45 min
    • Base camp: where we are now
    • What helps us climb
    • Obstacles on the way
    • Gear we're missing
    • The summit we're aiming for

    Best for: Long goals with a clear end point

  • FLAP

    45 min
    • Future considerations
    • Lessons learned
    • Accomplishments
    • Problem areas

    Best for: The end of a project phase

  • Quarterly Retrospective

    60 min
    • Wins this quarter
    • What was hard
    • What we learned
    • Focus for next quarter

    Best for: Stepping back from sprint-level detail

  • OKR Review

    60 min
    • Key results we hit
    • Key results we missed
    • Why
    • What we change next cycle

    Best for: The end of an OKR cycle

  • Release Retro

    45 min
    • What went smoothly
    • What broke or slipped
    • What we missed before release
    • What to change for next release

    Best for: Right after shipping a release

  • Project Post-Mortem

    60 min
    • Goals vs. what we delivered
    • What went well
    • What didn't go well
    • Root causes
    • Lessons for next time

    Best for: Closing out a project, win or lose

  • End of Year

    60 min
    • Highlights of the year
    • Hardest moments
    • What we learned
    • Thank-yous
    • Hopes for next year

    Best for: The last retro of the year

How to choose

Ask what you're closing.

  • A release. Run the Release Retro within a week of shipping, while details are fresh. Its "What we missed before release" column is where testing and rollout gaps show up.
  • A project phase, with more to come. FLAP pairs accomplishments and lessons with future considerations, so the next phase starts with a list. 4Ls is simpler and more reflective, and works well when engineers, designers and product people sit in the same retro.
  • A whole project, win or lose. The Project Post-Mortem starts with goals against what you delivered, then digs into root causes. Use it when people outside the team will read the outcome.
  • A long stretch where memories blur. The Timeline sorts notes into early, middle and end, so the last week doesn't crowd out everything before it.
  • A quarter or an OKR cycle. The Quarterly Retrospective steps back from sprint detail. The OKR Review is narrower: it asks why each key result was hit or missed.
  • A goal still in progress. Hot Air Balloon and Mountain Climber look back and forward at once. Mountain Climber suits a goal with a clear end point, such as a migration with a cutover date.
  • The year. End of Year adds thank-yous and hopes for next year. Use it for the last retro before the holidays.

Collecting notes over a long period

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.

Frequently asked questions

What's the difference between a sprint retrospective and a project retrospective?

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.

How long should a project retrospective take?

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.

Should stakeholders join a project retrospective?

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.

More formats by goal

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