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.

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the Definition of Done, if appropriate and not in conflict with product or organizational standards.

" The Sprint Backlog is a plan by and for the Developers. "

- The Scrum Guide (TM) of 2020.

Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.

Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.

The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. They are structured and empowered by the organization to manage their own work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency.

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

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

The Developers may invite other people to attend the Sprint Planning in order to provide technical or domain advice.

The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting.

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.