Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.

In Scrum, there are four events that occur within a Sprint:

1. Sprint Planning: A time-boxed meeting where the entire Scrum Team collaborates to determine what can be delivered in the upcoming Sprint, and how the work will be accomplished.
2. Daily Scrum: A daily, time-boxed event where the Developers inspect progress toward the Sprint Goal and plans for the next 24 hours.
3. Sprint Review: A time-boxed event where the Scrum Team and stakeholders inspect the Increment of work and adapt the Product Backlog if needed.
4. Sprint Retrospective: A time-boxed event where the Scrum Team inspects itself and creates a plan for improvements to be enacted during the next Sprint.

And the artifacts are: Product Backlog; Sprint Backlog; Increment.

The aim of the Scrum Team is to deliver a valuable and usable increment that meets the Definition of Done (and not just pieces of code). In agile, we are business / product / value oriented.

Only the Developers participate in the Daily Scrum. Not the entire Scrum Team.

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 Product Owner is responsible for maximizing the value of the product and the work of the Developers. The primary tool to do so is the Product Backlog.

The Product Owner manages Product Backlog against the assumption that value will be generated. This assumption remains invalidated when not checked against users and market.

Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.

The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal.

The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog.

In a first place, it will generate too much complexity for an empirical process to be efficient.

Ex : Each Scrum Team needs to mutually define their Definition of Done so their work will be potentially releasable. That involves some overhead work in syncing up, and hence the impact to productivity.

Coding best practices are not the interest of the Stakeholders.

What is a Sprint Review?

A Sprint Review is a Scrum Event that occurs at the end of each Sprint. The purpose of the Sprint Review is to inspect and demonstrate the work that was completed during the Sprint and to get feedback from stakeholders. The Scrum Team presents the work they have built during the Sprint to stakeholders. This event provides an opportunity for the stakeholders to see the progress being made, provide feedback, and help the Product Owner adjust the Product Backlog if necessary. The Sprint Review is a collaborative and transparent process that helps the Scrum Team to continually improve their work and deliver the best possible product.