Skip to Content

Scrum PSM II: What Approach Ensures Well-Understood, Actionable Backlog Items at Sprint Planning?

Learn the recommended Scrum approach for preparing Product Backlog items ahead of Sprint Planning to enable smooth forecasting and actionable work for Developers.

Table of Contents

Question

Creating a forecast for a Sprint tends to run more smoothly when the Product Backlog items that are discussed are well understood and actionable. Which approach would you recommend to ensure well understood and actionable Product Backlog items at Sprint Planning?

A. A separate Scrum Team of business analysts and testers analyze high-ordered requirements one Sprint ahead of development.
B. The Product Owner works with the stakeholders to prepare Product Backlog items outside of the Sprint so the Developers will not be disrupted.
C. The analysts on the Scrum Team document high-ordered Product Backlog items during a Sprint when they are not busy working on the forecast.
D. The Developers use some time in each Sprint to analyze, estimate and design high-ordered Product Backlog items.

Answer

The best approach to ensure well understood and actionable Product Backlog items at Sprint Planning is:

D. The Developers use some time in each Sprint to analyze, estimate and design high-ordered Product Backlog items.

Explanation

In Scrum, the Developers are responsible for creating actionable Product Backlog items through analysis, estimating and design. This is part of the Developers’ work each Sprint.

The Developers collaboratively refine high-priority Product Backlog items to ensure they are ready for selection in upcoming Sprints. This involves analyzing requirements, designing solutions, estimating effort, and splitting items as needed. This is an ongoing activity, not a separate process.

Having the Developers do this work avoids handoffs and enables the Developers to directly clarify requirements with the Product Owner as needed. It allows the Developers to have a shared understanding of items before Sprint Planning.

The other options are not recommended in Scrum:

A) Using a separate team for analysis introduces handoffs and can lead to miscommunication. Scrum Teams should be cross-functional.

B) The Product Owner should collaborate with the Developers to refine the Product Backlog, not work separately.

C) Analysis should be an ongoing activity, not relegated to when people aren’t busy. It requires focused effort from the whole Scrum Team.

Therefore, having the Developers spend time each Sprint refining high-ordered Product Backlog Items is the recommended approach for well-understood, actionable items in Sprint Planning.

Scrum PSM II certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Scrum PSM II exam and earn Scrum PSM II certification.