The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.

During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.

The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

The Scrum Master ensures that the meeting is positive and productive. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

What is a Sprint Retrospective?

A Sprint Retrospective is a Scrum Event that occurs at the end of each Sprint. The purpose of the Sprint Retrospective is to reflect on the passed Sprint and identify areas for improvement in the next Sprint. The Developers, along with the Scrum Master and Product Owner, review their processes and identify ways to work more effectively together. This event provides an opportunity for the Scrum Team to continuously improve and evolve their way of working. The outcome of the Sprint Retrospective is a plan for the next Sprint that includes actions to address the identified improvements.

The Scrum Team is accountable for all product-related activities, as is the Product Owner (as a member of the Scrum Team).

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.

Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones.

"Low priority task items" refer to tasks or requirements that are deemed less important or urgent than other items in a project's backlog. These low-priority tasks are typically placed at the bottom of the product backlog, which is a prioritized list of all the tasks that need to be completed in a project. By placing lower priority tasks at the bottom of the backlog, the project team can focus their attention and resources on higher priority tasks first.

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

Scrum Masters are true leaders who serve the Scrum Team and the larger organization. The Scrum Master serves the Scrum Team in several ways, including:

● Coaching the team members in self-management and cross-functionality;

● Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done;

● Causing the removal of impediments to the Scrum Team’s progress; and,

● Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.

" The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog. "

- The Scrum Guide (TM) of 2020.

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment.

"The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

The moment a Product Backlog item meets the Definition of Done, an Increment is born."

- The Scrum Guide (TM) of 2020

By definition, an increment always meet the Definition of Done.

"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 in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum."

- The Scrum Guide (TM) of 2020

The Product Owner must be present at Scrum events.