In 30 seconds
- Fix the time; let scope adjust.
- Forces focus and decisions; stops endless polishing.
- Every Scrum event has a timebox.
Try it
min
15:00
Space start/pause · N next speaker · R reset · F fullscreen
Why it works
Work tends to expand to fill the time available. A timebox flips the usual approach: instead of asking how long something will take, decide how long it deserves, and do the best you can within it.
Scrum's timeboxes
| Event | Maximum (one-month sprint) |
|---|---|
| Sprint | One month |
| Sprint Planning | 8 hours |
| Daily Scrum | 15 minutes |
| Sprint Review | 4 hours |
| Retrospective | 3 hours |
Shorter sprints get proportionally shorter events.
Tips
- Decide what "good enough" looks like at the start
- Use a visible timer
- When time's up, decide: stop, or consciously grant one more box
Spikes are timeboxed research.
Myth vs reality
Myth · A timebox is a deadline to rush toward.
Reality · It's a limit; finishing early is fine.
Myth · Timeboxes reduce quality.
Reality · Scope flexes, not quality.
Myth · Timeboxes only apply to meetings.
Reality · They work for research, design and any open-ended task.
FAQ
What if the work isn't finished?
Stop, decide what's next, and carry the rest as new work if needed.
Are timeboxes the same as estimates?
No; an estimate predicts, a timebox limits.
Who sets a timebox?
Whoever owns the activity, agreed with those taking part.