CASPO-001 Practice Questions

Success in Scrum is tied to value delivery, not internal metrics. Option B—frequent releases with KPI

updates—aligns with Scrum’s empirical nature: "Scrum is founded on empiricism and lean thinking."

Real-world feedback refines the Product Backlog, ensuring success.

A: Velocity is an internal capacity metric, not a success indicator.

C: Time variance is irrelevant to value.

D: Acceptance at Sprint Review is a step, but not the ultimate measure of market success.

Exact Extract from Scrum Guide: "The Sprint Review is a working session and the Scrum Team should

avoid limiting it to a presentation... The Product Owner discusses the Product Backlog as it stands."

(Section: "Sprint Review") B extends this to market validation.

Thus, B is correct.

Reference: Scrum Guide (2020), Sections: "Scrum Theory," "Sprint Review."

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.

D: Use Case

are too specific; the backlog contains items, not document links.

Exact Extract from Scrum Guide: "The Product Backlog is an emergent, ordered list of what is needed

to improve the product. It is the single source of work undertaken by the Scrum Team." (Section:

"Product Backlog")

Thus, A is correct.

Reference: Scrum Guide (2020), Section: "Product Backlog."

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.

D, F: Resource availability is a constraint, not the sole criterion.

Exact Extract from Scrum Guide: "The Product Owner may influence the Developers by helping them

understand and select trade-offs, but those who will perform the work are the final judge as to what

goes into the Increment." (Section: "Sprint Planning") E reflects this holistic approach.

Thus, E is correct.

Reference: Scrum Guide (2020), Section: "The Product Owner."

The Sprint Backlog is collectively owned by the Developers, not assigned to individuals. The Scrum

Guide defines 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.

D: The Product Owner manages the Product Backlog, not the Sprint Backlog.

Exact Extract from Scrum Guide: "The Sprint Backlog is a plan by and for the Developers. It is

composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what),

as well as an actionable plan for delivering the Increment (how)." (Section: "Sprint Backlog")

Thus, C is correct.

Reference: Scrum Guide (2020), Section: "Sprint Backlog."

A single product has one Product Owner, regardless of the number of teams. The Scrum Guide states:

"The Product Owner is one person, not a committee... Multiple Scrum Teams often work together on

the same product. One Product Backlog is used to describe the upcoming work on the product."

A: Multiple Product Owners fragment accountability.

B: Correct—one Product Owner for one product.

C, D: The number isn’t negotiable in Scrum.

Exact Extract from Scrum Guide: "Multiple Scrum Teams often work together on the same product.

One Product Backlog is used to describe the upcoming work on the product. A Product Backlog is

ordered by the Product Owner." (Section: "Product Backlog")

Thus, B is correct.

Reference: Scrum Guide (2020), Section: "Product Backlog."

The Product Backlog is under the Product Owner’s control and can be updated anytime. The Scrum

Guide states: "The Product Owner is accountable for effective Product Backlog management,"

implying ongoing adjustments as needed.

A: Limiting updates to Sprint Review contradicts its emergent nature.

B: Refinement is a key activity, but updates aren’t restricted to it.

C: A "change request" process isn’t in Scrum.

D: Correct—flexibility is key.

Exact Extract from Scrum Guide: "As long as a product exists, its Product Backlog also exists... The

Product Backlog is dynamic; it constantly changes to identify what the product needs to be

appropriate, competitive, and useful." (Section: "Product Backlog")

Thus, D is correct.

Reference: Scrum Guide (2020), Section: "Product Backlog."

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

Reference: Scrum Guide (2020), Section: "The Developers," "The Scrum Master."

The Scrum Guide states: "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.

Reference: Scrum Guide (2020), Section: "The Product Owner."

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.

Reference: Scrum Guide (2020), Section: "Sprint Planning."

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.

B: This aligns with the team’s collective improvement goal.

Exact Extract from Scrum Guide: "The Sprint Retrospective is an opportunity for the Scrum Team to

inspect itself and create a plan for improvements to be enacted during the next Sprint... The Sprint

Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month

Sprint." (Section: "Sprint Retrospective")

Thus, B is correct.

Reference: Scrum Guide (2020), Section: "Sprint Retrospective."