CASPO-001 Certified Agile Scrum Product Owner (CASPO) Questions and Answers

The Product Backlog is dynamic and evolves with the product. The Scrum Guide defines 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 Sprint Backlog is a plan that evolves. The Scrum Guide states: "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." At Sprint Planning’s end, it needs enough detail to start, with flexibility to adapt later.

A: Correct—initial work is planned, not everything.

B: The Product Owner doesn’t control the Sprint Backlog.

C: Full task definition isn’t required; it emerges during the Sprint.

The Scrum Guide states that the Sprint Backlog is owned by the Developers, who are responsible for planning and executing the work to achieve the Sprint Goal. If they realize they’ve over-committed, they must adjust the Sprint Backlog. However, since the Product Owner is accountable for maximizing value and managing the Product Backlog, their involvement is critical to ensure adjustments align with value delivery and the Sprint Goal. The Scrum Guide notes: "The Product Owner may influence the Developers by helping them understand and select trade-offs." Option A includes a non-existent "project manager" role in Scrum, making it incorrect. Option C involves stakeholders, who are not part of mid-Sprint adjustments (they provide feedback at the Sprint Review). Option D excludes the Product Owner, which is insufficient given their role. Thus, B is correct.

A Sprint is a fixed-length, time-boxed event that ends when its duration expires, regardless of work completion. The Scrum Guide states: "Sprints are the heartbeat of Scrum, where ideas are turned into value. They are fixed length events of one month or less to create consistency." The end is determined by the time-box, not by acceptance, quality standards, or task completion.

A: Product Owner acceptance occurs at Sprint Review, but doesn’t define Sprint end.

B: The Definition of "Done" applies to the Increment, not the Sprint’s duration.

C: Correct—the time-box dictates the end.

The Sprint Retrospective involves the entire Scrum Team—Product Owner, Scrum Master, and Developers—to inspect and improve. The Scrum Guide states: "The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done." The Product Owner’s presence is mandatory because they are part of the team, contributing to discussions on collaboration and process (e.g., backlog refinement).

A: Optional attendance contradicts the team-wide focus.

C: Exclusion is incorrect; it’s not just for Developers.

Scrum does not mandate specific tools like burndown charts; it focuses on outcomes (e.g., a "Done" Increment) rather than prescriptive practices. The Scrum Guide mentions progress tracking as optional: "Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism."

A: False—burndown charts are optional.

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 Scrum Guide mandates 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 the Scrum Guide requires full integration regardless. Option D correctly emphasizes the need for a cohesive, inspectable Increment, making it the best answer.

In Scrum, Sprints are continuous and fixed-length, with no gaps allowed between them. The Scrum Guide explicitly states: "A new Sprint starts immediately after the conclusion of the previous Sprint." This ensures a consistent cadence of delivery and adaptation, a cornerstone of Scrum’s empirical process. Let’s examine each option:

A (Not enough "Ready" items): The Product Backlog can be refined incrementally; a lack of "Ready" items doesn’t justify delaying a Sprint. The team can start with what’s available and refine further during the Sprint.

B (No Sprint Goal): The Sprint Goal is defined during Sprint Planning, not beforehand. Its absence pre-Sprint isn’t a valid delay reason.

C: This aligns with the Scrum Guide ’s mandate for immediate succession, making it correct.

D (QA needs more time): Scrum rejects external dependencies like a separate QA department; the Developers must deliver a "Done" Increment within the Sprint. Delaying contradicts this.

The Scrum Guide describes 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.

The Product Backlog is emergent and doesn’t need to be fully "ready" before Sprint Planning. The Scrum Guide states: "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.

As Scrum Teams mature, they improve quality and effectiveness. The Scrum Guide implies 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.

The Product Owner maximizes value, per the Scrum Guide : "The Product Owner is accountable for maximizing the value of the product."

C: Ordering the Product Backlog by value ensures high-priority items are addressed first, a core responsibility: "Ordering Product Backlog items."

D: Frequent releases test assumptions empirically, aligning with Scrum’s inspection and adaptation pillars.

A: Value Poker is a technique, not a fundamental principle, and isn’t universally required.

The Product Owner’s role during a Sprint centers on maximizing value through Product Backlog management and stakeholder engagement, as outlined in the Scrum Guide .

C: Refinement is a key activity: "The Product Owner may do the above work [Product Backlog management], or may delegate the responsibility to others. Regardless, the Product Owner remains accountable." Collaborating with Developers ensures items are clear and "Ready."

E: Stakeholder collaboration is critical: "The Product Owner is also accountable for effective Product Backlog management, which includes... representing the needs of many stakeholders in the Product Backlog."

A: Attending every Daily Scrum isn’t typical; it’s the Developers’ event, and the Product Owner attends only if needed.

B: The Developers manage their work plan (Sprint Backlog); the Product Owner doesn’t update it.

The Scrum Guide allows 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.

Stakeholder feedback isn’t limited to the Sprint Review. The Scrum Guide encourages ongoing collaboration: "The Product Owner is also accountable for effective Product Backlog management, which includes... representing the needs of many stakeholders." Feedback can occur during refinement, informal discussions, or releases, not just the Sprint Review, which is a formal inspection point: "The Scrum Team presents the results of their work to key stakeholders."

A: False—feedback is continuous.

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.

The Sprint Goal and the Sprint Backlog are both outcomes of Sprint Planning, making this statement true. According to the Scrum Guide , Sprint Planning is an event where the Scrum Team collaborates to define the work to be performed during the Sprint. The Sprint Goal is a single objective set for the Sprint, providing focus and coherence to the work selected. It is crafted collaboratively by the Product Owner, Developers, and Scrum Master during Sprint Planning. Simultaneously, the Sprint Backlog is created, consisting of the Product Backlog items selected for the Sprint plus a plan to deliver them, aligned with the Sprint Goal. The Scrum Guide states: "Sprint Planning initiates the Sprint by laying out the work to be performed... This resulting plan is created by the collaborative work of the entire Scrum Team." Thus, both the Sprint Goal and Sprint Backlog emerge from this event, confirming option A as correct.

The Product Owner’s primary duty is to maximize value, with flexibility in how they order the Product Backlog. The Scrum Guide states: "The Product Owner is accountable for effective Product Backlog management, which includes... Ordering Product Backlog items." Option E gives the Product Owner latitude to consider value, effort, risk, dependencies, or other factors relevant to the Product Goal.

A, C: Prioritizing effort or cost over value is too narrow.

B: Cohesion is a Developer concern, not the Product Owner’s primary focus.

The Definition of "Done" is a team or organizational standard, not the Scrum Master’s sole responsibility. The Scrum Guide states: "If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product."

A: Accurate—it defines completion.

B: True—it can differ by context or product.

C: Least accurate—the Scrum Team or organization defines it, not just the Scrum Master.

The Product Owner has explicit accountability for product value. The Scrum Guide states: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

A: The Scrum Master ensures Scrum effectiveness, not value.

B: Correct—value maximization is their role.