Scrum Master English Vocabulary: 60 Terms for Ceremonies and Coaching

Scrum Masters lead ceremonies, coach teams, and communicate with stakeholders — in English, across time zones. The Scrum vocabulary comes from the Scrum Guide, SAFe documentation, and Agile community practice. This guide covers the 60 terms every Scrum Master needs to facilitate, coach, and communicate confidently.

Scrum Framework

Scrum

Scrum is an Agile framework for delivering value in short, iterative cycles called sprints. It defines three roles (Product Owner, Scrum Master, Developers), five events, and three artefacts.

Sprint

A sprint is a fixed-length iteration (typically 2 weeks) during which the team delivers a potentially releasable product increment. Sprints have a consistent cadence — they don’t extend or shorten.

Sprint Goal

The Sprint Goal is a single, concise statement of what the team intends to achieve during the sprint. It gives the sprint focus and flexibility — the team may adjust the plan as long as the goal is achievable.

“This sprint’s goal: enable customers to export their data in CSV format.”

Product Backlog

The product backlog is the ordered list of all work needed for the product — user stories, features, bug fixes, technical work. Owned and prioritised by the Product Owner.

Sprint Backlog

The sprint backlog is the subset of product backlog items the team commits to completing in the current sprint, plus the plan for how to deliver them.

Increment

The increment is the sum of all product backlog items completed during a sprint and all previous sprints — the potentially releasable product at the end of each sprint.

Definition of Done (DoD)

The Definition of Done is a shared understanding of the criteria that every increment must meet before it can be considered complete. Includes code review, testing, documentation, and deployment to staging.

Scrum Roles

Scrum Master

The Scrum Master is a servant-leader who helps the team understand and enact Scrum, removes impediments, facilitates events, and coaches the organisation on Agile principles. Not a project manager.

Product Owner (PO)

The Product Owner is responsible for maximising product value — ordering the backlog, clarifying requirements, and accepting completed work.

Developers

In Scrum, Developers are all team members who work on the increment — engineers, testers, designers. Self-organising and cross-functional.

Sprint Ceremonies / Events

Sprint Planning

Sprint Planning is the ceremony that kicks off each sprint. The team collaborates to select backlog items, refine them, and create a sprint goal and plan. Timeboxed: 8 hours max for a 4-week sprint.

Daily Scrum (Daily Stand-up)

The Daily Scrum is a 15-minute daily meeting for Developers to synchronise and adapt the plan. The classic three questions: What did I do yesterday? What will I do today? Are there any impediments?

“The Daily Scrum is not a status report to the manager — it’s for the team to coordinate.”

Sprint Review

The Sprint Review is held at the end of the sprint: the team demonstrates completed work to stakeholders and collects feedback. The Product Owner updates the backlog based on feedback.

Sprint Retrospective

The Sprint Retrospective is a ceremony for the Scrum Team to reflect on the process and identify improvements. Format: What went well? What didn’t? What will we change?

Backlog refinement (also: backlog grooming) is an ongoing activity — the team reviews and clarifies upcoming backlog items, adds acceptance criteria, and estimates effort. Typically 1–2 hours per sprint.

Estimation

Story Points

Story points are a relative measure of effort, complexity, and uncertainty. Teams use the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) or T-shirt sizes (XS, S, M, L, XL).

Planning Poker

Planning poker is an estimation technique where team members simultaneously reveal their story point estimates, discuss differences, and converge on a shared estimate.

Velocity

Velocity is the average number of story points completed per sprint over the last 3–5 sprints. Used for sprint planning and release forecasting.

“Our velocity is 32 points per sprint. To deliver the feature with 96 points estimated, we plan for 3 sprints.”

Capacity

Capacity is the amount of work the team can take on in a sprint, accounting for planned leave, on-call duties, and other commitments. Different from velocity — velocity is historical; capacity is planned.

WIP (Work in Progress)

WIP is the number of items actively being worked on simultaneously. Limiting WIP improves flow and reduces context switching — a core Kanban and Lean principle.

Scrum Master Responsibilities

Impediment

An impediment is anything blocking the team’s progress. Removing impediments is the Scrum Master’s most visible responsibility.

“The impediment today: the test environment is down. I’m escalating to the infrastructure team to restore it by noon.”

Servant Leadership

Servant leadership means prioritising the needs of the team over personal authority. The Scrum Master serves the team, not the other way around.

