Pass the GAQM GAQM: Scrum / Agile CASPO-001 Questions and answers with CertsForce

A single product has one Product Owner, regardless of the number of teams. TheScrum Guidestates: "The Product Owner is one person, not a committee... Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product."

A:Multiple Product Owners fragment accountability.

B:Correct—one Product Owner for one product.

The Sprint Goal and the Sprint Backlog are both outcomes of Sprint Planning, making this statement true. According to theScrum Guide, Sprint Planning is an event where the Scrum Team collaborates to define the work to be performed during the Sprint. The Sprint Goal is a single objective set for the Sprint, providing focus and coherence to the work selected. It is crafted collaboratively by the Product Owner, Developers, and Scrum Master during Sprint Planning. Simultaneously, the Sprint Backlog is created, consisting of the Product Backlog items selected for the Sprint plus a plan to deliver them, aligned with the Sprint Goal. TheScrum Guidestates: "Sprint Planning initiates the Sprint by laying out the work to be performed... This resulting plan is created by the collaborative work of the entire Scrum Team." Thus, both the Sprint Goal and Sprint Backlog emerge from this event, confirming option A as correct.

TheScrum Guidetasks the Product Owner with ordering the Product Backlog to maximize value, but it doesn’t mandate a specific method like "value points." Option B is correct—using value points (e.g., in techniques like WSJF—Weighted Shortest Job First) is a helpful practice, but empirical validation (market reception) remains the ultimate measure, aligning with Scrum’s focus on inspection and adaptation. Option A overstates value points as "ultimate," ignoring real-world feedback. Option C is too rigid; Scrum allows flexibility in tools as long as empiricism is upheld. Thus, B is the best answer.

TheScrum Guidegrants the Product Owner sole authority over the Product Backlog: "The Product Owner is one person, not a committee... For Product Owners to succeed, the entire organization must respect their decisions." No external roles or processes override this.

A, C, D, E:These introduce roles (CFO, CEO, program manager, architect, change board) not recognized in Scrum as limiting the Product Owner’s authority.

F:Impediments affect execution, not the Product Owner’s right to update the backlog.

The Product Owner has explicit accountability for product value. TheScrum Guidestates: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

A:The Scrum Master ensures Scrum effectiveness, not value.

B:Correct—value maximization is their role.

The Sprint Backlog is created during Sprint Planning as the Developers select items and plan delivery. TheScrum Guidestates: "Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team."

A:Pre-planning creation isn’t supported; it’s a Sprint-specific plan.

B:It starts in planning, though it evolves during the Sprint.

C:Refinement prepares the Product Backlog, not the Sprint Backlog.

Scrum doesn’t require a fully detailed Product Backlog to begin. TheScrum Guidenotes: "The Product Backlog is an emergent, ordered list... It evolves over time." A minimal backlog with a Product Goal and some items is sufficient for the first Sprint, with refinement ongoing.

A:True—Scrum embraces starting with what’s known.

Scrum imposes no formal pre-conditions for Sprint Planning beyond the Sprint starting. TheScrum Guidestates: "Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint."

A:A fully refined backlog isn’t required; refinement is ongoing.

B:Budget approval isn’t a Scrum concept.

C, D:The Sprint Goal is defined during, not before, Sprint Planning.

E:Some "Ready" items help, but it’s not mandatory; planning can refine items.

The Product Owner and Developers must collaborate closely to maximize value, as per theScrum Guide.

B:Collaboration enables the Product Owner to balance effort (Developer input) and value (their priority), aligning with: "The Product Owner may influence the Developers by helping them understand and select trade-offs."

D:Frequent collaboration ensures the Developers understand stakeholder needs, supporting the creation of a valuable Increment: "The Developers are required to conform to the Definition of Done and to deliver an Increment that meets the Sprint Goal."

A:Separation contradicts Scrum’s emphasis on teamwork; the Scrum Team is cohesive, not siloed.

C:Full-time co-location isn’t required; the Product Owner focuses on value, not technical mastery.

TheScrum Guideexplicitly states: "The Product Owner is accountable for effective Product Backlog management, which includes... clearly expressing Product Backlog items." This responsibility ensures that the items reflect stakeholder needs and are understandable to the Developers. Option B is incorrect—the Scrum Master facilitates and coaches, not manages the Product Backlog. Option C is wrong—neither the Scrum Master nor Developers are accountable for this; it’s the Product Owner’s role. Option D introduces a "business analyst" role, which isn’t part of Scrum; the Product Owner directly handles this duty without delegation to a proxy. Thus, A is correct.