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

The Product Owner is accountable for effective Product Backlog management, which includes:

● Developing and explicitly communicating the Product Goal;

● Creating and clearly communicating Product Backlog items;

● Ordering Product Backlog items; and,

● Ensuring that the Product Backlog is transparent, visible and understood.

Sprint Planning addresses the following topics:

Topic One: Why is this Sprint valuable?

Topic Two: What can be Done this Sprint?

Topic Three: How will the chosen work get done?

" The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. "

- The Scrum Guide (TM) of 2020

It is not normal. Developers deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only “Done” functionality that could be released immediately.

The Product Owner is also known as the value maximizer. He is responsible for maximizing the value of the work that the Developers do. This is done through the ordering of the Product Backlog.

False. Scrum does not require having aligned Sprints for multiple teams.

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.

What is a Sprint Review?

A Sprint Review is a Scrum Event that occurs at the end of each Sprint. The purpose of the Sprint Review is to inspect and demonstrate the work that was completed during the Sprint and to get feedback from stakeholders. The Scrum Team presents the work they have built during the Sprint to stakeholders. This event provides an opportunity for the stakeholders to see the progress being made, provide feedback, and help the Product Owner adjust the Product Backlog if necessary. The Sprint Review is a collaborative and transparent process that helps the Scrum Team to continually improve their work and deliver the best possible product.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.

The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.