Free Practice Questions for GAQM CASPO-001 Exam

Scrum does not mandate specific tools like burndown charts; it focuses on outcomes (e.g., a "Done" Increment) rather than prescriptive practices. TheScrum Guidementions progress tracking as optional: "Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism."

A:False—burndown charts are optional.

The Product Backlog is managed solely by the Product Owner, not stakeholders. TheScrum Guideexplains: "The Sprint Review is a working session... The Product Owner discusses the Product Backlog as it stands." Stakeholders provide feedback during the Sprint Review, which the Product Owner may use to adjust priorities, but they don’t directly re-prioritize it.

A:False—stakeholders don’t have this authority.

TheScrum Guideexplicitly states: "The Product Owner is accountable for effective Product Backlog management, which includes... clearly expressing Product Backlog items." This responsibility ensures that the items reflect stakeholder needs and are understandable to the Developers. Option B is incorrect—the Scrum Master facilitates and coaches, not manages the Product Backlog. Option C is wrong—neither the Scrum Master nor Developers are accountable for this; it’s the Product Owner’s role. Option D introduces a "business analyst" role, which isn’t part of Scrum; the Product Owner directly handles this duty without delegation to a proxy. Thus, A is correct.

TheScrum Guideallows the Sprint Backlog to be adjusted during Sprint Planning if the Developers realize the scope exceeds capacity: "If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint."

D:Removing or changing items is valid to align with capacity while preserving the Sprint Goal.