Sprint Backlog & Sprint Goal
PSM I PSM I · Artifacts & Commitments
The Sprint Backlog is composed of three things: the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). It is a plan by and for the Developers — the only artifact that belongs to a single accountability in this way. It is a highly visible, real-time picture of the work 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, and it should have enough detail that the Developers can inspect their progress in the Daily Scrum. The exam tests the three-part composition directly, and it tests ownership just as hard: only the Developers change the Sprint Backlog.
The Sprint Goal is the commitment for the Sprint Backlog. It is the single objective for the Sprint, created during Sprint Planning, and it provides coherence — it gives the team a shared purpose that turns a list of items into a meaningful step toward the Product Goal. The Sprint Goal is created by the whole Scrum Team during Sprint Planning and must be finalized before the event ends. It communicates why the Sprint is valuable to stakeholders, and it is the anchor for every trade-off the team makes during the Sprint: when something changes, the question is whether the Sprint Goal is still achievable, not whether every selected item will be finished. A Sprint can succeed even if not every item is completed, as long as the goal is met — and a Sprint can fail even if every item is done, if the goal was missed. That distinction is one of the most important ideas in Scrum, and the exam tests it through scenarios where items and goals diverge.
The Sprint Backlog is a living plan, not a contract. As the Developers learn more during the Sprint, they update it: tasks are added, removed, or re-estimated; the plan adapts. The Daily Scrum is the main moment for this adaptation, as the Developers inspect progress toward the Sprint Goal and adjust the upcoming work. Scope may be clarified and renegotiated with the Product Owner as more is learned — but the Sprint Goal is protected: no changes are made that would endanger it, and quality does not decrease. The Product Owner cannot unilaterally change the Sprint Backlog, and neither can the Scrum Master or a manager. If new work emerges mid-Sprint, the Developers and the Product Owner discuss it, and the Developers update their own plan if they agree to the change.
The Sprint Goal in practice
A good Sprint Goal is specific enough to guide decisions and flexible enough to allow adaptation. Vague goals like do good work or make progress are useless, because they cannot guide a trade-off. A good goal names the outcome: enable customers to pay with a digital wallet, or reduce the checkout error rate below one percent. When the Developers discover mid-Sprint that one selected item is bigger than expected, the goal tells them what to protect: they can negotiate scope with the Product Owner, dropping or shrinking a less critical item, as long as the goal stays achievable. Without a goal, the same situation becomes a debate about which tasks to finish, with no shared criterion for deciding. The exam often presents exactly this situation and asks what the team should do — the correct answer always involves protecting the Sprint Goal and negotiating scope with the Product Owner.
Worked scenario
A Scrum Team selects five items for a Sprint with the goal of launching a redesigned login flow. On day three, the Developers discover that the authentication service behaves differently from its documentation, and one item will take twice as long as estimated. The team has a goal, so the decision is clear: they talk to the Product Owner, explain the situation, and agree to drop the least important item — a nice-to-have animation — while keeping the items that deliver the login flow itself. The Sprint Backlog is updated to reflect the new plan. The Sprint Goal is still achievable, quality is maintained, and the team finishes the Sprint having delivered what mattered. If the team had no goal, the same discovery would have produced either silent overtime or a quiet decision to cut quality — both of which the framework is designed to prevent.
The Sprint Backlog as a transparency tool
The Sprint Backlog is a highly visible, real-time picture of the work — and that visibility serves everyone, not just the Developers. The Product Owner can see progress toward the Sprint Goal without asking for status reports. Stakeholders can see what the team is working on and why. The Developers themselves can see the whole plan and how their work fits into it. This transparency is what makes self-management possible: when the plan is visible and current, the team can coordinate without a manager, because everyone can see what needs doing and what is already in progress. When the Sprint Backlog goes stale — tasks not updated, new work not added, completed work not marked — transparency drops, coordination suffers, and the Daily Scrum loses its foundation. Keeping the backlog current is part of the Developers' daily discipline, not administrative overhead.
Emergent work is normal during a Sprint. The Developers discover tasks that were not foreseen in Sprint Planning — a test that needs writing, a dependency that needs checking, a bug that needs fixing — and they add them to the Sprint Backlog as they go. The plan grows and changes, and that is expected: the Sprint Backlog is a picture of what the Developers plan to accomplish, updated as more is learned. What does not change without discussion is the Sprint Goal. New work that threatens the goal is a topic for conversation with the Product Owner, not a unilateral decision — and work that does not serve the goal at all may belong in the Product Backlog instead, where the Product Owner can order it against everything else. The exam tests this distinction: the Developers update their own plan freely, but scope changes that affect the Sprint Goal are negotiated with the Product Owner.
Exam traps to watch for
- Thinking the Sprint Backlog is fixed once Sprint Planning ends. It is updated throughout the Sprint as more is learned.
- Letting the Product Owner or Scrum Master change the Sprint Backlog. It is a plan by and for the Developers; only they update it.
- Confusing the Sprint Goal with the list of selected items. The goal is the commitment; a Sprint can meet its goal without finishing every item.
- Treating the Sprint Backlog as a status report. It is a real-time plan for the Developers, with enough detail to inspect progress in the Daily Scrum.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.What is the Sprint Backlog composed of?
Explanation: The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). The Product Goal and Definition of Done belong to other artifacts. Stakeholders are not part of the Sprint Backlog. And the Sprint Backlog is updated throughout the Sprint, not only at the Review.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q2.What is the commitment for the Sprint Backlog?
Explanation: Each artifact has a commitment: for the Sprint Backlog it is the Sprint Goal. The Product Goal is the commitment for the Product Backlog. The Definition of Done is the commitment for the Increment. The Sprint timebox is a property of the Sprint event, not a commitment.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q3.Who owns the Sprint Backlog?
Explanation: The Sprint Backlog is a plan by and for the Developers — they create it and update it throughout the Sprint. The Product Owner owns the Product Backlog, not the Sprint Backlog. The Scrum Master does not track or own it. And it is not a shared document anyone can change; only the Developers update it, with scope negotiated with the Product Owner.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q4.When is the Sprint Backlog updated?
Explanation: The Sprint Backlog is updated throughout the Sprint as more is learned — it is a living plan, not a frozen contract. Sprint Planning creates it but does not freeze it. The Daily Scrum is a key moment for adapting it, but not the only time it changes. And it is updated as learning happens, not only when the goal changes.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q5.A Sprint ends with the Sprint Goal achieved, but one selected item unfinished. How should this Sprint be judged?
Explanation: The Sprint Goal is the commitment for the Sprint Backlog; a Sprint can succeed when the goal is met even if not every item is finished. Judging by item completion alone misses the point of the goal. The Sprint is not invalid because an item is unfinished — the item returns to the Product Backlog. And success is not a matter of the Product Owner's approval; it is judged against the goal.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q6.Mid-Sprint, the Developers discover that a selected item is larger than expected and the Sprint Goal is at risk. What SHOULD they do?
Explanation: During the Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned — the Developers and Product Owner collaborate to adjust while protecting the Sprint Goal. Silent overtime hides the problem and breaks transparency. Reducing quality violates the rule that quality does not decrease. Cancelling is only for when the Sprint Goal becomes obsolete, which is not the case here.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q7.What does the Sprint Goal provide to the Scrum Team?
Explanation: The Sprint Goal is the single objective for the Sprint and provides coherence — it gives the team a shared purpose and a basis for trade-offs. It is not a task list; the plan is the Developers' work. It guarantees nothing about item completion. And it has nothing to do with refinement deadlines.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q8.How much detail should the Sprint Backlog have?
Explanation: The Sprint Backlog should have enough detail that the Developers can inspect their progress in the Daily Scrum. An hour-by-hour schedule is not required and would contradict self-management. Too little detail makes daily inspection impossible. And the Sprint Backlog is a plan for the Developers, not a management tracking tool.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q9.A manager asks the Developers to add an urgent task to the Sprint Backlog directly. What is the correct response?
Explanation: New work enters through the Product Backlog and the Product Owner, who weighs it against everything else; if it affects the Sprint, the Developers and Product Owner negotiate scope together. Managers do not outrank the team in Scrum — there is no hierarchy over the Scrum Team's plan. Refusing to discuss it is unhelpful; the work may be genuinely valuable. And the Scrum Master does not change the Sprint Backlog on anyone's behalf.
Exam objective: PSM I Focus Area: Managing Products with Agility — Stakeholders & Customers