GAQM CASPO-001 - Certified Agile Scrum Product Owner (CASPO)

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 Sprint Backlog is collectively owned by the Developers, not assigned to individuals. TheScrum Guidedefines it as: "The Sprint Backlog is a plan by and for the Developers... It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint." Self-organization means the Developers decide who does what, without fixed ownership of items.

A, B:Individual assignment isn’t mandated; it’s a team effort.

C:Correct—the Developers as a whole own it.

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.

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.

C:TheScrum Guidedefines Scrum as "a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems." This is a core truth.

D:Scrum’s foundation in empirical process control theory (transparency, inspection, adaptation) is explicitly stated in theScrum Guide: "Scrum is founded on empiricism and lean thinking."

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.

TheScrum Guideclearly assigns the responsibility for delivering a "Done" Increment to the Developers: "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." This includes all work—development, testing, integration, etc.—needed to meet the Definition of "Done," a shared commitment that ensures quality. Option A (Scrum Team) is too broad; while the Scrum Team collaborates, only the Developers perform the hands-on work. Option C (Product Owner) is incorrect—they manage the Product Backlog, not the execution. Option D (QA Specialists) introduces a role not defined in Scrum; quality is the Developers’ collective responsibility. Option E (Scrum Master) is wrong—they facilitate, not build. Thus, B is correct.

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.

Management has a role in supporting Scrum, though not within the Scrum Team. TheScrum Guidenotes: "Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing... Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows." Management provides resources, removes impediments, and sets organizational context, but doesn’t manage the team directly.

A:False—management supports externally.

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.