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

Self-organization gives the Developers autonomy over their work execution, but not over Product Backlog ordering, which is the Product Owner’s domain. TheScrum Guidestates: "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."

A:Pulling items into the Sprint Backlog is their responsibility during Sprint Planning.

B:Reordering the Product Backlog is the Product Owner’s task: "Ordering Product Backlog items."

C:Delivering "Done" work is their core duty.

TheScrum Guideclarifies that the definition of "Done" is a shared commitment created by the Scrum Team: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." While the Product Owner defines what goes into the Increment (via the Product Backlog), the definition of "Done" is a collaborative effort, often driven by the Developers’ technical expertise and organizational standards, with input from the Product Owner on value and quality expectations. Option A incorrectly gives the Product Owner sole authority, while B correctly reflects the team’s collective responsibility, with the Product Owner as a contributor, not the final arbiter.

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 Backlog is dynamic and evolves with the product. TheScrum Guidedefines it as: "The Product Backlog is an emergent, ordered list of what is needed to improve the product." Option A captures its living, evolving nature.

B:"Formally approved" and "set period" suggest rigidity, unlike Scrum’s adaptability.

C:A separate "Technology Backlog" isn’t in Scrum; all work is in one backlog.

The Scrum Master ensures the Daily Scrum is effective, with a key focus on its 15-minute time-box. TheScrum Guidestates: "The Scrum Master teaches the Developers to keep it within the 15-minute timebox." While they may support other aspects, managing the time-box is primary when present.

A:Correct—time-box adherence is key.

B:The three questions are a practice, not mandatory; Developers run the event.

TheScrum Guidedefines the Sprint Backlog as "a plan by and for the Developers" that includes selected Product Backlog items and a plan to deliver the Sprint Goal. Option C accurately reflects this ownership and purpose. Option A is too absolute—while it’s a plan, it’s not necessarily "complete" as it can evolve during the Sprint. Option B is incorrect—Scrum does not mandate hour-based estimates; estimation is up to the Developers’ discretion. Option D is false—items don’t require individual owners; the Developers collectively own the Sprint Backlog. Option E is wrong—the Product Owner orders the Product Backlog, not the Sprint Backlog, which is managed by the Developers. Thus, C is the best description.

TheScrum Guidemandates that when multiple Scrum Teams work on one product, they produce a single integrated Increment: "Multiple Scrum Teams often work together on the same product... The Increment must be integrated and usable so that it can provide value." This ensures transparency and stakeholder feedback at the Sprint Review. Option A (hardening Sprint) is a misconception—Scrum rejects separate phases for integration. Option B contradicts the single-product focus. Option C limits integration to dependencies, but theScrum Guiderequires full integration regardless. Option D correctly emphasizes the need for a cohesive, inspectable Increment, making it the best answer.

Self-organization in Scrum means the Developers have autonomy over how they deliver the Sprint Goal. TheScrum Guidestates: "The Developers... are self-managing, meaning they internally decide who does what, when, and how." Option A aligns with this—choosing how to accomplish work is their domain. Option B is incorrect; the Product Owner orders the Product Backlog. Option C is wrong; the Product Owner invites stakeholders to the Sprint Review. Option D is partially true—Sprint length is set by the Scrum Team collaboratively, not just the Developers, and is typically fixed once established. Option E is false; release decisions are the Product Owner’s responsibility. Thus, A is the best answer.

The Definition of "Done" is a shared standard, often set by the organization, but defaults to the Scrum Team if no broader standard exists. TheScrum Guidestates: "If the Definition of Done for an increment is part of the conventions, standards, or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product."

A:Correct—organizational standards take precedence, otherwise the Scrum Team defines it.

B:Collaboration occurs, but it’s not just a "common denominator."

The Product Owner’s core accountability is maximizing value through the Product Backlog. TheScrum Guidestates: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." Option B encapsulates this fully.

A:The Developers deliver the Increment; the Product Owner doesn’t ensure it.

C:Refinement is part of management, but not the sole accountability.