Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Every Scrum Team should have: (Choose the best answer)
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.
Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose the best two answers)
The Scrum Guide states: 'The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness' by inspecting the last Sprint's people, processes, and tools.
D: The next Sprint's Sprint Backlog is planned in Sprint Planning, not the Retrospective, making it inappropriate.
E: Product Backlog value is the Product Owner's domain, discussed in refinement or Sprint Review, not the Retrospective, which focuses on team improvement.
Options A, B, and C (work processes, team dynamics, Definition of 'Done') are valid Retrospective topics as they relate to quality and effectiveness. Thus, D and E are not appropriate.
The purpose of a Sprint Retrospective is for the Scrum Team to: (Choose the best answer)
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.
What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Scrum Teams? (Choose the best answer)
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.
How does an organization know that a product built through Scrum is successful? (Choose the best answer)
Success in Scrum is tied to value delivery, not internal metrics. Option B---frequent releases with KPI updates---aligns with Scrum's empirical nature: 'Scrum is founded on empiricism and lean thinking.' Real-world feedback refines the Product Backlog, ensuring success.
A: Velocity is an internal capacity metric, not a success indicator.
C: Time variance is irrelevant to value.
D: Acceptance at Sprint Review is a step, but not the ultimate measure of market success.
Exact Extract from Scrum Guide: 'The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation... The Product Owner discusses the Product Backlog as it stands.' (Section: 'Sprint Review') B extends this to market validation.
Thus, B is correct.
80 questions covering all exam domains, starting from $20
6 domains from the GAQM CASPO-001 exam outline, with approximate weightings. Every sample question above is tagged with the domain it comes from
Covers the key responsibilities of a Product Owner in an Agile Scrum environment. Candidates learn the core duties that define this role within Scrum teams.
Highlights the process of defining and communicating the product vision to stakeholders. Product Owners must articulate a clear direction that aligns the team and business goals.
Focuses on managing and maintaining the product backlog, a key responsibility of the Product Owner. Includes prioritization, refinement, and ensuring backlog items are clear and actionable.
Covers how to plan and execute product releases effectively, ensuring that they meet customer needs and business objectives. Addresses scheduling, dependencies, and stakeholder communication around releases.
Focuses on the role of the Product Owner in Sprint planning and other Scrum ceremonies, such as daily stand-ups, Sprint reviews, and retrospectives. Emphasizes effective participation in each Scrum event.
Addresses the transition into the Product Owner role, including understanding the responsibilities and adapting to the dynamic nature of Agile environments. Helps new Product Owners understand the learning curve and common challenges.
Common questions about the exam itself
