Timeboxing
- Pronunciation
- TYM-boks-ing
In short
Timeboxing is setting a fixed maximum time for an activity in advance and stopping when it runs out, keeping work focused and forcing decisions about scope.
What is timeboxing?
Instead of asking how long something will take, timeboxing asks how much time it is worth. A design discussion gets 30 minutes; a research spike gets two days; a sprint gets two weeks. When the box ends, the team stops and looks at what it has, then decides whether that is enough, whether to change direction or whether to spend another box on it.
Scrum is built on timeboxes. The sprint has a fixed length, and every event has a maximum duration, such as 15 minutes for the daily scrum. Spikes, hackathons and design sprints use the same idea, and individuals use it too: the Pomodoro technique works in 25-minute focused blocks followed by short breaks.
Timeboxing works because it fights Parkinson's law, the observation that work expands to fill the time available, and it forces prioritization: with a fixed amount of time, the most important parts get done first. It also makes plans predictable, because time is fixed and scope adjusts, rather than the other way round.
A common misconception is that timeboxing means rushing or cutting corners. The scope changes, not the quality bar: if a feature doesn't fit, a smaller version ships or the rest moves to the next box. Teams that simply let timeboxes overrun lose the main benefit, the regular moment to stop and decide.
Key takeaways
- Timeboxing fixes a maximum time for an activity in advance.
- When time runs out, you stop and decide what to do next.
- Scrum sprints and events, spikes and Pomodoros are timeboxes.
- It counters Parkinson's law and forces prioritization.
- Scope adjusts to the time, not quality.
Readers ask
What is a timebox in Scrum?
A maximum duration for an event or iteration. The sprint itself has a fixed length, and events such as sprint planning, the daily scrum and the retrospective each have an upper time limit.
What is the Pomodoro technique?
A personal timeboxing method: work with full focus for 25 minutes, take a short break, and after four rounds take a longer break. It helps with concentration and with estimating how long tasks take.
What happens when a timebox ends before the work is done?
You stop, review what has been achieved and decide: accept a smaller result, plan another timebox, or drop the work. The decision is deliberate rather than letting the task drift on.
See also
- SprintTeams & Process, p. 26A sprint is a fixed-length period of one month or less, often two weeks, in which a Scrum team works toward one goal and produces a usable product increment.
- ScrumTeams & Process, p. 21Scrum is an Agile framework in which a small team delivers a product in fixed-length cycles called sprints, using defined roles, events, and artifacts.
- SpikeTeams & Process, p. 25A spike is a short, timeboxed investigation an Agile team does to answer a question or reduce uncertainty before committing to build a feature.
- Daily StandupTeams & Process, p. 6A daily standup is a short daily meeting, usually 15 minutes or less, where a team checks progress toward its goal, plans the day, and raises blockers.
- Sprint PlanningTeams & Process, p. 27Sprint planning is the Scrum event that starts each sprint, where the team agrees on a sprint goal, selects backlog items it can finish and plans the work.
- RetrospectiveTeams & Process, p. 20A retrospective is a team meeting held at the end of each sprint to reflect on how the team worked and agree on concrete ways to improve next time.
Spotted a mistake or something missing on this page?Suggest an edit