Free Practice Questions for GAQM CASPO-001 Exam

TheScrum Guideexplains the Definition of "Done" as "a formal description of the state of the Increment when it meets the quality measures required for the product":

A:It increases transparency by making quality expectations visible to all.

B:It creates a shared understanding of "complete" across the Scrum Team.

In Scrum, a time-box is a maximum duration for an event, ensuring focus and efficiency. TheScrum Guidestates: "All events are time-boxed, meaning they have a maximum duration." For example, Sprint Planning is 8 hours max, Daily Scrum is 15 minutes, etc. The event can end earlier if its purpose is achieved, but it cannot exceed the time-box. Option A refers to scheduling, not time-boxing. Option B implies a deadline, not a duration limit. Option C suggests a minimum, which isn’t part of the definition. Thus, D is correct.

The Product Owner maximizes value, per theScrum Guide: "The Product Owner is accountable for maximizing the value of the product."

C:Ordering the Product Backlog by value ensures high-priority items are addressed first, a core responsibility: "Ordering Product Backlog items."

D:Frequent releases test assumptions empirically, aligning with Scrum’s inspection and adaptation pillars.

A:Value Poker is a technique, not a fundamental principle, and isn’t universally required.

TheScrum Guidedescribes 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.

TheScrum Guidestates: "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.

The Sprint Retrospective is a mandatory event for the entire Scrum Team, including the Product Owner. TheScrum Guidespecifies: "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." As a Scrum Team member, the Product Owner’s participation is essential for team-wide reflection and improvement.

A:False—attendance isn’t optional.

Management has a role in supporting Scrum, though not within the Scrum Team. TheScrum Guidenotes: "Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing... Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows." Management provides resources, removes impediments, and sets organizational context, but doesn’t manage the team directly.

A:False—management supports externally.

The Sprint Retrospective involves the entire Scrum Team—Product Owner, Scrum Master, and Developers—to inspect and improve. TheScrum Guidestates: "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.

Time-boxed Sprints in Scrum enable rapid feedback loops by delivering usable Incrementsregularly. TheScrum Guideemphasizes: "Sprints are the heartbeat of Scrum, where ideas are turned into value." Option B aligns with this—frequent releases to the market allow the Product Owner to gather real user and market feedback, validating assumptions and adjusting the Product Backlog.

A:Finishing Sprint Backlog work is internal; it doesn’t guarantee market feedback.

C:Delaying Sprint end for testing contradicts the fixed time-box and "Done" requirement within the Sprint.

D:Reports are informational, not direct market feedback.

The Definition of "Done" is a team or organizational standard, not the Scrum Master’s sole responsibility. TheScrum Guidestates: "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.