GAQM CASPO-001 Practice Exams
Last updated on Oct 22,2026- Exam Code: CASPO-001
- Exam Name: Certified Agile Scrum Product Owner (CASPO)
- Certification Provider: GAQM
- Latest update: Oct 22,2026
Question #51
When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint? (Choose the best answer)
- A . No, that is far too hard and must be done in a hardening Sprint.
- B . No, each Scrum Team stands alone.
- C . Yes, but only for Scrum Teams whose work has dependencies.
- D . Yes, otherwise the Product Owners and stakeholders may not be able to accurately inspect what is done.
Correct Answer: D
D
Explanation:
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.
Reference: Scrum Guide (2020), Section: "The Increment."
D
Explanation:
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.
Reference: Scrum Guide (2020), Section: "The Increment."
Question #52
Every Scrum Team should have: (Choose the best answer)
- A . The competencies and skills needed to deliver a Done Increment in a Sprint.
- B . At least one representative from each major software engineering discipline (like QA, Dev, UX).
- C . One Lead Developer and no more than eight other members.
Correct Answer: A
A
Explanation:
The Scrum Guide emphasizes that a Scrum Team must be cross-functional, meaning it has all the competencies and skills necessary to create a "Done" Increment within a Sprint without relying on external resources.
Option A aligns directly with this principle: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers… They are cross-functional, meaning the members have all the skills necessary to create value each Sprint." Option B, while suggesting a structured representation from disciplines, is too prescriptive and not a Scrum requirement―Scrum does not mandate specific roles like QA or UX within the Developers.
Option C imposes a rigid team structure (one Lead Developer and a maximum of eight others), which contradicts Scrum’s flexibility in team composition (typically 10 or fewer total, but no specific roles or limits beyond that are mandated). Thus, A is the best answer, focusing on capability rather than structure.
Reference: Scrum Guide (2020), Section: "The Scrum Team."
A
Explanation:
The Scrum Guide emphasizes that a Scrum Team must be cross-functional, meaning it has all the competencies and skills necessary to create a "Done" Increment within a Sprint without relying on external resources.
Option A aligns directly with this principle: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers… They are cross-functional, meaning the members have all the skills necessary to create value each Sprint." Option B, while suggesting a structured representation from disciplines, is too prescriptive and not a Scrum requirement―Scrum does not mandate specific roles like QA or UX within the Developers.
Option C imposes a rigid team structure (one Lead Developer and a maximum of eight others), which contradicts Scrum’s flexibility in team composition (typically 10 or fewer total, but no specific roles or limits beyond that are mandated). Thus, A is the best answer, focusing on capability rather than structure.
Reference: Scrum Guide (2020), Section: "The Scrum Team."
Question #53
Who is responsible for clearly expressing Product Backlog Items? (Choose the best answer)
- A . The Product Owner.
- B . The Scrum Master.
- C . The Scrum Master, or the Scrum Master may have the Developers do it.
- D . The business analyst who represents the Product Owner in the Developers.
Correct Answer: A
A
Explanation:
The Scrum Guide explicitly states: "The Product Owner is accountable for effective Product Backlog
management, which includes… clearly expressing Product Backlog items." This responsibility ensures that the items reflect stakeholder needs and are understandable to the Developers.
Option B is incorrect―the Scrum Master facilitates and coaches, not manages the Product Backlog.
Option C is wrong―neither the Scrum Master nor Developers are accountable for this; it’s the Product Owner’s role.
Option D introduces a "business analyst" role, which isn’t part of Scrum; the Product Owner directly handles this duty without delegation to a proxy. Thus, A is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
A
Explanation:
The Scrum Guide explicitly states: "The Product Owner is accountable for effective Product Backlog
management, which includes… clearly expressing Product Backlog items." This responsibility ensures that the items reflect stakeholder needs and are understandable to the Developers.
Option B is incorrect―the Scrum Master facilitates and coaches, not manages the Product Backlog.
Option C is wrong―neither the Scrum Master nor Developers are accountable for this; it’s the Product Owner’s role.
Option D introduces a "business analyst" role, which isn’t part of Scrum; the Product Owner directly handles this duty without delegation to a proxy. Thus, A is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
Question #54
Why would the Product Owner concern themselves with technical debt? (Choose the best answer)
- A . The total cost of ownership (TCO) of the product will be impacted if technical debt is present and grows
- B . The Scrum Master is responsible for technical debt management
- C . They wouldn’t, it is an issue for Developers
Correct Answer: A
A
Explanation:
Technical debt affects product value, a Product Owner’s core concern. The Scrum Guide doesn’t explicitly mention technical debt, but the Product Owner’s accountability for "maximizing the value of the product" implies considering factors like TCO, which rises with debt due to rework or maintenance costs.
A: Correct―debt impacts long-term value and cost.
B: The Scrum Master facilitates, not manages debt.
C: False―the Product Owner must care about value impacts.
Exact Extract from Scrum Guide: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." (Section: "The Product Owner") Debt reduces value, linking to A.
Thus, A is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
A
Explanation:
Technical debt affects product value, a Product Owner’s core concern. The Scrum Guide doesn’t explicitly mention technical debt, but the Product Owner’s accountability for "maximizing the value of the product" implies considering factors like TCO, which rises with debt due to rework or maintenance costs.
A: Correct―debt impacts long-term value and cost.
B: The Scrum Master facilitates, not manages debt.
C: False―the Product Owner must care about value impacts.
Exact Extract from Scrum Guide: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." (Section: "The Product Owner") Debt reduces value, linking to A.
Thus, A is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
Question #55
When can the Product Backlog be updated? (Choose the best answer)
- A . Only after a Sprint Review if agreed to by the stakeholders
- B . Only during Product Backlog refinement sessions if the Product Owner is present
- C . Never, unless agreed to by the change request
- D . At any time when done by the Product Owner or at the Product Owner’s discretion
Correct Answer: D
D
Explanation:
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."
D
Explanation:
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."
Question #56
What three factors are best considered when establishing the Sprint length? (Choose the best three answers)
- A . The ability to go to market with a product release.
- B . Sprints must have the same length throughout an organization.
- C . The frequency at which team formation can be changed.
- D . The level of uncertainty over the technology to be used.
- E . The risk of being disconnected from the stakeholders.
Correct Answer: A, D, E
A, D, E
Explanation:
Sprint length in Scrum is a critical decision that impacts the team’s ability to deliver value and adapt. The Scrum Guide states 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.
E (The risk of being disconnected from the stakeholders): Shorter Sprints ensure frequent stakeholder engagement (e.g., via Sprint Reviews), reducing this risk.
Option B is incorrect because Scrum does not require uniform Sprint lengths across an organization― each team can choose what works best.
Option C is irrelevant, as team formation changes are not tied to Sprint length in Scrum. Thus, A, D, and E are the best factors.
Reference: Scrum Guide (2020), Section: "Sprint."
A, D, E
Explanation:
Sprint length in Scrum is a critical decision that impacts the team’s ability to deliver value and adapt. The Scrum Guide states 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.
E (The risk of being disconnected from the stakeholders): Shorter Sprints ensure frequent stakeholder engagement (e.g., via Sprint Reviews), reducing this risk.
Option B is incorrect because Scrum does not require uniform Sprint lengths across an organization― each team can choose what works best.
Option C is irrelevant, as team formation changes are not tied to Sprint length in Scrum. Thus, A, D, and E are the best factors.
Reference: Scrum Guide (2020), Section: "Sprint."
Question #57
Which is NOT a Scrum role? (Choose the best answer)
- A . Product Owner
- B . Developers
- C . Project Manager
- D . Scrum Master
Correct Answer: C
C
Explanation:
Scrum defines three roles: Product Owner, Scrum Master, and Developers. The Scrum Guide states:
"The Scrum Team consists of one Scrum Master, one Product Owner, and Developers." Project Manager (C) is a traditional role absent in Scrum, where responsibilities are distributed among the Scrum Team.
A, B, D: These are explicit Scrum roles.
C: Not a Scrum role.
Exact Extract from Scrum Guide: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies." (Section: "The Scrum Team")
Thus, C is correct.
Reference: Scrum Guide (2020), Section: "The Scrum Team."
C
Explanation:
Scrum defines three roles: Product Owner, Scrum Master, and Developers. The Scrum Guide states:
"The Scrum Team consists of one Scrum Master, one Product Owner, and Developers." Project Manager (C) is a traditional role absent in Scrum, where responsibilities are distributed among the Scrum Team.
A, B, D: These are explicit Scrum roles.
C: Not a Scrum role.
Exact Extract from Scrum Guide: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies." (Section: "The Scrum Team")
Thus, C is correct.
Reference: Scrum Guide (2020), Section: "The Scrum Team."
Question #58
What is the Product Owner accountable for in Scrum? (Choose the best answer)
- A . Describing an Increment at the Sprint Planning and making sure that the Developers deliver it by the end of the Sprint
- B . Creating and sustaining a Product Backlog that maximizes value and represents the needs of the stakeholders
- C . Refining the top-level Product Backlog items until they are ready to be handed over to the Developers
- D . Writing the User Stories so they are understandable to stakeholders
Correct Answer: B
B
Explanation:
The Product Owner’s core accountability is maximizing value through the Product Backlog. The Scrum Guide states: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." Option B encapsulates this fully.
A: The Developers deliver the Increment; the Product Owner doesn’t ensure it.
C: Refinement is part of management, but not the sole accountability.
D: Writing User Stories is a technique, not the overarching duty.
Exact Extract from Scrum Guide: "The Product Owner is accountable for effective Product Backlog management, which includes: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood." (Section: "The Product Owner")
Thus, B is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
B
Explanation:
The Product Owner’s core accountability is maximizing value through the Product Backlog. The Scrum Guide states: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." Option B encapsulates this fully.
A: The Developers deliver the Increment; the Product Owner doesn’t ensure it.
C: Refinement is part of management, but not the sole accountability.
D: Writing User Stories is a technique, not the overarching duty.
Exact Extract from Scrum Guide: "The Product Owner is accountable for effective Product Backlog management, which includes: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood." (Section: "The Product Owner")
Thus, B is correct.
Reference: Scrum Guide (2020), Section: "The Product Owner."
Question #59
It is mandatory for the Product Owner to monitor and share progress of Product Backlog through: (Choose the best answer)
- A . A Product or Release burn-down chart
- B . A Value burn-up chart
- C . A Gantt chart
- D . Any projective practice based on trends of work completed and upcoming work
- E . A Sprint Review acceptance report
Correct Answer: D
D
Explanation:
The Scrum Guide requires transparency but doesn’t mandate specific tools: "The Product Owner is accountable for… ensuring that the Product Backlog is transparent, visible, and understood." Progress tracking is necessary, but the method is flexible.
D: This allows any trend-based practice (e.g., burn-downs, burn-ups), fitting Scrum’s adaptability. A, B: Useful but not mandatory; Scrum doesn’t prescribe them.
C: Gantt charts are traditional, not Scrum-aligned.
E: Sprint Review focuses on the Increment, not backlog progress reporting.
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") Monitoring progress is implied, not tool-specific.
Thus, D is correct.
Reference: Scrum Guide (2020), Section: "Product Backlog."
D
Explanation:
The Scrum Guide requires transparency but doesn’t mandate specific tools: "The Product Owner is accountable for… ensuring that the Product Backlog is transparent, visible, and understood." Progress tracking is necessary, but the method is flexible.
D: This allows any trend-based practice (e.g., burn-downs, burn-ups), fitting Scrum’s adaptability. A, B: Useful but not mandatory; Scrum doesn’t prescribe them.
C: Gantt charts are traditional, not Scrum-aligned.
E: Sprint Review focuses on the Increment, not backlog progress reporting.
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") Monitoring progress is implied, not tool-specific.
Thus, D is correct.
Reference: Scrum Guide (2020), Section: "Product Backlog."
Question #60
What are the purposes of the Definition of "Done"? (Choose the best two answers)
- A . Help ensure the Increment is releasable
- B . Provide transparency
- C . Document the Sprint Goal
- D . Ensure unit testing occurs
Correct Answer: A, B
A, B
Explanation:
The Definition of "Done" ensures quality and clarity. The Scrum Guide states: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."
A: It ensures the Increment is usable/releasable: "In order to provide value, the Increment must be
usable."
B: It provides transparency by setting a shared standard: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed."
C: The Sprint Goal is separate, defined in Sprint Planning.
D: Unit testing is a practice, not a purpose of "Done."
Exact Extract from Scrum Guide: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment… In order to provide value, the Increment must be usable." (Section: "Definition of Done")
Thus, A and B are correct.
Reference: Scrum Guide (2020), Section: "Definition of Done."
A, B
Explanation:
The Definition of "Done" ensures quality and clarity. The Scrum Guide states: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."
A: It ensures the Increment is usable/releasable: "In order to provide value, the Increment must be
usable."
B: It provides transparency by setting a shared standard: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed."
C: The Sprint Goal is separate, defined in Sprint Planning.
D: Unit testing is a practice, not a purpose of "Done."
Exact Extract from Scrum Guide: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment… In order to provide value, the Increment must be usable." (Section: "Definition of Done")
Thus, A and B are correct.
Reference: Scrum Guide (2020), Section: "Definition of Done."