GAQM Certified Agile Scrum Product Owner (CASPO) CASPO-001 Exam Dumps: Updated Questions & Answers (October 2025)

The Daily Scrum is the Developers’ event, not the Scrum Master’s. TheScrum Guidestates: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team... The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum." The Scrum Master’s role is to ensure it happens and is effective, not to attend mandatorily.

A:Documenting impediments is a support task, not a Daily Scrum requirement.

B:Facilitation is optional, only if requested.

C:Burndown charts aren’t mandated; this isn’t their purpose.

TheScrum Guidedescribes the Sprint Retrospective as an event where the Scrum Team inspects itself and plans improvements, with the Scrum Master playing a dual role: "The Scrum Master participates as a peer team member in the Sprint Retrospective... and ensures that the event takes place and is positive and productive." Option C captures this—participating as a team member and facilitating when needed. Option A (scribe) is too narrow and not required. Option B (prioritizing) is a team decision, not the Scrum Master’s alone. Option D (reporting to management) violates Scrum’s team autonomy. Thus, C is correct.

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 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 Guideemphasizes self-organization and self-management as core principles for the Scrum Team, particularly the Developers: "They are self-managing, meaning they internally decide who does what, when, and how." When forming multiple Scrum Teams from a large group, the Scrum Master’s role is to facilitate and coach, not dictate. Option C aligns with this by empowering the Developers to self-organize into teams, fostering ownership and collaboration. Option A (skill-based division) is too prescriptive and risks creating component teams rather than cross-functional ones, which Scrum favors. Option B shifts responsibility to the Product Owner, whose role is Product Backlog management, not team formation. Thus, C is the best tactic.

TheScrum Guidedefines Scrum as "a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems." It provides roles, events, and artifacts but intentionally avoids prescribing detailed "how-to" processes for building software (e.g., coding practices, tools). This distinguishes it from a methodology, which offers specific steps. Scrum focuses on "what" (e.g., deliver an Increment) and leaves "how" to the team’s discretion, making the statement false. Thus, B is correct.

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.

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.

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.

TheScrum Guidestates: "The Product Owner is also accountable for effective Product Backlog management, which includes... representing the needs of many stakeholders in the Product Backlog." Option C reflects this collaborative approach—actively seeking stakeholder input to shape the Product Backlog. Option A is too passive; the Product Owner interprets, not just transcribes. Option B contradicts Scrum’s emphasis on stakeholder engagement. Option D introduces a formal process not in Scrum; the Sprint Review is for feedback, not signed agreements. Thus, C is best.