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.

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.

Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.

When a product grows, it is quite possible that the PO will get help from other Product Managers and others in the organization who interact regarding the customer facing activities and knowledge of the product marketplace. While it is fine for the PO to be aided by the aforementioned people, it is NOT acceptable for the PO to attempt to proxy or outsource their PO Scrum Team duties, especially the Scrum Team facing duties.

But only the Developers may PARTICIPATE in the Daily Scrum.

"Attend" the Daily Scrum means you are present at the event as a silent observer when participation means you step in and talk.

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.

The Cone of Uncertainty is a concept that describes the level of uncertainty and risk associated with a project at different stages of the development process. The Cone of Uncertainty suggests that as a project progresses, the level of uncertainty and risk decreases.

At the beginning of a project, there is a high degree of uncertainty and risk, and the project team has limited information about the project's scope, requirements, and timelines. As the project progresses, more information becomes available, and the level of uncertainty and risk decreases.

The Cone of Uncertainty provides a visual representation of this concept, with the cone widening at the beginning of the project to represent the high level of uncertainty and risk, and narrowing as the project progresses to represent the decreasing level of uncertainty and risk.

" Topic Two: What can be Done this Sprint?

Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.

Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts. "

- The Scrum Guide (TM) of 2020.

For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one can force the Developers to work from a different set of requirements.

The Scrum Master ensures that the meeting is positive and productive. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

What is a Sprint Retrospective?

A Sprint Retrospective is a Scrum Event that occurs at the end of each Sprint. The purpose of the Sprint Retrospective is to reflect on the passed Sprint and identify areas for improvement in the next Sprint. The Developers, along with the Scrum Master and Product Owner, review their processes and identify ways to work more effectively together. This event provides an opportunity for the Scrum Team to continuously improve and evolve their way of working. The outcome of the Sprint Retrospective is a plan for the next Sprint that includes actions to address the identified improvements.

The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute time-box.

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.

The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and the Developers.