Test Your Scrum Knowledge

Summary of the 2020 Scrum Guide

The Scrum Guide defines Scrum, a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
Scrum is founded on empiricism and lean thinking, which emphasizes knowledge coming from experience and making decisions based on what is observed, and reducing waste and focusing on the essentials.
Scrum employs an iterative, incremental approach to optimize predictability and to control risk, and engages groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.
Transparency, inspection, and adaptation are the empirical pillars of Scrum, and the framework includes four formal events for inspection and adaptation within a containing event, the Sprint.
The Scrum Team is the fundamental unit of Scrum, consisting of one Scrum Master, one Product Owner, and Developers, and is responsible for all product-related activities.
The Scrum Team is cross-functional, meaning the members have all the skills necessary to create value each Sprint, and is self-managing, meaning they internally decide who does what, when, and how.
Successful use of Scrum depends on people becoming more proficient in living five values: commitment, focus, openness, respect, and courage.
The Sprint is a container for all other events, and Sprints are fixed length events of one month or less to create consistency.
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint, and the Daily Scrum inspects progress toward the Sprint Goal and adapts the Sprint Backlog as necessary.
The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed, and the Sprint Retrospective is held after the Sprint Review to inspect the Scrum Team’s processes and relationships and to plan improvements for the next Sprint.
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, enabling the Scrum Team to improve its practices, and serving the Product Owner and the organization.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, effective Product Backlog management, and making decisions visible in the content and ordering of the Product Backlog and through the inspectable Increment at the Sprint Review.
Developers are accountable for creating any aspect of a usable Increment each Sprint, and the specific skills needed by the Developers are often broad and will vary with the domain of work.Scrum Guide Summary
Sprint Review is held to inspect the outcome of the Sprint and determine future adaptations, where the Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
Sprint Review is a working session and is timeboxed to a maximum of four hours for a one-month Sprint.
Sprint Retrospective is held to plan ways to increase quality and effectiveness, where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint.
Scrum Artifacts represent work or value and contain a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured.
Product Backlog is an emergent, ordered list of what is needed to improve the product and is the single source of work undertaken by the Scrum Team.
Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against and is in the Product Backlog.
Sprint Backlog is composed of the Sprint Goal, the set of Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment.
Sprint Goal is the single objective for the Sprint, provides flexibility in terms of the exact work needed to achieve it, and is created during the Sprint Planning event and then added to the Sprint Backlog.
Increment is a concrete stepping stone toward the Product Goal, each Increment is additive to all prior Increments and thoroughly verified, and the Sprint Review should never be considered a gate to releasing value.
Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.