Sprint

A sprint is a fixed-length iteration in Scrum — usually one to four weeks — during which a team turns a set of backlog items into a done, potentially releasable increment.

A sprint is the heartbeat of Scrum: a timeboxed period, consistent in length, within which the team plans, builds and reviews a usable increment of the product. Each sprint has a sprint goal that gives it focus, a sprint backlog of selected work, and a definition of done that sets the quality bar. Sprints are back-to-back with no gaps, and their fixed length creates a predictable delivery rhythm. Scope can be renegotiated within a sprint, but the length and goal are held stable.

Why it matters

The fixed sprint cadence turns open-ended work into a series of short, finishable commitments. It forces prioritisation (only so much fits), creates frequent delivery and feedback points, and makes progress measurable. The timebox also protects the team from mid-sprint churn — new requests wait for the next sprint rather than derailing the current one — while still allowing the product to change direction every couple of weeks.

When to use it

Sprints suit teams using Scrum for complex, evolving product work where regular delivery and feedback add value. They fit less well for interrupt-driven or highly variable work (where Kanban’s continuous flow is better) or where a single fixed deadline makes iteration pointless.

How to use it

1. Sprint Planning: agree a sprint goal and pull backlog items into the sprint backlog.
2. Build the increment during the timebox, coordinating daily at the Daily Scrum.
3. Protect the sprint from scope churn — new work goes to the backlog for future sprints.
4. Sprint Review: demonstrate the done increment and gather feedback.
5. Retrospective: reflect on how the sprint went and improve for the next one.

Example

A team commits to a two-week sprint with the goal "checkout supports Apple Pay". They pull five backlog items, meet briefly each morning, finish four and carry one over, demo the working checkout at the review, and in the retro agree to refine estimates because the carried item was underestimated.

Template

A sprint runs on a sprint backlog, a definition of done, and a board — start from those and a sprint-goal statement.

Browse templates →

Tools

Related topics

FAQs

Alternatives

• Kanban continuous flow — no fixed iterations
• Longer release cycles — for work that cannot be sliced into short increments