GAQM CASPO-001 Certified Agile Scrum Product Owner Exam CASPO Exam Practice Test

Answer : D, E

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.

E: Informing the Product Owner, starting the Sprint, and monitoring progress reflects collaboration and adaptability, keeping the Sprint on track.

Option A (overtime) contradicts Scrum's sustainable pace principle. Option B (recruiting) isn't feasible mid-planning and disrupts team stability. Option C (canceling) is an extreme measure only the Product Owner can initiate, not the Developers, and only for specific reasons (e.g., Sprint Goal obsolescence). Thus, D and E are valid.

Answer : A, D, E

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.

Answer : B

The Scrum Guide clarifies that the definition of 'Done' is a shared commitment created by the Scrum Team: 'The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.' While the Product Owner defines what goes into the Increment (via the Product Backlog), the definition of 'Done' is a collaborative effort, often driven by the Developers' technical expertise and organizational standards, with input from the Product Owner on value and quality expectations. Option A incorrectly gives the Product Owner sole authority, while B correctly reflects the team's collective responsibility, with the Product Owner as a contributor, not the final arbiter.

Answer : C

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.

Answer : B

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

Answer : C

The Sprint Retrospective is a key Scrum event focused on continuous improvement. The Scrum Guide defines its purpose explicitly as an opportunity for the Scrum Team (Product Owner, Scrum Master, and Developers) to reflect on the past Sprint and identify actionable ways to enhance their effectiveness and quality in the next Sprint. Option C---'Inspect how the last Sprint went and plan improvements for the next Sprint'---accurately captures this intent, aligning with Scrum's empirical pillars of inspection and adaptation. Let's evaluate all options:

A (Review stories planned for the next Sprint and provide estimates): This pertains to Sprint Planning or Product Backlog refinement, not the Retrospective. The Retrospective focuses on past performance, not future planning of specific stories or estimation.

B (Demonstrate completed User Stories to the Product Owner): This describes the Sprint Review, where the Increment is showcased to stakeholders, not the Retrospective, which is an internal team event.

C: Correct---the Retrospective is about inspecting the last Sprint (e.g., processes, interactions, tools) and adapting by planning improvements, making it the best answer.

D (The Product Owner): This is incomplete and nonsensical as a purpose; it likely resulted from an OCR error in the original document. The Product Owner participates but isn't the purpose.

The original document's incomplete option C was a typo or truncation error (ending at 'This study wou'). By restoring the intended meaning based on Scrum principles, C becomes the clear and correct choice.

Exact Extract from Scrum Guide: 'The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved... The Sprint Retrospective concludes the Sprint.' (Section: 'Sprint Retrospective')

This extract confirms that the Retrospective's purpose is inspection and improvement planning, precisely matching option C.

Answer : B

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.