What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team? (choose the best three answers)

Question

Options

• AIt helps the Developers estimate the date that the Product Backlog will be
• BIt is not mandatory in Scrum. There is no real advantage.
• CIt provides a good overall direction so Sprints will feel less like isolated pieces of
• DIt helps the Scrum Team keep focus and they can weigh any decision against
• EIt is easier to inspect incremental progress at the Sprint Review.

Explanation

Based on the Scrum Guide, the correct answers are C, D, and E.

A clearly defined Product Goal gives the team a shared long-term objective that connects Sprint work into a coherent journey (C), acts as a north star so the team can evaluate decisions - like Backlog refinement choices - against a common purpose (D), and provides a meaningful benchmark at Sprint Reviews to inspect whether the increment is actually moving toward the goal (E).

A is wrong because the Product Goal is a strategic direction, not a forecasting tool - it doesn't help estimate when the entire Product Backlog will be finished. B is wrong because the 2020 Scrum Guide explicitly introduced the Product Goal as a commitment for the Product Backlog, making it a formal Scrum artifact element with clear intent.

Memory tip: Think of the Product Goal as a lighthouse - it gives direction (C), helps you steer every decision (D), and lets you measure how close you are at each Sprint Review (E). Anything about scheduling or "it doesn't matter" is automatically wrong.

No community discussion yet for this question.