PSM I Glossary

Key terms and acronyms for the PSM I exam, explained in plain language.

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

Acceptance criteria
Conditions a specific Product Backlog item must satisfy. Distinct from the Definition of Done, which is the quality standard for the Increment as a whole.
Accountability (Scrum)
One of the three defined responsibilities in a Scrum Team: Developers, Product Owner, Scrum Master. Accountability cannot be delegated away even when the work is delegated.
Adaptation
One of the three pillars of empiricism: adjusting a process or product as soon as possible when inspection finds deviation outside acceptable limits.
Artifact
One of the three formal objects in Scrum — Product Backlog, Sprint Backlog, Increment — each with a commitment that makes progress measurable.
Burn-down chart
A chart showing remaining work over time. A forecasting practice that has proven useful but does not replace empiricism.
Commitment (artifact)
The element that gives an artifact focus and measurability: Product Goal for the Product Backlog, Sprint Goal for the Sprint Backlog, Definition of Done for the Increment.
Cross-functional
A property of the Scrum Team: its members have all the skills necessary to create value each Sprint, without depending on people outside the team.
Daily Scrum
A 15-minute event for the Developers, held every working day of the Sprint at the same time and place, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
Definition of Done
A formal description of the state of the Increment when it meets the quality measures required for the product. The commitment for the Increment; work counts as part of an Increment only when it meets the Definition of Done.
Developers
The people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint. Includes testers, designers, and analysts — not only programmers.
Emergent
Evolving over time rather than fully defined upfront. The Product Backlog is emergent: it changes as the product, market, and understanding change.
Empiricism
The theory that knowledge comes from experience and decisions are based on what is observed. Scrum is founded on empiricism and lean thinking.
Forecasting
Predicting future progress from observed delivery, using practices such as burn-downs, burn-ups, or cumulative flows. Forecasts are empirical and change as the team learns.
Impediment
Anything blocking the Scrum Team's progress. The Scrum Master causes the removal of impediments.
Increment
A concrete stepping stone toward the Product Goal. Additive to all prior Increments, thoroughly verified, and usable. The sum of Increments is presented at the Sprint Review.
Inspection
One of the three pillars of empiricism: frequently and diligently examining artifacts and progress toward goals to detect unwanted variation. Pointless without adaptation.
Lean thinking
Reducing waste and focusing on the essentials. One of the two foundations of Scrum, alongside empiricism.
Product Backlog
An emergent, ordered list of what is needed to improve the product. The single source of work undertaken by the Scrum Team.
Product Backlog refinement
The ongoing activity of breaking Product Backlog items into smaller, more precise items, adding details such as description, order, and size.
Product Goal
A long-term objective describing a future state of the product. The commitment for the Product Backlog; one Product Goal per product at a time.
Product Owner
The accountability for maximizing the value of the product and for effective Product Backlog management. One person, not a committee.
Professional Scrum Competencies
Scrum.org's competency model defining the Focus Areas the PSM I exam draws from: the Scrum Framework, Developing People and Teams, and Managing Products with Agility.
PSM I
Professional Scrum Master I: Scrum.org's entry-level Scrum Master certification. 80 questions, 60 minutes, 85% to pass, $200 per attempt, lifetime validity.
PSM II / PSM III
Scrum.org's advanced and distinguished-level Scrum Master certifications, for practitioners with deeper experience than PSM I requires.
Refinement
See Product Backlog refinement: the ongoing activity of adding detail to Product Backlog items. Not a formal Scrum event.
Scrum
A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
Scrum Guide
The definitive description of Scrum, written by Ken Schwaber and Jeff Sutherland. The current version is the 2020 edition; it is the sole source for the PSM I exam.
Scrum Master
The accountability for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness. A true leader who serves, with no authority over team members.
Scrum Open
Scrum.org's free practice assessment for PSM I. Uses the same question style as the real exam and is the best calibration tool available before booking.
Scrum Team
The fundamental unit of Scrum: one Scrum Master, one Product Owner, and Developers. Cross-functional, self-managing, typically 10 or fewer people, with no sub-teams or hierarchies.
Scrum Values
Commitment, focus, openness, respect, and courage. The values give direction to the Scrum Team's work, actions, and behavior; when embodied, the empirical pillars come to life and build trust.
Self-managing
A property of the Scrum Team: it internally decides who does what, when, and how. No one outside the team assigns its work.
Servant leadership
Leading by serving rather than commanding. The Scrum Master is a true leader who serves the Scrum Team and the larger organization.
Sprint
A fixed-length event of one month or less in which ideas are turned into value. The container for all other Scrum events; a new Sprint starts immediately after the previous one.
Sprint Backlog
The Sprint Goal (why), the Product Backlog items selected for the Sprint (what), and the plan for delivering the Increment (how). A plan by and for the Developers.
Sprint Goal
The single objective for a Sprint, created during Sprint Planning. The commitment for the Sprint Backlog; it gives the Sprint coherence.
Sprint Planning
The event that initiates the Sprint by laying out the work to be performed. Timeboxed to a maximum of 8 hours for a one-month Sprint; addresses why, what, and how.
Sprint Retrospective
The event for planning ways to increase quality and effectiveness, by inspecting individuals, interactions, processes, tools, and the Definition of Done. Maximum 3 hours for a one-month Sprint.
Sprint Review
The event for inspecting the outcome of the Sprint and determining future adaptations, with key stakeholders. Maximum 4 hours for a one-month Sprint; a working session, not a presentation.
Stakeholder
A person or group with an interest in the product. Stakeholders collaborate with the Scrum Team, attend the Sprint Review, and influence the Product Backlog by convincing the Product Owner.
Timebox
A fixed maximum duration for an event. Scrum events are timeboxed: Sprint Planning 8 hours, Daily Scrum 15 minutes, Sprint Review 4 hours, Sprint Retrospective 3 hours (for a one-month Sprint).
Transparency
One of the three pillars of empiricism: the emerging process and work must be visible to those performing the work and those receiving it.
Velocity
A measure of how much work a team completes per Sprint, used for forecasting. Not defined in the Scrum Guide and not a measure of the team's value or productivity.
Advertisement