The Sprint Goal and Sprint Backlog are related but distinct. Confusing them is one of the most common PSM I exam mistakes — here's how to get it right.

Sprint Goal vs Sprint Backlog: What's the Difference and Why It Matters for PSM I

The Sprint Goal and the Sprint Backlog are two of the most tested concepts on the PSM I exam — and they are frequently confused. Candidates who understand the relationship between them, and the crucial difference in how each can change during a Sprint, will answer a significant cluster of exam questions correctly.

What Is the Sprint Goal?

The Sprint Goal is the single objective for the Sprint. It is the commitment associated with the Sprint Backlog, and it answers one question: why is this Sprint valuable?

Key facts from the Scrum Guide 2020:

The Sprint Goal is created during Sprint Planning by the entire Scrum Team — not by the Product Owner alone, not by the Developers alone
It provides flexibility to the Developers: they may negotiate the scope of the Sprint Backlog with the Product Owner as they learn more, as long as the Sprint Goal is not endangered
If the work turns out to be different than expected — more complex, simpler, or heading in an unexpected direction — the Sprint Goal does not change
The Sprint Goal gives the team a coherent purpose that is larger than any individual backlog item

Think of the Sprint Goal as the destination. The path to that destination can adapt. The destination itself does not move.

What Is the Sprint Backlog?

The Sprint Backlog is made up of three things:

The Sprint Goal (why)
The set of Product Backlog Items selected for the Sprint (what)
An actionable plan for delivering the Increment (how)

The Sprint Backlog is owned by the Developers. It is a highly visible, real-time picture of the work the Developers plan to accomplish during the Sprint. It is updated throughout the Sprint as the Developers learn more.

The Critical Distinction: What Can Change and What Cannot

This is where PSM I questions are designed to trip you up.

The Sprint Goal cannot change once the Sprint begins. It is fixed for the duration of the Sprint.
The Sprint Backlog items can change. The Developers may add or remove work, adjust the plan, and renegotiate scope with the Product Owner — provided these changes serve the Sprint Goal rather than undermine it.

The Sprint Goal is the commitment. The Sprint Backlog is the current best plan for fulfilling that commitment. Plans adapt; commitments hold.

PSM I Exam Questions on This Topic

The following three questions are written in PSM I style. Work through each before reading the explanation.

Question 1

During a Sprint, the Developers discover that one of the Sprint Backlog items is more complex than originally estimated. They believe completing it will prevent them from achieving the Sprint Goal. What should they do?

A) Extend the Sprint to allow more time for the complex item
B) Remove the Sprint Goal so the team can focus purely on completing all backlog items
C) Work with the Product Owner to negotiate the scope of the Sprint Backlog while keeping the Sprint Goal intact
D) Escalate to the Scrum Master to resolve the problem on their behalf

Correct answer: C

The Sprint Goal is fixed. The scope of the Sprint Backlog is negotiable. When work is harder than expected, the right response is to collaborate with the Product Owner on what can be adjusted — not to abandon the goal, extend the Sprint, or delegate the problem. The Scrum Guide explicitly states that scope may be clarified and renegotiated with the Product Owner as more is learned.

Question 2

At the end of Sprint Planning, the team has selected their Product Backlog items and created a plan. The Product Owner says the Sprint Goal will be written after the meeting, once she has had time to think about it. Is this correct?

A) Yes — the Product Owner is responsible for the Sprint Goal and can create it at any time
B) Yes — the Sprint Goal just needs to be set before the Daily Scrum begins
C) No — the Sprint Goal is created during Sprint Planning by the entire Scrum Team
D) No — the Sprint Goal must be approved by stakeholders before the Sprint begins

Correct answer: C

The Scrum Guide 2020 is explicit: the Sprint Goal is created during Sprint Planning. It is a collaborative output of the whole Scrum Team — Scrum Master, Product Owner, and Developers together. The Product Owner does not own the Sprint Goal unilaterally, and it cannot be deferred to after planning ends.

Question 3

Halfway through the Sprint, the Developers realise the remaining work will take far less time than expected. They will likely finish all Sprint Backlog items with a week to spare. What should they do?

A) End the Sprint early since the work is complete
B) Pull in additional Product Backlog items, working with the Product Owner to ensure they align with the Sprint Goal
C) Wait until the Sprint ends before taking on any new work
D) Extend the next Sprint to accommodate the extra capacity

Correct answer: B

The Sprint runs its full timebox — it cannot be shortened unilaterally by the Developers. When capacity frees up, the Developers may pull additional Product Backlog items in collaboration with the Product Owner. These additions should ideally align with the Sprint Goal. The Sprint Goal remains unchanged; only the scope of what gets done expands to fill available capacity.

Why This Topic Appears Repeatedly on PSM I

The Sprint Goal vs Sprint Backlog distinction tests something fundamental: whether a candidate understands that Scrum is built around a commitment to an objective, not a commitment to a task list. Many teams in the real world treat the Sprint Backlog as the contract and ignore or discard the Sprint Goal when things get difficult. The Scrum Guide 2020 explicitly rejects this approach.

For the PSM I exam, internalise this: the Sprint Goal is the why, it is immovable, and it gives the team the freedom to adapt the how. Every question on this topic can be answered correctly if you hold that principle clearly.