Scrum
Scrum Definition
In a nutshell, Scrum requires a Scrum Master to foster an environment where:
1. A Product Owner orders the work for a complex problem into a Product Backlog.
2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
4. Repeat
Scrum Theory
Transparency
Inspection
Adaptation
Scrum Values
Commitment
Focus
Openness
Respect
Courage
Scrum Team
The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
Developers
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
The Scrum Master is accountable for the Scrum Team’s effectiveness.
Scrum Masters are true leaders who serve the Scrum Team and the larger organization.
Scrum Events
The Sprint
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
Scrum Artifacts
Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:
For the Product Backlog it is the Product Goal.
For the Sprint Backlog it is the Sprint Goal.
For the Increment it is the Definition of Done.
Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
It is the single source of work undertaken by the Scrum Team.
Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items.
Sprint Backlog
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.
The Sprint Backlog is a plan by and for the Developers.
If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.
Increment
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
The moment a Product Backlog item meets the Definition of Done, an Increment is born.