Skip to content
PMPCAPM

Sprint

A Sprint is a fixed-length timebox of one month or less in Scrum during which the team creates a usable, potentially releasable product Increment.

Explanation

The Sprint is the heartbeat of Scrum. Each Sprint is a container for all other Scrum events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Sprints have a consistent duration throughout a development effort, and a new Sprint starts immediately after the conclusion of the previous one.

During a Sprint, no changes are made that would endanger the Sprint Goal, quality does not decrease, the Product Backlog is refined as needed, and scope may be clarified and renegotiated with the Product Owner as more is learned. If the Sprint Goal becomes obsolete, the Product Owner can cancel the Sprint, though this is rare.

Sprints enable predictability by ensuring inspection and adaptation of progress toward the Product Goal at least every calendar month. Shorter sprints generate more learning cycles and reduce the risk of cost and effort going to waste. Most teams use two-week sprints as a practical balance between overhead and feedback frequency.

Key Points

  • Fixed-length timebox of one month or less
  • Contains all other Scrum events
  • No changes that endanger the Sprint Goal are permitted
  • Only the Product Owner has the authority to cancel a Sprint

Exam Tip

Sprints are always timeboxed and never extended. If the work is not done, remaining items return to the Product Backlog.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.