Is founded on empiricism and lean thinking

delivering superior customer value by eliminating waste - continuous improvement.

Adaptive Products of highest value to solve complex problems in volatile environment. It's the opposite of the waterfall process.

Test and feedback oriented

Knowledge comes from experience.

It helps to generate value through adapative solutions for complex problems

Do it right. Courage facilitates empiricism and collaborative teamwork.

Focus on the overall outcome.

Scrum Team commits to goals. "It will be done no matter what"

Respect people, accountabilities, dedication, accomplishments.

Facilitates teamwork and collaboration

Scrum Master

Product Owner

Developers

The Product Goal

Multiple Scrum Teams working on the same product must deliver at least one integrated increment at the end of the Sprint.

Typically 10 or fewer

1 per Product. Can also work as a Dev

Typically 10 or fewer

1 per Scrum Team. Can also work as a Dev

Scrum Teams (ST)

Product Owner (PO)

Scrum Master (SM)

Developers (Devs)

Commitment

Composed of a Product Owner, a Scrum Master and Developers.

No hierarchies

No dependencies

Self-managing and cross-functional

The Scrum Team delivers valuable and usable increment every sprint

All product-related activities. Creating a valuable, useful Increment every Sprint

Improves every Sprint (via the Sprint Retrospective)

Optimizes flexibility, creativity, and velocity

Receive feedback from users and stakeholders

Commitment

1 person, not a committee

Stakeholders and users representative

Visionary

Maximizes the Value of the Product built by the Developers

Commitment

Cross-functional, no titles

Multi-skilled

Build the usable increment that meets the Definition of Done

Create the Sprint Backlog

Ensure the increment meets the DoD

Product Backlog Items estimation

Monitor the progress of the Sprint (Daily Scrum)

A true leader, facilitator and a coach

Supports the Scrum Team.

Promotes Scrum as it is described in the Scrum Guide ™within the organization

Accountable for Scrum Team’s effectiveness

Facilitates Scrum Events and ensures to keep them within time-boxes

The result of prioritizing speedy delivery (quick and dirty) over perfect code (long term stability). Maintenance and fixing will be required.

When a change of people occurs within the Scrum Team, coordination and training will be required in a first place which will lower the short-term velocity. The same principle apply to adding a new Scrum Team on a product (for Nexus / Scaled Scrum)

All the Sprints must deliver an increment ready to be released in production whenever needed.

No hardening sprint or Sprint 0.

The Scrum Team is responsible for executing the tasks and monitoring and managing process and progress.

Multiple Scrum Teams working on the same product must deliver at least one integrated increment at the end of the Sprint.

Multiple Scrum Teams working on the same product may have different Sprint length and start/end dates (not recommended though). Nevertheless, they must integrate the increment by the Sprint Review.

Scrum requires a Scrum Team and a Product Backlog with enough items for a first Sprint.

Scrum Team defines DoD. The Devs apply it.

DoD must follow organizational standards as minimum

Multiple Scrum Teams have one DoD

Includes testing

Time-box

Purpose (outcome)

Participants

Time-box

Purpose (outcome)

Participants

Time-box

Purpose (outcome)

Participants

Time-box

Purpose (outcome)

Participants

Time-box

Purpose (outcome)

Participants

Description

Commitment

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.

Description

Commitment

Description

Commitment