Professional Scrum Master I key terms

The approach of basing decisions on what is observed, experienced, and measured rather than on theory or prediction. In Scrum, progress is assessed from actual evidence so that the team can adapt to reality.

The property of making the process, work, and outcomes visible to everyone doing or receiving the work. Without it, inspection produces misleading conclusions and adaptation leads the team in the wrong direction.

The regular, careful examination of Scrum artifacts and progress toward agreed goals. It is frequent enough to detect unwanted deviation early but not so frequent that it disrupts the work itself.

Adjusting process or work as soon as inspection reveals that one or more aspects are unacceptable or off course. The team changes what it does, not just what it says, to stay on target.

A mindset that focuses on reducing waste, limiting work in progress, and delivering value continuously. It underpins Scrum's emphasis on small batches, flow, and respecting people.

Commitment, Focus, Openness, Respect, and Courage. These five qualities guide how team members behave and make the empirical pillars of transparency, inspection, and adaptation possible in practice.

A small, self-managing group made up of one Scrum Master, one Product Owner, and Developers. The whole team is collectively accountable for delivering a valuable, useful Increment each Sprint.

The single person accountable for maximizing the value of the product resulting from the Scrum Team's work. This role owns the Product Goal, orders the Product Backlog, and decides what the team builds next.

The person accountable for establishing Scrum as described in the Scrum Guide and for the team's effectiveness. This role serves the team and organization by coaching, teaching, and removing impediments rather than directing work.

The team members who create any aspect of a usable Increment each Sprint. They self-manage their work, decide how to turn backlog items into value, and hold each other accountable as professionals.

The characteristic of a Scrum Team that chooses internally who does what, when, and how. The team is given a goal and the authority to decide how to reach it, without a manager assigning tasks.

A style of leading that puts the needs of the team and its customers first. The Scrum Master practices this by helping others grow, facilitating their success, and removing obstacles rather than commanding.

Helping individuals and teams improve through questioning, feedback, and guided reflection rather than by giving answers or instructions. It is a core way a Scrum Master develops the team's capability over time.

Designing and guiding group interactions so participants can reach their own decisions and outcomes. The Scrum Master uses it to keep events productive without imposing content or controlling the discussion.

Anything blocking or slowing the team's progress toward its goal. The Scrum Master helps the team identify and remove these obstacles, escalating beyond the team when the cause lies elsewhere.

The five formal ceremonies: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Each has a purpose and a timebox, and together they create regularity and minimize unplanned meetings.

A fixed-length period of one month or less in which the team turns backlog items into a usable Increment. It is the container event inside which all other Scrum events occur.

The event that opens a Sprint, where the team agrees on why the Sprint is valuable, what can be delivered, and how the work will be done. It produces the Sprint Goal and the Sprint Backlog.

A 15-minute event for the Developers, held each working day of the Sprint, to inspect progress toward the Sprint Goal and adapt the plan. It is for the Developers, not a status report to managers.

A working session near the end of the Sprint where the team and stakeholders inspect the Increment and adapt the Product Backlog. Its purpose is collaboration and feedback, not a formal sign-off presentation.

The closing event of a Sprint, where the team inspects how it worked and identifies improvements to apply immediately. It focuses on people, process, tools, and the Definition of Done.

A fixed maximum amount of time set for an event or activity. The event ends when the timebox expires, which keeps Scrum events focused and prevents one topic from consuming unlimited discussion.

One of the three things Scrum defines to represent work or value: the Product Backlog, the Sprint Backlog, and the Increment. Each carries a commitment that gives it focus and purpose.

An ordered, ever-evolving list of what is needed to improve the product. It is the single source of work for the team, and its ordering reflects value, risk, and priority as judged by the Product Owner.

The set of Product Backlog items selected for a Sprint, together with the plan for delivering them. It is a living picture of the work and is updated as more is learned during the Sprint.

The sum of completed, usable work produced during a Sprint. Each Increment adds to previous ones, must be in a usable condition, and is delivered as soon as it meets the Definition of Done.

A long-term target describing a future state of the product that the team works toward. It gives direction to the Product Backlog and is the commitment associated with that artifact.

A single objective for the Sprint that explains why the Sprint is valuable. It gives the team focus and flexibility, and it is the commitment associated with the Sprint Backlog.

An agreed, shared description of the quality state an Increment must reach to be considered complete. It makes transparency real and is the commitment associated with the Increment.

The ongoing activity of breaking down and clarifying Product Backlog items so they are ready for future Sprints. It is not a formal Scrum event, and the team decides how much time to spend on it.

A single entry in the Product Backlog describing something of value to build, such as a feature, fix, or improvement. Items are ordered and refined until they are small enough to be done within a Sprint.

A person or group with an interest in the product, such as customers, users, or business sponsors. Stakeholders give feedback in the Sprint Review and influence the ordering of the Product Backlog.

A measure of how much work a team completes per Sprint, often expressed in story points. It is a planning aid the team derives for itself, not a performance target imposed by others.

A relative unit teams use to size backlog items by effort, complexity, and uncertainty rather than by clock time. Points support forecasting and conversation; they are not a measure of individual productivity.

A visual showing work remaining over time within a Sprint or release. It helps the team inspect progress empirically and adapt its plan, but it is a tool, not a required Scrum artifact.

A physical or digital display of the Sprint Backlog, often organized into workflow columns. It makes work visible for inspection at the Daily Scrum, supporting transparency and self-management.

The practice of Scrum with genuine mastery of the framework and its values, rather than mechanical ceremony-following. It emphasizes craftsmanship, continuous improvement, and honest empiricism over rigid process compliance.