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

The Product Owner is accountable for ordering the Product Backlog to maximize value. TheScrum Guideallows delegation of tasks but not accountability: "The Product Owner may do the above work, or may delegate the responsibility to others. Regardless, the Product Owner remains accountable." Delegating ordering risks misprioritization, potentially leading to an Increment that doesn’t meet value goals or releasability.

A, B, D:These are unrelated consequences.

As Scrum Teams mature, they improve quality and effectiveness. TheScrum Guideimplies that the Definition of "Done" evolves: "As Scrum Teams mature, it is expected that their definitions of‘Done’ will expand to include more stringent criteria for higher quality."

A:Events remain mandatory for Scrum’s structure.

B:The Scrum Master remains vital for coaching and facilitation.

Sprint length in Scrum is a critical decision that impacts the team’s ability to deliver value and adapt. TheScrum Guidestates that Sprints are fixed in length (typically one month or less) to create consistency and enable regular inspection and adaptation. While it doesn’t explicitly list factors, practical application and Scrum principles suggest:

A (The ability to go to market with a product release):Shorter Sprints allow faster feedback and releases, aligning with Scrum’s focus on delivering value frequently.

D (The level of uncertainty over the technology to be used):High uncertainty may warrant shorter Sprints to mitigate risk and validate assumptions, a key aspect of empirical process control.

The Scrum Master serves the Product Owner by fostering Scrum adoption: "The Scrum Master serves the Product Owner in several ways, including... Helping find techniques for effective Product Goal definition and Product Backlog management." If collaboration is lacking, coaching (C) aligns with this role, emphasizing Scrum’s collaborative nature and incremental value delivery.

A:Escalation bypasses the Scrum Master’s responsibility to resolve issues.

The Product Owner’s primary accountability is maximizing the value of the product, per theScrum Guide. Metrics should reflect outcomes, not just internal process efficiency:

A (Time to market):Faster delivery of Increments to the market validates value through real-world feedback, a key Scrum principle.

B (Customer satisfaction):This directly measures whether the product meets user needs, aligning with value delivery.

C (Velocity):While useful for Developers to gauge capacity, it’s an internal metric, not adirect indicator of value.

D (Productivity):This focuses on effort, not outcome, and isn’t tied to value in Scrum.

The Definition of "Done" ensures quality and usability, critical for the Product Owner’s value delivery:

A:Per theScrum Guide, a "Done" Increment is usable, enabling the Product Owner to decide on releases at the Sprint Review.

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.

TheScrum Guidedefines the Scrum Team as consisting of three roles: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers." Option A (Developers) is the group responsible for building the Increment. Option D (Product Owner) manages the Product Backlog and value delivery. Option E (Scrum Master) facilitates Scrum adoption and team effectiveness. Options B (Users) and C (Customers) are external stakeholders, not Scrum Team roles—they interact with the product but aren’t part of the team. Thus, A, D, and E are the correct roles.

The Product Backlog is emergent and doesn’t need to be fully "ready" before Sprint Planning. TheScrum Guidestates: "Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint." If items aren’t refined, the team can refine them during planning to select enough for the Sprint.

A:Canceling isn’t an option; Sprints start immediately after the previous one.

B:Splitting Sprint Planning isn’t supported; it’s a single time-boxed event.

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.