GAQM CASPO-001 Exam Dumps

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.

D: Correct---it evolves with maturity.

Exact Extract from Scrum Guide: 'The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product... If it is not an organizational standard, the Scrum Team must create [it].' (Section: 'Definition of Done')

Thus, C is correct.

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.

The Scrum Guide defines the Scrum Team as consisting of three roles: 'The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.' Option A (Developers) is the group responsible for building the Increment. Option D (Product Owner) manages the Product Backlog and value delivery. Option E (Scrum Master) facilitates Scrum adoption and team effectiveness. Options B (Users) and C (Customers) are external stakeholders, not Scrum Team roles---they interact with the product but aren't part of the team. Thus, A, D, and E are the correct roles.

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.

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.