Sprint Backlog
Part of the Scrum Guide chapter index. Read the canonical version inline in the app: Sprint Backlog on app.prettyscrum.org.
Why this chapter matters for the PSM I exam
The Sprint Backlog has three parts: the Sprint Goal (why), the selected Product Backlog items (what), and an actionable plan to deliver them (how). It is the Developers’ plan, by them and for them. It updates throughout the Sprint as more is learned.
The Scrum Guide text
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.
Commitment: Sprint Goal. The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.
The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. As the Developers work during the Sprint, they keep the Sprint Goal in mind. If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.
Source: 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland, © CC BY-SA 4.0. License.
Key points to remember
- Three parts: Sprint Goal, selected items, plan.
- Owned by the Developers.
- Updated throughout the Sprint as understanding grows.
- Commitment: the Sprint Goal.
- Enough detail to inspect progress at the Daily Scrum.
- Sprint Goal stays fixed; scope can be renegotiated.
Common exam trap
The Sprint Backlog is owned by the Developers. The Scrum Master and Product Owner do not modify it. The scope can be renegotiated with the PO, but the Sprint Goal stays fixed.
Practice this chapter
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-05-04. Scrum Guide content licensed under CC BY-SA 4.0.