Important GAQM CASPO-001 CASPO Exam Questions

Answer: C

Explanation:

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.

Answer: C

Explanation:

The Scrum Guide describes the Sprint Retrospective as an event where the Scrum Team inspects itself and plans improvements, with the Scrum Master playing a dual role: 'The Scrum Master participates as a peer team member in the Sprint Retrospective... and ensures that the event takes place and is positive and productive.' Option C captures this---participating as a team member and facilitating when needed. Option A (scribe) is too narrow and not required. Option B (prioritizing) is a team decision, not the Scrum Master's alone. Option D (reporting to management) violates Scrum's team autonomy. Thus, C is correct.

Answer: C

Explanation:

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

Explanation:

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: A

Explanation:

The Definition of 'Done' is a shared standard, often set by the organization, but defaults to the Scrum Team if no broader standard exists. The Scrum Guide states: '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. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.'

A: Correct---organizational standards take precedence, otherwise the Scrum Team defines it.

B: Collaboration occurs, but it's not just a 'common denominator.'

C, D: Neither the Product Owner nor Scrum Master owns it alone.

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 a Definition of Done appropriate for the product.' (Section: 'Definition of Done')

Thus, A is correct.