Here you can find all the free questions related with GAQM Certified Agile Scrum Product Owner Exam (CASPO-001) exam. You can also find on this page links to recently updated premium files with which you can practice for actual GAQM Certified Agile Scrum Product Owner Exam . These premium versions are provided as CASPO-001 exam practice tests, both as desktop software and browser based application, you can use whatever suits your style. Feel free to try the Certified Agile Scrum Product Owner Exam premium files for free, Good luck with your GAQM Certified Agile Scrum Product Owner Exam .
Question No: 1
MultipleChoice
What happens if the customer no longer wants the feature that the Sprint Goal intended to meet? (Choose the best answer)
Options
Answer AExplanation
If the Sprint Goal becomes obsolete (e.g., a feature is no longer needed), the Product Owner can cancel the Sprint. The Scrum Guide states: 'A Sprint can be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.'
A: Correct---the Product Owner decides.
B: Stakeholders advise, but don't decide.
C: The Scrum Master lacks this authority.
Exact Extract from Scrum Guide: 'A Sprint can be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. Only the Product Owner has the authority to cancel the Sprint.' (Section: 'Sprint Cancellation')
Thus, A is correct.
Question No: 2
MultipleChoice
Every Scrum Team should have: (Choose the best answer)
Options
Answer AExplanation
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.