The Sprint
The Sprint is Scrum’s fixed-length container event where ideas are turned into value. For the PSM I exam, remember the core rules: a Sprint lasts one month or less, a new Sprint starts immediately after the previous one, the Sprint Goal stays fixed, and only the Product Owner can cancel the Sprint if the goal becomes obsolete.
Part of the Scrum Guide chapter index. Read the canonical version inline in the app: The Sprint on app.prettyscrum.org.
Why this chapter matters for the PSM I exam
The Sprint is the heartbeat of Scrum. Maximum one month, fixed length, immediately followed by the next Sprint with no gap. The most-tested rules: Sprint Goal is fixed, scope is renegotiable, only the Product Owner can cancel, cancellation is for an obsolete Sprint Goal only.
Direct answer: what is the Sprint in Scrum?
The Sprint is a fixed-length event of one month or less that contains all other Scrum events and all work needed to move toward the Product Goal. It creates a regular rhythm for inspection and adaptation while protecting focus through the Sprint Goal.
The Scrum Guide text
Sprints are the heartbeat of Scrum, where ideas are turned into value.
They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.
All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.
During the 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.
Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame. Each Sprint may be considered a short project.
Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism. In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making.
A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.
Source: 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland, © CC BY-SA 4.0. License.
Key points to remember
- Maximum length: one month. Shorter is allowed.
- Sprint Goal is fixed. Sprint Backlog scope is renegotiable.
- Only the Product Owner can cancel a Sprint, only when the Sprint Goal becomes obsolete.
- No changes that endanger the Sprint Goal.
- Quality does not decrease to meet the timebox.
- A new Sprint starts immediately after the previous one ends.
Common exam trap
Quality and the Definition of Done do not decrease to fit the timebox. If something does not meet the Definition of Done by Sprint end, it returns to the Product Backlog. The team does not lower the bar just to finish on time.
PSM I question pattern to watch
Watch for answer choices that treat the Sprint Goal as negotiable. The scope can change as more is learned, but the Sprint Goal stays intact. Also watch for wrong claims that the Scrum Master or Developers can cancel a Sprint. Only the Product Owner can do that.
Practice this chapter
For broader prep, pair this chapter with the PSM I passing score guide and the timed mock exam.
Related chapters
Or jump back to the Scrum Guide chapter index or the PSM I hub.
Author: Maurice Heinze (PSM I, certified by Scrum.org). Last updated: 2026-06-05. Scrum Guide content licensed under CC BY-SA 4.0.