The Daily Scrum is a 15-minute time-boxed event for the Developers of Scrum Teams of any size.

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.

Note: The Daily Scrum is an internal meeting to the Developers. Therefore, the Product Owner and the Scrum Master may ATTEND the Daily Scrum as silent observers but they cannot actively PARTICIPATE in the Daily Scrum.

Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.

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.

Note: The Daily Scrum is an internal meeting to the Developers. Therefore, the Product Owner and the Scrum Master may ATTEND the Daily Scrum as silent observers but they cannot actively PARTICIPATE in the Daily Scrum.

The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.

During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.

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 purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness.

The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.

The Scrum Master serves the organization in several ways, including:

● Leading, training, and coaching the organization in its Scrum adoption;

● Planning and advising Scrum implementations within the organization;

● Helping employees and stakeholders understand and enact an empirical approach for complex work; and,

● Removing barriers between stakeholders and Scrum Teams.

If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

The Scrum Master can work with stakeholders to make them understand Scrum and the entire team collaborates with them during Sprint Reviews.

The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering and is the sole person responsible for managing the Product Backlog. For the Product Owner to succeed, the entire organization must respect his or her decisions.

The Product Owner clearly expresses Product Backlog items, ensuring the Developers understand items in the Product Backlog to the level needed for developing them and creating the value the Product Owner envisions. Scope may be re-negotiated if the effort grows much higher than anticipated.

Scrum Masters are true leaders who serve the Scrum Team and the larger organization.

A Scrum Master is also a facilitator who coaches those inside and outside the team on the values of Scrum and incremental delivery.