Sprint

A sprint is a fixed-length time-box of one month or less in which a Scrum team turns selected product backlog items into a usable increment of the product. Sprints run back to back, with a new one starting as soon as the previous one ends. All other Scrum events, from Sprint Planning and Daily Scrums to the Sprint Review and Retrospective, take place inside a sprint.

How a Sprint Works

The Scrum Guide sets the rules. A sprint has a fixed length of one month or less, and keeping the length consistent creates a steady rhythm. Many teams choose one or two weeks. The guide notes that shorter sprints create more learning cycles and limit the risk of wasted effort to a smaller time frame.

Each sprint follows the same structure:

• Sprint Planning starts the sprint. The team sets a Sprint Goal, selects items from the product backlog and plans the work. Together these form the sprint backlog.
• Daily Scrums are short daily check-ins where developers inspect progress toward the Sprint Goal and adjust their plan.
• The Sprint Review near the end lets the team and stakeholders inspect what was built and decide what to do next.
• The Sprint Retrospective closes the sprint, with the team looking at how it worked and choosing improvements.

During the sprint, no changes are made that would endanger the Sprint Goal, and quality does not decrease. Scope can still be clarified and renegotiated with the product owner as the team learns more, so the goal is fixed while the details can flex. Work counts as part of the increment only when it meets the Definition of Done. A sprint can be cancelled only if its goal becomes obsolete, and only the product owner can cancel it.

Why Sprints Matter

The time-box forces regular delivery and regular feedback. Every few weeks the team must produce something usable and show it, which exposes problems early and lets the product owner change direction based on real results rather than plans.

The fixed rhythm also helps with forecasting. Because sprints are the same length, a team can look at what it typically completes and plan future work more reliably. And the Sprint Goal gives the team a shared focus: when unexpected work appears, the question is whether it helps or threatens the goal.

Sprint Example

A team works in two-week sprints. In Sprint Planning they set the goal "new users can import contacts from a CSV file" and select four stories. Midway through, they learn that large files time out. Instead of adding scope, they agree with the product owner to support files up to a set size this sprint and add a story for larger files to the backlog. At the Sprint Review they demonstrate the working import to two customers, and in the retrospective they agree to test with realistic file sizes earlier next time.

Sprint vs. Iteration

"Iteration" is the general term for a short, repeating development cycle and is used by Extreme Programming and other agile methods. "Sprint" is Scrum's name for its iteration, with specific rules such as the one-month maximum, a Sprint Goal and the set of events inside it.