Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.

Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.

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.

False. Scrum does not require having aligned Sprints for multiple teams. However, in a Nexus context all the Scrum Teams' Sprints must be aligned.

The Product Owner participates in the Sprint Retrospective as a Scrum Team member and should work closely with the team to determine next steps and actions to be taken to address identified areas for improvement.

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?

When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone.

The Scrum Team members learn and explore those values as they work with the Scrum roles, events, and artifacts.

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 increment must be in useable condition regardless of whether the Product Owner decides to release it.