The Sprint Review is the designated formal event within the Scrum framework for inspecting the outcome of the Sprint. During this meeting, the Development Team demonstrates the work completed—the product Increment—to the Product Owner and other key stakeholders. It is at this point that the Product Owner inspects the completed user stories against the acceptance criteria and the Definition of Done. The Product Owner's acceptance of the demonstrated work serves as the formal confirmation to the entire Scrum Team that the stories are completed to their satisfaction.

B. During the sprint retrospective: This event is for the Scrum Team to inspect its own process and identify improvements, not to review or accept the product Increment.

C. During the sprint backlog review: This is not a formal Scrum event. The Sprint Backlog is a plan that is inspected daily during the Daily Scrum, but this is for progress tracking, not formal acceptance.

D. During the sprint user acceptance test: User acceptance testing is an activity, not a formal Scrum event. While it is part of verifying a story, the formal acceptance of the Sprint's outcome occurs in the Sprint Review.

---

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org. In the "Sprint Review" section

it states

"The purpose of the Sprint Review is to inspect the outcome of the Sprint... The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed." This inspection by the Product Owner and stakeholders is where formal acceptance occurs.

2. Hohl

P.

et al. (2018). A Large-Scale Study on the Suitability of Scrum in a Pre-development Phase. In: Product-Focused Software Process Improvement. PROFES 2018. Lecture Notes in Computer Science

vol 11271. Springer

Cham. https://doi.org/10.1007/978-3-030-03673-72. The paper describes the Scrum events

noting the Sprint Review as the meeting where "the development team presents the results to the stakeholders and the product owner

who decides whether to release the increment" (Section 2.1

Scrum Framework). This decision is the formal confirmation.

3. University of California

Berkeley. (n.d.). CS 169 Software Engineering

Lecture 10: Agile/Scrum. Retrieved from course materials. The lecture notes describe the Sprint Review as the event where the team "Present[s] the result to Product Owner

who decides whether to release it." This decision represents the formal acceptance of the completed work.