Pepelen
Agile and Scrum: Flexible Project Management

Lesson

Lesson 4.1 — The Sprint and its timeboxes

Explain the Sprint as the container event with a fixed length and correctly state event timeboxes as maximums.

1 / 5

The Sprint: container for all events

The Sprint and its timeboxes

The Sprint is the heart of Scrum. It is a fixed-length event that acts as a container for all other Scrum events — Sprint Planning, the Daily Scrums, the Sprint Review, and the Sprint Retrospective all happen inside one Sprint. A Sprint lasts one month or less, and its length never changes mid-Sprint. If a Sprint is set to two weeks, every Sprint is two weeks until the team deliberately decides to change it. A key concept is the timebox. A timebox is a MAXIMUM time limit, not an exact duration. The Scrum Guide defines the following timeboxes for a one-month Sprint: Sprint Planning is at most 8 hours, Sprint Review is at most 4 hours, and Sprint Retrospective is at most 3 hours. For shorter Sprints, these events are usually proportionally shorter. Always say 'at most' or 'no more than' — saying a Sprint Planning 'takes exactly 8 hours' would be incorrect. The Sprint itself does not have a timebox in the same sense — it has a fixed, pre-agreed length. The stability of Sprint length creates rhythm and predictability, which is essential for empirical process control.
Lesson notes
The Sprint and its timeboxes
The Sprint is the heart of Scrum. It is a fixed-length event that acts as a container for all other Scrum events — Sprint Planning, the Daily Scrums, the Sprint Review, and the Sprint Retrospective all happen inside one Sprint. A Sprint lasts one month or less, and its length never changes mid-Sprint. If a Sprint is set to two weeks, every Sprint is two weeks until the team deliberately decides to change it. A key concept is the timebox. A timebox is a MAXIMUM time limit, not an exact duration. The Scrum Guide defines the following timeboxes for a one-month Sprint: Sprint Planning is at most 8 hours, Sprint Review is at most 4 hours, and Sprint Retrospective is at most 3 hours. For shorter Sprints, these events are usually proportionally shorter. Always say 'at most' or 'no more than' — saying a Sprint Planning 'takes exactly 8 hours' would be incorrect. The Sprint itself does not have a timebox in the same sense — it has a fixed, pre-agreed length. The stability of Sprint length creates rhythm and predictability, which is essential for empirical process control.
Lesson 4.1 — The Sprint and its timeboxes — Agile and Scrum: Flexible Project Management