Timeboxing sprint planning: give every decision a clock

12 October 2026 · Updated 16 October 2026 · 7 min read

Every planning meeting has the same quiet villain: the story that "just needs five more minutes". Then ten. Then it's the last half hour and the remaining stories get a shrug and a guess. Timeboxing is the cure, and it's simpler than it sounds: decide how long each part of planning is worth before you start, and let a clock keep you honest. This guide shows how to give every decision its own clock, with a minute-by-minute budget you can borrow.

Fixed time, flexible scope

A timebox is a fixed slot of time for a piece of work. When it ends, you stop, whatever state the work is in. The trick is what you let flex. In an untimed meeting the time stretches to fit the discussion. In a timeboxed one the time is fixed and the outcome adapts: you decide with what you know, break the problem down or set it aside.

You already use timeboxes. The sprint itself is one, and the Scrum Guide caps sprint planning at a maximum of eight hours for a one-month sprint, and less for shorter ones. This article is about the layer inside that: the minutes within the meeting.

A timebox is not a deadline to be afraid of. It's a budget. Work expands to fill the time available, so the box gives the discussion a shape and gives the quiet people a reason to speak sooner.

Three clocks, three jobs

A planning meeting runs best with three nested clocks:

• The meeting clock. The whole session has a start and a hard stop, split into phases: goal, capacity, estimating, commitment. Each phase has its own budget.
• The story clock. Each story gets a few minutes in total, from "read it out" to "estimate saved". Three to four minutes is a good default for a story that has been refined.
• The vote clock. The smallest box: the time people have to pick a card. Thirty seconds to a minute is plenty for a story everyone has just heard. A short clock also stops people from watching each other's hands.

The discussion clock is the one most teams skip, and it's the cheapest to automate. In Storyvote the host or a facilitator starts a discussion timer from the room's top bar, up to an hour. The time left shows for everyone, and a minute can be added, or the clock restarted or cancelled, without leaving the round.

A minute budget for a ninety-minute planning

Here's a budget for a five-person team planning a two-week sprint in ninety minutes. Adjust it, but write it down, on the board or in the first line of the meeting invite:

Notice the buffer. A budget with no slack turns every overrun into an emergency. Five minutes at the end is cheaper than ten minutes of stress in the middle.

Inside a four-minute story

The story clock, spent well, looks like this:

1. 30 seconds: the owner reads the story and its acceptance criteria.
2. 30 seconds: one round of clarifying questions, no solutions.
3. 30 seconds: everyone votes in private on the vote clock.
4. 10 seconds: read the reveal. Is it a clean sweep, near neighbours or a real split? The shapes of a reveal tell you what to do next.
5. Up to 2 minutes: extremes explain, then one revote if needed.
6. The rest: save it, say the number, next story.

Most stories finish in far less. That's where the time for the hard ones comes from.

When the clock rings: the three exits

A timebox only works if it ends something. When a story's time is up and you still disagree, there are exactly three honest exits:

• Decide with what you have. Take the larger estimate, note the biggest risk next to it and move on. An estimate with a visible risk is more useful than a perfect one that cost ten minutes.
• Split it. If two groups are imagining different work, you have two stories. Cut it, and estimate the halves in the next slots.
• Park it. If the missing piece is information, write the question, name an owner and put the story back on the backlog. Parked is a decision, not a failure.

The one thing you shouldn't do is quietly extend. If the room truly needs more time, grant one visible extension, a minute or two, said out loud, once per story. It keeps the box real while leaving room for the story that's one answer away from done.

Who holds the clock

A timebox needs a keeper, or it's just a suggestion. The facilitator usually does it, but the job rotates well: a different teammate each sprint, with the right to say "that's time" kindly and without apology. A rotating timekeeper also spreads the habit, so the team stops relying on one person to be the bad guy.

In Storyvote, the facilitator role can be given to more than one person, and facilitators can run the round: select the story, reveal, clear votes, run the discussion timer and save the estimate. The timekeeper doesn't have to be the host.

Four ways timeboxes go wrong

• Boxing quality instead of effort. A clock is for discussion, not for how carefully the team should think. If a story needs more thought than four minutes, that's a sign it wasn't refined, so park it rather than rush it.
• Clocks as pressure. A timer that makes people feel hurried gets shorter, shallower answers. Introduce it as a tool that protects everyone's time, and let the team choose the lengths.
• Same box for every story. A one-line fix and a risky integration don't need the same minutes. Start from the default and let the team say "this one's a ten".
• No review. Boxes are guesses at first. Without a look back they stay wrong.

Tune the boxes in the retro

After each planning, spend two minutes on three questions: which phase overran, which story blew its box and why, and did anyone feel unheard? If estimating always runs over, you may be bringing unrefined stories, or the box is simply too small. If you always finish early, give the time to the capacity check or to the stories at the bottom of the list. Within three or four sprints the budget stops being a guess and becomes a fit for your team.

Try it in Storyvote

Storyvote is free planning poker with a discussion timer built in: start it from the top bar and everyone sees the time left. Votes stay hidden until the reveal, so nobody anchors on the first number either. Nobody needs an account, so a teammate can join from the link.

Planning the whole meeting? Read how to plan a sprint your team can finish.

← All articles