" When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame. Each Sprint may be considered a short project. "

- The Scrum Guide (TM) of 2020.

"Coach of the Developers in self-organization and cross-functionality" and "Remover of impediments to the Developers' progress" are parts of the Scrum Master's accountabilities.

Remember :

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 Scrum Team is self-managed and self-organized. They choose the PBI format they want. User stories are not mandatory.

The Product Owner is accountable for the Product Backlog. He/She is the one who can explain the Product Backlog Items.

"Sprint Retrospectives" is incorrect because during this event, the Scrum Team doesn't talk about the Product and the market.

"Daily Scrums" is incorrect because this event is for Developers only. The Product Owner can only attend the Daily Scrum but not participate in it.

The Four Values of The Agile Manifesto :

- Individuals and Interactions Over Processes and Tools.

- Working Software Over Comprehensive Documentation.

- Customer Collaboration Over Contract Negotiation.

- Responding to Change Over Following a Plan.

The Sprint Retrospective is the last event of a Sprint.

A new Sprint starts immediately after the conclusion of the previous Sprint.

As new work is required, the Developers adds it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Developers can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and it belongs solely to the Developers.

In Scrum, the project plan is essentially the Product Backlog. The Product Owner should continuously update the Product Backlog as new information, feedback, and insights become available. This allows for flexibility and adaptation throughout the project.

A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master.

The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plans to accomplish during the Sprint, and it belongs solely to the Developers.