When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint? (Choose the best answer)
Answer(s): D
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.
Scrum Guide (2020), Section: "The Increment."
During a Sprint Retrospective, for what is the Scrum Master responsible? (Choose the best answer)
Answer(s): C
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.
Scrum Guide (2020), Section: "Sprint Retrospective."
Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose the best two answers)
Answer(s): D,E
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.
What is typical work for a Product Owner in a Sprint? (Choose the best two answers)
Answer(s): C,E
The Scrum Guide outlines the Product Owner's responsibilities as maximizing value through Product Backlog management, which includes:C: "Developing and explicitly communicating the Product Goal" and refining the Product Backlog with Developers to ensure clarity and readiness.E: "Representing stakeholders" by collaborating with them to align the Product Backlog with their needs.Option A is incorrect--the Product Owner may attend Daily Scrum if needed, but it's not typical or required; it's the Developers' event. Option B is wrong--the Developers manage their work plan (Sprint Backlog). Option D (financial reporting on hours) isn't a Scrum responsibility. Thus, C and E are typical.
Scrum Guide (2020), Section: "The Product Owner."
Which phrase best describes a Product Owner? (Choose the best answer)
Answer(s): B
The Scrum Guide defines the Product Owner as "accountable for maximizing the value of the product resulting from the work of the Scrum Team." Option B (Value optimizer) encapsulates this core focus on value delivery. Option A (Requirements engineer) is too narrow--while they manage requirements, their role transcends engineering to strategic vision. Option C (Team manager) is incorrect--they don't manage the team; the Scrum Master supports team self-management. Option D (Go-between) understates their authority; they actively shape the product, not just relay information. Thus, B is the best description.
Post your Comments and Discuss GAQM CASPO-001 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CASPO-001 content, but please register or login to continue.