Scrum Terminology 2026: The Complete Glossary for Practitioners

The Product Owner owns the Product Backlog and is accountable for maximising the value of the product. One person, not a committee. The Scrum Master is accountable for the team's Scrum practice and effectiveness, coaching the team, the Product Owner and the organisation. The Developers are the people who build the Increment each Sprint. Together these three form the Scrum Team, which the 2020 Scrum Guide capped at ten people total.

The Sprint is the container event, a fixed timebox of one month or less in which a usable Increment is created. Inside the Sprint sit four other events: Sprint Planning defines what and how; the Daily Scrum re-plans the next 24 hours; the Sprint Review inspects the Increment with stakeholders; the Sprint Retrospective inspects the team's process and decides on improvements.

The three artifacts are the Product Backlog (an ordered list of everything that might be needed in the product), the Sprint Backlog (the plan for the current Sprint) and the Increment (a concrete stepping stone toward the Product Goal). Each artifact carries a commitment: the Product Goal, the Sprint Goal and the Definition of Done respectively. Commitments were added in the 2020 Scrum Guide to make the artifacts empirical rather than decorative.

Beyond the Scrum Guide itself, teams use vocabulary borrowed from XP, Kanban and scaled frameworks. Story points, velocity, throughput, cycle time and lead time are measurement terms. Epic, feature, user story and task are backlog decomposition terms. SAFe adds Program Increment, ART (Agile Release Train), PI Planning and Solution Train. LeSS and Nexus add integration teams and cross-team refinement.

• Story points - relative sizing estimate
• Velocity - story points completed per Sprint
• Cycle time - start to done for one item
• Definition of Ready - entry criteria to a Sprint
• Refinement - ongoing backlog grooming
• Program Increment (SAFe) - 8 to 12 week planning cycle

Interview panels in 2026 typically probe six areas: the three commitments, the difference between a Product Owner and a project manager, how the Definition of Done governs quality, how Refinement differs from Sprint Planning, what velocity is (and is not) for forecasting, and how scaling frameworks coordinate multiple teams. Prepare a one-line answer for each and one 90-second story from your delivery experience that illustrates it. Candidates who can move fluently between the Scrum Guide vocabulary and lived examples consistently outperform those who can only recite definitions. The CSM and CSPO exams reward the same fluency, so the interview prep and the certification prep are the same effort. Keep the Scrum Guide bookmarked, it is 14 pages and reads in one sitting.