Is the relationship between the ordering of the Product Backlog, the Product Owner having clear objectives, and the Sprint Goal direct?

• A. The relationship is direct and independent of team size
• B. Yes. The PO typically comes to Sprint Planning with a business objective and the team crafts a Sprint Goal aligned to that objective.
• C. The relationship is indirect and depends on complexity
• D. The relationship is irrelevant

Answer: (B)

In Scrum, there’s a direct link between how the Product Backlog is ordered, the Product Owner’s clear objectives, and the Sprint Goal. The Product Owner prioritizes the backlog to maximize value and set business objectives. When Sprint Planning happens, the team doesn’t guess the direction in isolation—they craft a Sprint Goal that aligns with those objectives and the prioritized backlog. This creates a straight line from what the backlog is ordered to what the team commits to achieve in the sprint: the Sprint Goal is shaped to reflect the PO’s objectives, and the selected backlog items are the means to reach that goal.

This option captures that flow: the Product Owner comes to Sprint Planning with a business objective, and the team develops a Sprint Goal that aligns with that objective, ensuring the backlog’s priorities guide the sprint’s focus. It’s not about team size changing the relationship, and it isn’t described as indirect or irrelevant in Scrum, which is why this choice fits best.

Others imply the relationship is indirect, dependent on complexity, or irrelevant, which doesn’t reflect how Scrum emphasizes alignment between backlog priorities, the PO’s objectives, and the sprint’s shared goal.