Good / Bad / Improve retrospective template

The simplest retrospective format: what went well, what didn't, and what to change next sprint.

Start a Good / Bad / Improve retroFree. No account needed. Share the link and your team joins.

The columns and what to ask

  • Good

    What went well this sprint? What should we make sure we keep doing?

  • Bad

    What slowed us down or frustrated us? Where did we lose time?

  • Improve

    What is one concrete change we could try next sprint?

Best for

  • Teams running their first retrospectives
  • A dependable default when nothing special happened
  • Short sessions of 30 to 45 minutes

Skip it when

  • The team has run it for months and the same points keep coming back. Switch format to change the conversation.
  • The sprint was emotionally heavy. A format that names feelings will surface more (see Mad / Sad / Glad).

How to run it in 45 minutes

Sized for a team of up to eight. Add time for larger groups.

  1. 1

    Set the stage · 5 min

    Restate the sprint goal and remind everyone the retro is about the process, not people. Agree that cards stay anonymous until the discussion.

  2. 2

    Write cards · 10 min

    Everyone adds cards to all three columns silently and at the same time.

  3. 3

    Group and vote · 10 min

    Merge duplicates, then give each person five votes to spend on the topics they most want to discuss.

  4. 4

    Discuss · 15 min

    Work through the top-voted cards, timeboxing each one. For every Bad, ask what would make it better and write that in Improve.

  5. 5

    Commit to actions · 5 min

    Pick at most two improvements, give each an owner and a date, and read them back.

Facilitation tips

  • Write cards silently first. Talking before writing lets the loudest voice frame the whole sprint.
  • Turn every Bad card into an Improve card or let it go. A complaint without an action is just venting.
  • Cap actions at two. Teams that commit to six change nothing.
  • Open the next retro by checking last time's actions before anything else.

Questions

How long should a Good / Bad / Improve retro take?
Thirty to forty-five minutes for a team of up to eight people. Larger groups need more time to discuss, so split into smaller discussion groups after voting.
Who should run it?
Anyone on the team can facilitate. Rotating the facilitator each sprint keeps the format fresh and shares the load.

Run it with your team now

Your board opens with these columns. Votes, timers and anonymous cards are built in.

Start a Good / Bad / Improve retro

See all 6 templates