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

TheScrum Guideallows the Sprint Backlog to be adjusted during Sprint Planning if the Developers realize the scope exceeds capacity: "If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint."

D:Removing or changing items is valid to align with capacity while preserving the Sprint Goal.

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.

Incremental delivery in Scrum involves delivering usable product pieces iteratively. TheScrum Guidedefines an Increment as: "a concrete stepping stone toward the Product Goal" that is "usable" and "meets the Definition of Done." Option D—deploying functional increments over the project—reflects this, emphasizing cumulative value delivery.

A:Nonfunctional increments contradict the "usable" requirement.

B:Testing is part of creating a "Done" Increment, not a post-delivery step.

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 Retrospective is an event for the entire Scrum Team, including the Scrum Master, to inspect and improve their processes. TheScrum Guideexplicitly states that the Scrum Master participates as a peer: "The Scrum Master participates as a peer team member in the Sprint Retrospective from the accountability over the Scrum Team’s effectiveness." This ensures a collaborative review of the Sprint, including the Scrum Master’s facilitation role.

A:True—the Scrum Master is a full participant.

The Product Backlog is under the Product Owner’s control and can be updated anytime. TheScrum Guidestates: "The Product Owner is accountable for effective Product Backlog management," implying ongoing adjustments as needed.

A:Limiting updates to Sprint Review contradicts its emergent nature.

B:Refinement is a key activity, but updates aren’t restricted to it.

C:A "change request" process isn’t in Scrum.

TheScrum Guideexplains the Definition of "Done" as "a formal description of the state of the Increment when it meets the quality measures required for the product":

A:It increases transparency by making quality expectations visible to all.

B:It creates a shared understanding of "complete" across the Scrum Team.

The Sprint Retrospective is a key Scrum event focused on continuous improvement. TheScrum Guidedefines its purpose explicitly as an opportunity for the Scrum Team (Product Owner, Scrum Master, and Developers) to reflect on the past Sprint and identify actionable ways to enhance their effectiveness and quality in the next Sprint. Option C—"Inspect how the last Sprint went and plan improvements for the next Sprint"—accurately captures this intent, aligning with Scrum’s empirical pillars of inspection and adaptation. Let’s evaluate all options:

A (Review stories planned for the next Sprint and provide estimates):This pertains to Sprint Planning or Product Backlog refinement, not the Retrospective. The Retrospective focuses on past performance, not future planning of specific stories or estimation.

B (Demonstrate completed User Stories to the Product Owner):This describes the Sprint Review, where the Increment is showcased to stakeholders, not the Retrospective, which is an internal team event.

C:Correct—the Retrospective is about inspecting the last Sprint (e.g., processes, interactions, tools) and adapting by planning improvements, making it the best answer.

The Product Owner leads inspection related to value and backlog management:

A:At the Sprint Review, they present the Product Backlog state, adapting it based on Increment feedback, per: "The Product Owner discusses the Product Backlog as it stands."

D:Inviting stakeholders ensures market insights inform value, aligning with: "The Product Owner may invite other people to attend."

B:Daily Scrum is for Developers; the Product Owner doesn’t inspect burn-downs there.

Success in Scrum is tied to value delivery, not internal metrics. Option B—frequent releases with KPI updates—aligns with Scrum’s empirical nature: "Scrum is founded on empiricism and lean thinking." Real-world feedback refines the Product Backlog, ensuring success.

A:Velocity is an internal capacity metric, not a success indicator.

C:Time variance is irrelevant to value.