Answering: “How much of the Sprint Backlog must be defined during the Sprint Planning event?” (PSM I)

By the end of Sprint Planning, enough of the Sprint Backlog must be defined for the Developers to forecast what they can do. The rest emerges as the Sprint goes on.

Exam Question

How much of the Sprint Backlog must be defined during the Sprint Planning event? (choose the best answer)

• A. Enough so the Developers can create their forecast of what they can do.
• B. Just enough tasks for the Scrum Master to be confident in the Developers’ understanding of the Sprint.
• C. Just enough to understand design and architectural implications.
• D. The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning event.

Correct Answer

A. Enough so the Developers can create their forecast of what they can do.

Why This Is the Correct Answer

Sprint Planning answers why the Sprint is valuable, what can be done and how it will get done. The Developers select items, craft the plan and form a forecast of what they believe they can deliver toward the Sprint Goal. The Scrum Guide notes that the Developers often plan by decomposing items into work of one day or less, but it leaves the method up to them. Full detail up front is neither possible nor useful in complex work. The Guide says “The Sprint Backlog is updated throughout the Sprint as more is learned,” so planning only needs to go deep enough to start with confidence.

Why the Other Options Are Wrong

B. Enough tasks for the Scrum Master to be confident in the Developers’ understanding. The plan is by and for the Developers. The Scrum Master is not the one who needs to be satisfied.

C. Just enough to understand design and architectural implications. Design is part of the conversation, but the purpose of planning is a forecast and a plan toward the Sprint Goal.

D. The entire Sprint Backlog must be identified and estimated. This is upfront planning. In complex work, details emerge during the Sprint and the plan adapts.

Exam Tip

For “how much must be done in Sprint Planning” questions, avoid answers that demand everything up front or that satisfy someone other than the Developers.

Key Takeaways

• Sprint Planning creates enough of a plan to start.
• The Sprint Backlog emerges throughout the Sprint.
• The plan serves the Developers, not observers.