Learner Reference
Last updated on 2026-01-16 | Edit this page
Glossary
This glossary defines the key terms used throughout this course. These definitions come from primary sources including the Scrum Guide, Scrum@Scale Guide, associated essence cards, the Scrum Patterns Community, and Scrum Inc. thought leadership.
A
Adaptation
One of the three Scrum Pillars. If an inspector determines that one or more aspects of a product or process deviate outside acceptable limits and that the resulting product will be unacceptable, the process or the work being done must be adjusted.
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
B
Backlog
An ordered, prioritized list of work to be done by the Scrum Team. The Product Owner curates the Backlog.
C
Cross-Functional Team
A team with all the competencies needed to accomplish work they are given without outside help. Cross-functional teams are proven to be more flexible, creative, and productive than teams that specialize in only one of the competencies needed to get the work done.
D
Daily Scrum
One of the 5 Scrum Events, this meeting lasts no more than fifteen minutes and happens every workday at the same appointed time and place. Everyone on the team attends. At this meeting, the information needed to assess progress is presented, and any impediments are noted. This information may result in re-planning of the Sprint.
Dependency Board
A visualization of any dependencies, collaborations and events that will impact the teams during the Sprint (or Sprint of Sprints) especially those that go outside the control of the Scrum of Scrums. It provides a way to manage the flow of work within a Scrum of Scrums and should be reviewed and updated at least daily.
Definition of Done
The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Definition of Done (DoD) represents the organization’s formal definition of quality for all Product Backlog Items (PBIs). If an organization does not have one, the Scrum team should set its own. The Definition of Done is the commitment contained within the Increment artifact.
Definition of Ready
Information needed by the team in order to understand and complete a Product Backlog Item (PBI). Examples include the I.N.V.E.S.T. Criteria. There should be no further conversation or exploration of what is needed for the team to complete the PBI.
Development Team
Also known simply as the Team, it is comprised of people who work on Sprint Backlog Items. It acts as ‘one team’ and has all the skills needed to produce a working tested increment each Sprint. The development team is:
- Self-Organizing
- Cross-Functional
- Accountable
- Small with 3 - 9 team members
E
Empiricism
A foundation of Scrum. The belief that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Estimation
The act of predicting how much effort will be needed to complete work on a Product Backlog Item. Without it, Product Owners and Scrum Masters will struggle with securing a release date and showing velocity improvement. There are many methods. Most commonly occurs during Product Backlog Refinement.
F
I
Impediment
Anything that slows the Team down or prevents them from completing work. The key is to identify and remove impediments as quickly and systematically as possible. The Scrum Master helps the team remove impediments and is accountable for surfacing impediments the team can’t remove on their own.
Improvement Backlog Item
Individual backlog items of impediments that are hindering or blocking the work of a Scrum of Scrums and their associated Scrum Teams. These Backlog Items can also address opportunities and drive change.
Improvement Backlog Refinement
The ongoing process of adding detail, estimates, and order to the items in the Improvement Backlog, and transforming opportunities and impediments into actionable improvements. A Scrum of Scrums level activity led by the Scrum of Scrums Master.
Increment
An Increment (sometimes referred to as a ‘Potentially Shippable Product’) is the value delivered for the customer via the Product Backlog Items completed during a Sprint. Each Increment should interface seamlessly with all prior Increments and stand alone as a distinct addition of value to the Product.
Inspection
One of the three Scrum Pillars. Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Inspections are most beneficial when diligently performed at the point of work and at Scrum events.
K
Kanban Workflow
A visual process management system that emphasises continuous delivery and optimisation of services or products. It utilizes Kanban cards to represent work items and visualizes the flow of tasks on a board, allowing teams to manage their work, set policies, measure metrics, and deliver value more effectively than traditional methodologies like Waterfall.
M
MetaScrum
An event where the Chief Product Owner shares the Scaled Backlog with the business owners who control funding, personnel and customer commitments so they can express their preferences and, sometimes, urgent demands.
P
Pair Programming
An Agile software development technique where two programmers work together at a single workstation. This collaborative approach involves one person writing code (the driver) while the other reviews each line of code as it’s written (the navigator). The two programmers switch roles frequently throughout the session.
Parking Lot
An unofficial extension of a meeting that often follows The Daily Scrum where the members of the Scrum Team discuss in-depth issues, impediments, or topics that go beyond the scope of the Daily Scrum.
Product Backlog
A priority ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
Product Backlog Item (PBI)
A change to be made to the product in a future release (for example a feature, function, requirement, enhancement, or fix). Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones.
Product Backlog Refinement
A whole team activity led by the Product Owner. The on-going process of adding detail, estimates, and order to the items in the Product Backlog. Not an official Scrum Event, but a highly recommended practice. Usually consumes no more than 10% of the capacity of the Team.
R
Refinement
The act of adding detail, estimates, and order to items in a Backlog. The on-going process of adding detail, estimates, and order to the items in the Product Backlog. Not an official Scrum Event, but a highly recommended practice. Usually consumes no more than 10% of the capacity of the Team.
Release Planning
Collaboratively agree what is to be achieved by a Scrum of Scrums Team using a longer planning horizon than a single Sprint (usually 1-6 months). A Product Owner Team led event used to acquire funding, drive marketing, and align stakeholder/team expectations. A timeboxed event of no more than 4 hours for a one-month period.
S
Scaled Daily Scrum
Used in Scrum@Scale, an event used to plan and replan the work for the next 24 hours or so; to resolve emergent dependencies and issues, to optimize team collaboration, and to get things to Done. Normally held daily after the teams’ Daily Scrum, this is a 15-minute time-boxed scaled event.
Scaled Product Backlog Refinement
Used in Scrum@Scale, the ongoing process of adding detail, estimates, and order to the items in the Shared Product Backlog and decomposing complex items so they can be pulled by the individual teams. A Product Owner Team activity led by the Chief Product Owner and held at least once a Sprint.
Scaled Sprint Review
Used in Scrum@Scale, an informal meeting held at the end of the Common Sprint to inspect the Shared Increment and adapt the Shared Product Backlog. A timeboxed event of no more than 4 hours for a one-month Sprint (shorter for shorter Sprints), which can remove the need for individual team Sprint Reviews.
Scrum of Scrums Retrospective
Used in Scrum@Scale, an opportunity for the Scrum of Scrums to inspect itself and create a plan for Improvements to be enacted across the teams. A time-boxed event of no more than 3 hours for a one-month Sprint (shorter for shorter Sprints). It is not necessarily done every Sprint but must be done at least once every 3 months.
Scrum
Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
Scrum Artifacts
There are three artifacts in Scrum: Product Backlog, Sprint Backlog, and Increment. Each artifact contains a commitment to enhancing transparency, focus, and understanding how to measure progress. The commitments for each artifact are: Product Goal for the Product Backlog, Sprint Goal for the Sprint Backlog, and Definition of Done for the Increment.
Sprint Board
A tool that makes visible a Scrum Team’s Sprint Backlog and progress during a Sprint. Can take many forms ranging from a digital tool to a three-column board labeled ‘Do’, ‘Doing’, ‘Done’. The board is updated by the Team and shows all items that need to be completed, are in progress, or are finished in the Sprint.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. They are accountable for the Scrum Team’s effectiveness by enabling the Scrum Team to improve its practices within the Scrum framework. Scrum Masters are true leaders who serve the Scrum Team and the broader organization.
Scrum Pillars
Scrum is founded on empirical process control theory, or empiricism. Three pillars uphold every implementation of empirical process control:
- Transparency
- Inspection
- Adaptation
Scrum Team
The fundamental unit of Scrum is a small team of people, a Scrum Team. A Scrum Team consists of one Scrum Master, one Product Owner, and Developers (anyone working on the Sprint Increment). Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit focused on one objective at a time, the Product Goal.
Scrum Values
There are five Scrum Values: commitment, courage, focus, openness, and respect. When these values are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone.
Sprint
One of the five Scrum Events. It is a short, consistent cycle no longer than four weeks. The goal is to have an iteration short enough to keep the team focused but long enough to deliver a meaningful increment of work. All other Scrum Events take place during a Sprint. Once a Sprint is finished, the next begins.
Sprint Backlog
The set of Product Backlog Items selected for the Sprint, plus a plan for delivering the Increment and realizing the Sprint Goal. It includes at least one Improvement identified at the last Sprint Retrospective. It makes visible all of the work the Team identifies as necessary to meet the Sprint Goal.
Sprint Goal
The Sprint Goal is the singular objective for the Sprint. It is the COMMITMENT of everyone working on the Sprint Increment, providing clarity to understand what is needed, who needs it, why it is needed, and how it will provide value. It helps create focus and alignment, encouraging the Scrum Team to work together to produce value rather than individual efforts.
Sprint Planning
One of the five Scrum Events. Where the work to be performed in the Sprint is planned. This event is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose.
Sprint Retrospective
One of the five Scrum Events. An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This event occurs after the Sprint Review and prior to the next Sprint Planning. At most a three-hour meeting for one-month Sprints.
Sprint Review
One of the five Scrum Events. Held at the end of the Sprint to allow customers and stakeholders to inspect the Increment, give feedback, and for the Scrum Team to adapt the Product Backlog if needed. This is at most a four-hour meeting for one-month Sprints.