What Is a Sprint in Scrum?

What a Sprint provides

A Sprint gives a Scrum Team a consistent period for pursuing a product goal, inspecting progress, and adapting its work. Its duration is fixed at one month or less. A new Sprint starts when the previous one ends.

The Scrum Guide is the authoritative reference for Scrum. The explanation below distinguishes the goal from the work initially selected to achieve it.

Sprint Goal and scope are different

The Sprint Goal explains the objective. Selected Product Backlog items describe work planned toward it. Developers and the Product Owner may renegotiate that work as new information emerges, provided the goal is not endangered and quality does not decrease.

For example, a team aiming to make account recovery usable may discover that an existing component solves part of the problem. It can adjust the planned implementation while preserving the objective. Treating every selected item as immutable would make that learning harder to use.

What happens inside a Sprint?

Sprint Planning establishes the objective and an initial plan. Developers inspect progress toward that objective during the Daily Scrum and adapt their plan. At the Sprint Review, the Scrum Team and stakeholders inspect the outcome and discuss future adaptations. The Retrospective identifies ways to improve quality and effectiveness.

The Scrum Team consists of a Product Owner, a Scrum Master, and Developers. Developers create a usable Increment that meets the Definition of Done. More than one Increment may be created, and delivery need not wait for the Sprint Review.

When circumstances change

Protect the objective while adapting the plan. If the Sprint Goal becomes obsolete, the Product Owner has the authority to cancel the Sprint. A difficult task or an urgent request does not, by itself, establish that the objective is obsolete.

For a team struggling with repeated interruptions, examine how work enters the Sprint, who can request a change, and how trade-offs are discussed. The aim is useful inspection and adaptation, not perfect adherence to an initial task list.