Retrospective Timer
Every retrospective facilitator knows the failure mode: 30 minutes of enthusiastic venting, then two minutes to decide what to actually change. A retrospective timer protects the phase that matters most — deciding — by giving every phase of the retro its own timebox.
This free sprint retro timer ships with the classic five-phase structure from Derby and Larsen's "Agile Retrospectives", sized for a 45-minute session.
The 45-minute retro agenda, timeboxed
| Agenda item | Timebox |
|---|---|
| Set stage | 5 min |
| Gather data | 10 min |
| Insights | 10 min |
| Decide | 15 min |
| Close | 5 min |
| Total | 45 min |
How to run a timed retrospective
Put the countdown where everyone can see it and say what it's for: "we keep 15 minutes for deciding, so everything before it has a clock." Teams accept firm timeboxes readily when the reason is protecting their own action items.
Auto-advance changes the facilitator's job. Instead of being the person who interrupts a good discussion, you let the timer end the phase and offer a trade: "we can stay on this topic, but it costs us Decide time — do we want that?" Sometimes the answer is yes, and that's fine; now it's the team's explicit choice instead of drift.
Timeboxing tips for retrospectives
- Never let Gather data borrow time from Decide — venting feels productive but changes nothing.
- One or two action items with owners beat five without. The Decide timebox is for narrowing down, not collecting.
- Start the next retro by checking last retro's actions during Set stage.
- Vary the format between retros, keep the timeboxes — structure prevents staleness better than length does.
Frequently Asked Questions
How long should each retrospective phase take?▼
A common split for 45 minutes is: 5 for setting the stage, 10 for gathering data, 10 for insights, 15 for deciding, 5 for closing — deciding deliberately gets the largest share. This template uses exactly that split, and every duration is editable.
How long should a sprint retrospective be overall?▼
45 minutes to an hour for a one- or two-week sprint is typical. Longer sprints or heated topics justify more, but a longer retro without protected Decide time just produces more discussion, not more change.
What if a discussion is too valuable to cut off?▼
Make the trade explicit: pause, tell the team what staying on the topic costs, and let them choose. The timer's job is to make time visible so those trade-offs are conscious decisions.
Free, no signup — opens the meeting agenda timer with this template loaded. Edit anything before you start.