Facilitation

Facilitation is guiding a group through a process to achieve a productive outcome — without imposing direction or judgement. Core Scrum Master skill: facilitating ceremonies, workshops, and conflict resolution.

Coaching

A Scrum Master coaches by asking questions that help the team find their own answers — rather than giving directives. Coaching builds team capability.

“Instead of telling the team what to do, I asked: ‘What do you think is causing the velocity drop?’”

Mentoring

Mentoring involves sharing experience and guidance from a more senior practitioner. A Scrum Master may mentor junior developers or teams new to Agile.

Shielding

Shielding (or “protecting the team”) means preventing unnecessary interruptions — requests that bypass the backlog, ad hoc tasks added mid-sprint, or pressure to commit to unrealistic deadlines.

Team Health & Culture

Psychological Safety

Psychological safety is the shared belief that the team is safe to take interpersonal risks — raising concerns, admitting mistakes, and challenging ideas without fear of punishment.

“Psychological safety is the foundation for effective retrospectives — without it, teams deflect instead of improving.”

Team Norms

Team norms (working agreements) are explicit agreements about how the team works together — communication channels, meeting etiquette, decision-making processes, and feedback norms.

Retrospective Techniques

Common retrospective formats:

Start / Stop / Continue — actions to start doing, stop doing, keep doing
4Ls — Liked, Learned, Lacked, Longed For
Sailboat — anchors (problems), winds (enablers), rocks (risks), sun (vision)
Mad / Sad / Glad — emotional check-in before identifying actions

Action Items

Action items from a retrospective are specific, assigned, and time-boxed improvements. A retrospective without action items is just a conversation.

Metrics & Reporting

Burndown Chart

A burndown chart shows remaining work (story points) vs. time within a sprint. Slopes downward as work is completed. A flat or rising line indicates blocked work.

Burnup Chart

A burnup chart shows completed work vs. total scope. More resilient to scope changes than a burndown — scope additions are visible rather than hidden.

Cycle Time

Cycle time is the time from when work starts on a backlog item to when it is done. A key flow metric. Shorter, more consistent cycle times improve predictability.

Lead Time

Lead time is the time from when a request enters the backlog to when it is delivered. Includes waiting time. Shorter lead time = faster customer value delivery.

Cumulative Flow Diagram (CFD)

A CFD shows the number of items in each state (To Do, In Progress, Done) over time. Widening bands indicate bottlenecks or WIP violations.

Scaling Agile

SAFe (Scaled Agile Framework)

SAFe organises multiple Agile teams into Agile Release Trains (ARTs) that deliver value on a Program Increment (PI) cadence (typically 10 weeks = 4 sprints + 1 Innovation & Planning sprint).

Key SAFe roles:

Release Train Engineer (RTE) — the Scrum Master for the ART
Product Manager — manages the Program Backlog
System Architect — guides technical direction across teams

Scrum of Scrums

Scrum of Scrums is a coordination mechanism for multiple Scrum teams — one representative per team meets to discuss cross-team dependencies, impediments, and integration.

PI Planning

PI Planning (Program Increment Planning) is a two-day, face-to-face event where all ART teams plan their work for the next Program Increment. Features team breakouts, dependency mapping, and risk identification.

Feature / Epic (SAFe)

In SAFe:

Epic — a large initiative spanning multiple ARTs or PIs
Feature — a service or capability that delivers value to the customer; fits within one PI
Story — a small piece of functionality that fits within one sprint

Useful Phrases

Opening a retrospective:

“Let’s start with a quick temperature check — rate the sprint from 1 to 5, one finger at a time.”
“This is a blameless space — we’re here to improve the process, not evaluate individuals.”

Removing impediments:

“The team is blocked on the API specification from the payments team. I’ll set up a meeting tomorrow to unblock this.”
“This is outside our control — I’m escalating to the management level to resolve it.”

In sprint planning:

“The sprint goal is clear — let’s make sure every item we pull in serves that goal.”
“Our capacity this sprint is 28 points — let’s not overcommit.”

Coaching conversations:

“What do you think is causing the issue? What have you already tried?”
“What would success look like for you at the end of this sprint?”

Practice

Test your Scrum vocabulary with the Scrum Master & Agile Coach exercise set — 5 exercises covering ceremonies, metrics, and coaching language.

Explore the Scrum Master learning path for facilitation scenarios, meeting language exercises, and writing practice.