" 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 Scrum Guide (TM) of 2020

" Scrum’s artifacts represent work or value. They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation. "

- The Scrum Guide (TM) of 2020.

The input to the Sprint Planning is the Product Backlog, the latest product Increment, projected capacity of the Developers during the Sprint, and past performance of the Developers.

Note: There is no such thing as "Sprint Plan" in the Scrum framework.

For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one can force the Developers to work from a different set of requirements.

It's a good idea to use user stories for describing the Product Backlog items but it's not required.

During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.

In Scrum, the length of a Sprint is decided by the Scrum Team, which includes the Developers, the Product Owner, and the Scrum Master. The team collectively decides on the length of the Sprint during the Sprint Planning meeting. The recommended length of a Sprint is typically between 1-4 weeks, with 2 weeks being the most commonly used duration. However, the Scrum Team may decide on a different duration that best suits their context, such as the nature of the product, the team's velocity, and the stakeholders' needs.

The Scrum Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. A “Done” increment is required at the Sprint Review.