GAQM CASPO-001 Practice Exam Questions & Answers

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.

B: Correct---Scrum supports frequent stakeholder input.

Exact Extract from Scrum Guide: 'The Product Owner ensures that key stakeholders attend the Sprint Review to provide feedback that can then be incorporated into the Product Backlog.' (Section: 'Sprint Review') This implies feedback elsewhere too.

Thus, B is correct.

C: The Scrum Guide defines Scrum as 'a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.' This is a core truth.

D: Scrum's foundation in empirical process control theory (transparency, inspection, adaptation) is explicitly stated in the Scrum Guide: 'Scrum is founded on empiricism and lean thinking.'

E: The Scrum Guide emphasizes that 'each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum.' Altering components risks losing Scrum's benefits.

Option A is false---Scrum is a framework, not a methodology, and cherry-picking parts undermines its integrity. Option B misrepresents Scrum; it's not a tweak on traditional processes but a distinct approach, and it doesn't merely replace Project Managers with self-organization---it eliminates that role entirely. Thus, C, D, and E are correct.

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 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 references 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.

The Developers own the Sprint Backlog and update it as work progresses. The Scrum Guide states: 'The Sprint Backlog is a plan by and for the Developers... As new work is required, the Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated.'

A: The Scrum Master facilitates, not updates.

B: Correct---the Developers manage it.

C, D: Execs and Product Owner don't touch the Sprint Backlog.

Exact Extract from Scrum Guide: 'As work is performed or completed, the estimated remaining work is updated. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint.' (Section: 'Sprint Backlog')

Thus, B is correct.

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.

C: Correct---quality standards rise with maturity.

Exact Extract from Scrum Guide: 'If the Definition of Done for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum... As Scrum Teams mature, it is expected that their definitions of 'Done' will expand.' (Section: 'Definition of Done')

Thus, C is correct.

Effort estimation is a technical task owned by the Developers, who execute the work. The Scrum Guide notes: 'The Developers are responsible for... planning how to deliver the Increment.' During Sprint Planning and refinement, they estimate effort based on their expertise.

A: Correct---the Developers collectively assess what's needed to meet the Definition of 'Done.'

B: PMO isn't a Scrum role; estimation stays within the team.

C: The Product Owner focuses on value and ordering, not technical estimates.

Exact Extract from Scrum Guide: 'The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint... They are self-managing, meaning they internally decide who does what, when, and how.' (Section: 'The Developers') This includes effort estimation.

Thus, A is correct.