During Sprint Planning, the first topic the Scrum Team discusses is "What can be done this Sprint." The items under discussion comes from the Product Backlog. The Product Backlog is the single source of truth that lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. This list would be considered the work. However, how the work is delivered can change during the implementation.

The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

(Be careful, "participate" is different from "attend").

What is a Daily Scrum?

Daily Scrum is a daily 15-minute time-boxed meeting in the Scrum framework where Developers briefly share their progress and plans for the day. The goal of Daily Scrum is to ensure that everyone is aligned on the goals of the Sprint, identify and address any obstacles, and improve communication and collaboration among the Developers.

When forming an Agile team, there are several key competencies that are important to consider in order to create a high-performing team that can add business value to the project. These competencies include a blend of interpersonal and technical skills, and include:

1. Collaboration and teamwork: Agile teams work collaboratively, and team members need to be able to work effectively with each other, share information, and work towards common goals. Look for team members who are good listeners, communicators, and collaborators, and who are willing to contribute to the team's success.
2. Adaptability and flexibility: Agile teams need to be adaptable and able to respond to changing requirements and priorities. Look for team members who are comfortable with change, able to pivot quickly, and able to work in a dynamic and fast-paced environment.
3. Technical expertise: Agile teams need to have a strong technical skillset, as they will be responsible for delivering high-quality software or products. Look for team members who have a strong technical background and experience with the tools and technologies that will be used in the project.
4. Problem-solving and critical thinking: Agile teams need to be able to solve problems quickly and efficiently. Look for team members who have strong problem-solving and critical thinking skills, and who are able to think creatively and innovatively to come up with solutions.
5. Customer focus: Agile teams are focused on delivering value to the customer, and team members need to be able to understand the customer's needs and requirements. Look for team members who are customer-focused, empathetic, and able to put themselves in the customer's shoes.

Overall, when forming an Agile team, it's important to look for a blend of interpersonal and technical skills that can help the team work collaboratively, adapt to changing requirements, and deliver high-quality products that add value to the business.

The Product Owner can delegate his/her responsibilities to the Developers but he/she stays accountable.

" 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. "

" The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one- month Sprint. For shorter Sprints, the event is usually shorter. "

- The Scrum Guide (TM) of 2020.

Unlike methodologies, the Scrum "framework" is not tailored because it's already limited to the essentials. Even the terms should not change let along adding or removing elements such as roles and events. However, you may need to add some practices and techniques to the framework.

Indications of value on Product Backlog are useful but are only a prediction until validated against users and market.

The Product Backlog is a living artifact which is continually kept up to date with the most recent insights.

All work to be done by the Developers must ultimately come from the Product Backlog as it is the single source of truth for any changes to be made to the product. How the work is done can change, evolve, and emerge as the work is being done.

The Product Owner is responsible for maximizing the value of the product. How this is done will vary widely.

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.