Agile Delivery · tool 2 of 6

Scrum Sprints

Scrum Sprints: delivers value in short, regular increments, and adapts to feedback along the way.

Best for: Products with evolving needs · Time: 1–4 week cycles
Domain: Schedule · Focus area: Executing

Product backlog

Sprint planning

Sprint, 1–4 weeks, daily scrum

Sprint review

Retrospective

Then the next sprint starts: a short, repeating loop that delivers a working increment each time.

How it works

Work is done in fixed-length sprints of 1 to 4 weeks. A Product Owner orders the backlog, the Developers commit to a sprint goal, and a Scrum Master removes impediments. Each sprint ends with a usable increment, shown to stakeholders.

Events: Sprint Planning, Daily Scrum (15 min), Sprint Review, Retrospective.
Artifacts: Product Backlog, Sprint Backlog, Increment.
The sprint length stays fixed — scope adapts, not the timebox.

How to apply it

Have the Product Owner build and order the backlog (MoSCoW helps).
Sprint Planning: the team picks what fits and agrees one sprint goal.
Daily Scrum: 15 minutes on progress toward the goal and blockers.
Sprint Review: demo working results to stakeholders and collect feedback.
Retrospective: choose one or two improvements, then start the next sprint.

Pro tip

Hybrid works: keep a high-level Gantt for milestones and contracts, and run Scrum inside the delivery phases.

Quick check

The sprint goal is at risk. What stays fixed?

Sources

K. Schwaber and J. Sutherland, The Scrum Guide (2020)

Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made