The Sprint is the foundational unit of Scrum. Everything that happens in Scrum happens within a Sprint — the planning, the daily coordination, the delivery, the review, the retrospective. Sprints run continuously: one ends immediately before the next begins. There are no gaps, no interim periods, no pause for reflection outside the retrospective. This continuity is deliberate.

What a Sprint is

A Sprint is a fixed-length period — one month or less — during which the team commits to achieving a Sprint Goal and creates a usable Increment of the product. The fixed length creates rhythm: a predictable cadence of planning, delivery, and review that, over time, makes the team's performance more predictable and their improvement more systematic.

The Sprint is also bounded: once started, its goal and scope should not change in ways that would undermine its value. The team commits to a Sprint Goal, not to a specific list of tasks, which gives them flexibility to adapt within the Sprint while maintaining the integrity of the commitment.

The Sprint cycle

Sprint Planning opens each Sprint. The team and Product Owner determine what the Sprint Goal is — the single objective that gives the Sprint its purpose — and the team selects the backlog items they believe will achieve it. The Sprint Backlog is the result: the selected items plus the team's plan for delivering them.

During the Sprint, the Daily Scrum provides a fifteen-minute daily touchpoint for Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next day. The emphasis is on adaptation — identifying what is working, what is not, and what needs to change — rather than on reporting.

The Sprint Review closes the delivery phase. The team demonstrates what was built to stakeholders, collects feedback, and collaborates on what the Product Backlog should look like going forward. This is an active working session, not a presentation.

The Sprint Retrospective closes the Sprint itself. The team examines not the product but the process: how did they work together, what got in the way, and what specific changes would improve the next Sprint? Retrospectives are where the continuous improvement discipline lives.

Before the first Sprint

Three things need to exist before a team's first Sprint can be productive. First, a Product Vision that is clear enough for the team to understand what they are working toward and why. Second, a Product Backlog that has been assembled and prioritised — not necessarily complete, but sufficient for the first Sprint Planning session. Third, realistic capacity planning: the team needs to understand what their actual availability is for the Sprint and commit only to what they can genuinely achieve.

Teams that skip these prerequisites tend to spend their first Sprint discovering why they matter.

Why Sprint length matters

Longer Sprints reduce planning overhead but increase risk — more can go wrong before the feedback loop of a Review catches it. Shorter Sprints increase planning frequency but reduce the time available for meaningful delivery. Most teams find two weeks a productive balance, though the right length depends on the nature of the work and the team's context.

The most important principle is consistency. Teams that change their Sprint length frequently are disrupting the rhythm that makes improvement measurable and planning predictable. Settling on a Sprint length and maintaining it — with deliberate change only when there is clear evidence that a different length would serve better — tends to produce better outcomes than constant experimentation with the cadence.

What makes Sprints valuable

The Sprint's value comes from three things working together: a meaningful Sprint Goal that gives the team a shared direction, a planning process that produces realistic commitments, and a Review process that generates genuine feedback rather than approval ceremonies. When these three elements are working well, Sprints produce a compounding learning effect: each Sprint is not only delivering value but building the team's capability to deliver more effectively in the next one.