https://www.scrumguides.org/scrum-guide.html

Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum is: Lightweight, Simple to understand , Difficult to master

Scrum is not a process, technique, or definitive method. The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.

• Development of software and hardware
• Development and sustaining of Cloud and other operational environments
• Managing the operation of an organization
• Unordered List ItemResearch and identifying of viable markets, technologies, and product capabilities
• Development of products and enhancements
• Development of almost everything we use in our daily lives as individuals and societies

The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive.

Scrum is based on empirism that asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach

• Transparency

must be visible to those responsible for the outcome. Nothing is hiddent. Observers share a common understanding of what is beeing see. Those performing the work and those inspecting the result must share a common definition of done.

• Inspection

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances

• L'adaptation

Events of scrum are occasion for inspection and adaptation.

• Commitment

.People personally commit to achieving the goals of the Scrum Team

• courage

Scrum Team members have courage to do the right thing and work on tough problems.

• focus

Everyone focuses on the work of the Sprint and the goals of the Scrum Team.

• Openness

The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.

• respect

Scrum Team members respect each other to be capable, independent people.

These value build trust for everyone

The Scrum Team is the Product Owner, the Development Team and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team

The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. The Product Owner is one person, not a committee He

• Clearly expressing Product Backlog items
• Ordering the items in the Product Backlog to best achieve goals and missions
• Optimizing the value of the work the Development Team performs
• Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
• Ensuring the Development Team understands items in the Product Backlog to the level needed.

The Development Team do the work of delivering a potentialy releasable increment of Done product at the end of each Sprint. The team organize and manage their own work.

The size of the Development Team is from 3 to 9.

Monitoring Sprint Progress : It is responsible for tracking the total work remaining at least for every daily scrum to project the likelihood of achieving the sprint goal. It manage its progress

Scrum Master Serves to the Product Owner He ensure that goals, scope and product domain are understood by everyone. He helps him in finding techniques for effective Product Backlog management. Ensure that he knows how to arrange the Product Backlog to maximize value. And he facilitate scrum events.

Scrum Master Serves to the Development Team He coach the Team, help in to create high value product, remove impediment and facilitate Scrum events.

Scrum Master serves the Organization

• Leading and coaching the organisation
• Planning Scrum implementations within the organization;
• Helping employees and stakeholders understand and enact Scrum and empirical product development;
• Causing change that increases the productivity of the Scrum Team
• Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization

Scrum organise event in order to minimize the need for other meetings. All events are time boxed with a maximum time of duration

The Sprint is the heart of Scrum. Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.

During the Sprint: No changes are made that would endanger the Sprint Goal, Quality goals do not decrease and Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

A Scrum Master should reinforce the purpose of Sprint Planning.

The Sprint Backlog consists of the selected Product Backlog Items and a plan to deliver them.

The Scrum Master is coping with incomplete transparency, in helping everyone to apply the most appropriate practices in the absence of complete transparency.

If the definition of done exists it should be clear for every one. If not the development team has to define one. Everyone must understand the same definition of done. This guides the development team to know how many product backlog item can be selected for the sprint planning. Each item of the increment must adhere the Dod.