Scrum Guide for Spectators

Below is the shortest version of the official Scrum Guide, which I created for those who "have no time".

Scrum is founded on empiricism and lean thinking.

Scrum Team

The fundamental unit of Scrum is a small team of people (typically 10 or fewer) – a Scrum Team.

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.

• Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.?
• The Scrum Master is accountable for the Scrum Team’s effectiveness.

Scrum Events

The Sprint – all the work necessary to achieve the Product Goal within Sprints.

Each Sprint has its goal – the Sprint Goal, the single objective for the Sprint, and may be considered a short project.

The Sprint Planning – meeting for the Scrum Team and advisors – addresses the following topics:

1. Why is this Sprint valuable?
2. What can be Done this Sprint?
3. How will the chosen work get done?

The Scrum Team may also invite other people to attend Sprint Planning to provide advice.

The purpose of the Daily Scrum – meeting for the Developers only – is to inspect progress toward the Sprint Goal.

The purpose of the Sprint Review – meeting for the Business and the Scrum team – 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. 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 should never be considered a gate to releasing value.

The purpose of the Sprint Retrospective – meeting for the Scrum Team only – ?is to plan ways to increase quality and effectiveness. It's a Kaizen tool.

?

Scrum Artifacts

The Product Backlog is a prioritized list of functionality which a product should contain — the single source of work undertaken by the Scrum Team.

Sprint Backlog is a list of items that can be Done within one Sprint — a plan by and for the Developers.

Increment is the latest stable and usable version of a product, because each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. It is a concrete stepping stone toward the Product Goal. The moment a Product Backlog item meets the Definition of Done, an Increment is born.?

If the Definition of Done 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.

To learn more:

Official Scrum Guide?