Timebox
What is a Timebox?
A timebox is a fixed time limit set for an activity, at the end of which the activity stops and scope, not time, is what gives. Scrum sprints and events are timeboxed, as are Pomodoro Technique work sessions.
Updated November 2026 · 2 min read
A timebox is a fixed, maximum amount of time allocated to an activity, after which the activity stops, whether or not everything planned has been finished. Instead of asking "how long will this take?", timeboxing asks "what is the best we can do in this amount of time?" Scope adjusts to fit the time, not the other way around.
Timeboxing is central to agile methods. Sprints, standups, sprint planning and retrospectives are all timeboxed, and DSDM and earlier rapid application development approaches used timeboxes to protect delivery dates. The idea also appears in personal productivity: the Pomodoro Technique, developed by Francesco Cirillo in the late 1980s, uses 25-minute timeboxes of focused work. One reason timeboxes work is captured in Parkinson's law, from C. Northcote Parkinson's 1955 essay in The Economist: work expands to fill the time available for its completion.
How long are Scrum timeboxes?
The Scrum Guide sets maximum durations for its events. For a one-month sprint they are:
| Event | Maximum duration | Notes |
|---|---|---|
| Sprint | One month | Many teams choose one or two weeks |
| Sprint planning | 8 hours | Usually shorter for shorter sprints |
| Daily Scrum | 15 minutes | Same for any sprint length |
| Sprint review | 4 hours | Usually shorter for shorter sprints |
| Sprint retrospective | 3 hours | Usually shorter for shorter sprints |
Types of timeboxes
- Delivery timeboxes. Sprints, iterations and release trains, where scope flexes to meet a fixed date.
- Meeting timeboxes. A fixed length for each meeting or agenda item, which forces focus.
- Research and spike timeboxes. A fixed budget for investigating an unknown, after which the team decides with what it has learned. See agile spike.
- Personal timeboxes. Blocks of calendar time reserved for specific work.
How to timebox effectively
- Define the goal. Say what the timebox is meant to produce or decide.
- Set the length before starting. Choose it based on the value of the activity, not on how long the work might take.
- Prioritize the scope. Do the most important part first so that stopping early still leaves something useful.
- Stop when time is up. Do not extend. Record what is unfinished.
- Decide what is next. Continue in a new timebox, change direction or stop, based on what was learned.
A hypothetical example
Consider a hypothetical team deciding whether to build its own search engine or adopt an off-the-shelf search service. Rather than research open-endedly, it sets a three-day timebox for two engineers, a budget of six engineer-days. The goal is a recommendation backed by a working test with real data. On day one they test the hosted option, on day two they test a self-hosted open-source engine, and on day three they compare relevance on 50 real customer queries and write up costs. The time runs out before they can test a third option, which they note. The evidence from the two tested options is strong enough to choose, and the team avoids weeks of analysis.
Common pitfalls
- Extending the timebox. Adding "just one more day" removes the discipline that makes timeboxes work.
- Fixing time and scope together. A timebox with a non-negotiable scope is just a deadline. Something must flex.
- Doing the easy parts first. If the most important work is left for the end, it is the first thing cut.
- Timeboxing without a goal. Without a defined output, the time ends but nothing is decided.
Timeboxing underpins every iteration and the agile ceremonies. It is also the mechanism behind fixed-date, flexible-scope delivery in DSDM and in design sprints.
Frequently asked questions
How long are the timeboxes in Scrum?
For a one-month sprint, the Scrum Guide caps sprint planning at 8 hours, the sprint review at 4 hours and the retrospective at 3 hours, with shorter limits usual for shorter sprints. The Daily Scrum is 15 minutes whatever the sprint length, and the sprint itself lasts at most one month, though many teams choose one or two weeks.
What is the difference between a timebox and a deadline?
A timebox fixes the time and lets scope flex: when time runs out, work stops and the team keeps whatever is done. A deadline with a non-negotiable scope fixes both, so nothing can give. That is why effective timeboxes tackle the most important work first, leaving something useful even if lower-priority parts get cut.
What kinds of activities can be timeboxed?
Delivery work such as sprints, iterations and release trains; meetings and individual agenda items; research spikes that investigate an unknown within a fixed budget; and personal blocks of calendar time for focused work, such as the Pomodoro Technique's 25-minute sessions. In each case, set the goal before starting and stop when the time is up rather than extending.
Related terms
Sprint Planning
The meeting that starts each Sprint by setting a goal and a plan.
Sprint Retrospective
The end-of-Sprint meeting where the team agrees how to work better.
Agile Spike
Short, time-boxed research to resolve an unknown before building.
Iteration
A timeboxed cycle of planning, building and reviewing work.