Free Practice Questions for GAQM CASPO-001 Exam

TheScrum Guiderequires transparency but doesn’t mandate specific tools: "The Product Owner is accountable for... ensuring that the Product Backlog is transparent, visible, and understood." Progress tracking is necessary, but the method is flexible.

D:This allows any trend-based practice (e.g., burn-downs, burn-ups), fitting Scrum’s adaptability.

A, B:Useful but not mandatory; Scrum doesn’t prescribe them.

C:Gantt charts are traditional, not Scrum-aligned.

The Sprint Backlog is a plan that evolves. TheScrum Guidestates: "The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint." At Sprint Planning’s end, it needs enough detail to start, with flexibility to adapt later.

A:Correct—initial work is planned, not everything.

B:The Product Owner doesn’t control the Sprint Backlog.

C:Full task definition isn’t required; it emerges during the Sprint.

The Product Owner is a singular, critical role in Scrum: "The Product Owner is one person, not a committee." Temporary or permanent unavailability requires specific actions:

A:During a Sprint, the Developers’ self-management allows them to proceed toward the Sprint Goal, adjusting with the Product Owner later, per: "The Developers are self-managing, meaning they internally decide who does what, when, and how."

C:Permanent absence means Scrum isn’t being followed without a Product Owner, necessitating a replacement: "For Product Owners to succeed, the entire organization must respect their decisions."

The Daily Scrum is the Developers’ event, not the Scrum Master’s. TheScrum Guidestates: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team... The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum." The Scrum Master’s role is to ensure it happens and is effective, not to attend mandatorily.

A:Documenting impediments is a support task, not a Daily Scrum requirement.

B:Facilitation is optional, only if requested.

C:Burndown charts aren’t mandated; this isn’t their purpose.

The Product Owner and Developers must collaborate closely to maximize value, as per theScrum Guide.

B:Collaboration enables the Product Owner to balance effort (Developer input) and value (their priority), aligning with: "The Product Owner may influence the Developers by helping them understand and select trade-offs."

D:Frequent collaboration ensures the Developers understand stakeholder needs, supporting the creation of a valuable Increment: "The Developers are required to conform to the Definition of Done and to deliver an Increment that meets the Sprint Goal."

A:Separation contradicts Scrum’s emphasis on teamwork; the Scrum Team is cohesive, not siloed.

C:Full-time co-location isn’t required; the Product Owner focuses on value, not technical mastery.

Effort estimation is a technical task owned by the Developers, who execute the work. TheScrum Guidenotes: "The Developers are responsible for... planning how to deliver the Increment." During Sprint Planning and refinement, they estimate effort based on their expertise.

A:Correct—the Developers collectively assess what’s needed to meet the Definition of "Done."

B:PMO isn’t a Scrum role; estimation stays within the team.

TheScrum Guidedefines the Scrum Team as consisting of three roles: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers." Option A (Developers) is the group responsible for building the Increment. Option D (Product Owner) manages the Product Backlog and value delivery. Option E (Scrum Master) facilitates Scrum adoption and team effectiveness. Options B (Users) and C (Customers) are external stakeholders, not Scrum Team roles—they interact with the product but aren’t part of the team. Thus, A, D, and E are the correct roles.

The Product Owner is accountable for ordering the Product Backlog to maximize value. TheScrum Guideallows delegation of tasks but not accountability: "The Product Owner may do the above work, or may delegate the responsibility to others. Regardless, the Product Owner remains accountable." Delegating ordering risks misprioritization, potentially leading to an Increment that doesn’t meet value goals or releasability.

A, B, D:These are unrelated consequences.

"Sprint 0" is a concept from pre-Scrum practices and isn’t part of the official framework. TheScrum Guidemandates that Sprints deliver value: "A Sprint is a time-box of one month or less during which a ‘Done’, usable, and potentially releasable product Increment is created." A preparatory "Sprint 0" for architecture, team building, or backlog creation contradicts this by not producing an Increment.

A, B, C:These may occur outside Sprints, but not as a "Sprint 0."