"Sprint 0" is a concept from pre-Scrum practices and isn’t part of the official framework. The Scrum Guide mandates 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."

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 Definition of "Done" ensures quality and clarity. The Scrum Guide states: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."

A: It ensures the Increment is usable/releasable: "In order to provide value, the Increment must be usable."

B: It provides transparency by setting a shared standard: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed."

C: The Sprint Goal is separate, defined in Sprint Planning.

Self-organization in Scrum means the Developers have autonomy over how they deliver the Sprint Goal. The Scrum Guide states: "The Developers... are self-managing, meaning they internally decide who does what, when, and how." Option A aligns with this—choosing how to accomplish work is their domain. Option B is incorrect; the Product Owner orders the Product Backlog. Option C is wrong; the Product Owner invites stakeholders to the Sprint Review. Option D is partially true—Sprint length is set by the Scrum Team collaboratively, not just the Developers, and is typically fixed once established. Option E is false; release decisions are the Product Owner’s responsibility. Thus, A is the best answer.

The Sprint Retrospective is an event for the entire Scrum Team, including the Scrum Master, to inspect and improve their processes. The Scrum Guide explicitly states that the Scrum Master participates as a peer: "The Scrum Master participates as a peer team member in the Sprint Retrospective from the accountability over the Scrum Team’s effectiveness." This ensures a collaborative review of the Sprint, including the Scrum Master’s facilitation role.

A: True—the Scrum Master is a full participant.

The Scrum Guide defines 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 Sprint Retrospective is a key Scrum event focused on continuous improvement. The Scrum Guide defines its purpose explicitly as an opportunity for the Scrum Team (Product Owner, Scrum Master, and Developers) to reflect on the past Sprint and identify actionable ways to enhance their effectiveness and quality in the next Sprint. Option C—"Inspect how the last Sprint went and plan improvements for the next Sprint"—accurately captures this intent, aligning with Scrum’s empirical pillars of inspection and adaptation. Let’s evaluate all options:

A (Review stories planned for the next Sprint and provide estimates): This pertains to Sprint Planning or Product Backlog refinement, not the Retrospective. The Retrospective focuses on past performance, not future planning of specific stories or estimation.

B (Demonstrate completed User Stories to the Product Owner): This describes the Sprint Review, where the Increment is showcased to stakeholders, not the Retrospective, which is an internal team event.

C: Correct—the Retrospective is about inspecting the last Sprint (e.g., processes, interactions, tools) and adapting by planning improvements, making it the best answer.

The Product Owner has explicit accountability for product value. The Scrum Guide states: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

A: The Scrum Master ensures Scrum effectiveness, not value.

B: Correct—value maximization is their role.

Stakeholder feedback isn’t limited to the Sprint Review. The Scrum Guide encourages ongoing collaboration: "The Product Owner is also accountable for effective Product Backlog management, which includes... representing the needs of many stakeholders." Feedback can occur during refinement, informal discussions, or releases, not just the Sprint Review, which is a formal inspection point: "The Scrum Team presents the results of their work to key stakeholders."

A: False—feedback is continuous.

The Scrum Guide defines Scrum as "a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems." It provides roles, events, and artifacts but intentionally avoids prescribing detailed "how-to" processes for building software (e.g., coding practices, tools). This distinguishes it from a methodology, which offers specific steps. Scrum focuses on "what" (e.g., deliver an Increment) and leaves "how" to the team’s discretion, making the statement false. Thus, B is correct.