All methods

Typical duration:
25m

Purpose

The Timeline Retrospective maps the sprint or project chronologically, allowing teams to reconstruct what happened, when it happened, and how it felt at each stage. By plotting events, moods, and milestones on a shared timeline, teams identify cause-and-effect relationships, turning points, and recurring patterns that other formats miss.

At a glance

  • Group size: 3–12 people
  • Duration: 25 minutes
  • Difficulty: Intermediate
  • Facilitation style: Structured
  • Setting: Both / Remote-friendly

How to run

  1. Draw a horizontal timeline on a board spanning the sprint/project period.
  2. Silent recall: each participant writes events, milestones, and feelings on sticky notes and places them chronologically (5 minutes).
  3. Walk through the timeline together, adding context and filling gaps (8 minutes).
  4. Mark high points and low points; discuss what caused each (7 minutes).
  5. Identify 1–2 patterns or turning points and define improvement actions (5 minutes).

Materials needed

  • Long whiteboard or paper roll
  • Sticky notes (two colours: events and feelings)
  • Markers
  • Timer

Pitfalls & common mistakes

  • Rushing through the timeline without pausing at critical moments.
  • Only recording facts without capturing emotions — the mood layer is essential.
  • Not connecting timeline insights to actionable changes.

Inclusion & accessibility

  • New team members may not know all events — pair them with veterans.
  • Allow digital contributions for remote participants using a shared board.
  • Use icons (thumbs up, thumbs down) alongside text for quick mood indication.

Variations

  • Mood Timeline: overlay a mood curve (happy to sad) on the event timeline.
  • Data Timeline: add metrics (velocity, bug count) to correlate events with outcomes.
  • Personal Timelines: each person draws their own timeline first, then merge.

When NOT to use this

  • When the sprint was very short and uneventful — a simpler format like Plus/Delta suffices.
  • When the team needs a forward-looking exercise rather than a historical review.

Source & further reading

  • Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen.
  • Retromat (retromat.org).

Turn the building blocks into an agenda

Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.

Try it free for 14 days
· GoodWorkshop