SAFe SSM key terms

A small, cross-functional group of typically five to eleven people who define, build, test, and deliver value in short iterations; in SAFe, the team is the basic building block of an Agile Release Train.

A long-lived team of Agile teams, usually 50 to 125 people, that plans, commits, and delivers together on a shared cadence to produce integrated value for a value stream.

A fixed timebox, usually eight to twelve weeks, during which an Agile Release Train delivers a set of planned features and enablers; it contains several iterations plus an Innovation and Planning iteration.

A short, fixed timebox, typically two weeks, in which an Agile team plans, builds, tests, and demonstrates a small increment of value, ending with a review and a retrospective.

Cadence gives teams a regular rhythm of events and deliverables; synchronization makes multiple teams in an ART plan, integrate, and demonstrate on the same schedule so dependencies surface early.

The practice of building quality into every step rather than inspecting it in at the end, using standards, test automation, and technical practices that keep the solution releasable at all times.

The ten SAFe principles, such as taking an economic view, applying systems thinking, assuming variability, and decentralizing decision-making, that guide behaviors and choices across the organization.

Transparency, inspection, and adaptation: the Scrum foundation holding that work must be visible, regularly examined, and adjusted when it drifts, so decisions rest on observed reality.

The team's list of work to do, including stories, enablers, and other items derived from the ART's features and refined by the team into small, estimable pieces.

The SAFe team role accountable for the team's effectiveness: facilitating events, coaching the team and the Product Owner, removing impediments, and fostering a culture of continuous improvement.

A leadership stance in which the Scrum Master puts the team's needs first, listening, supporting growth, and removing obstacles, rather than directing or controlling the work itself.

Anything blocking the team's progress or reducing its effectiveness, such as a missing skill, a broken environment, or an unresolved dependency, which the Scrum Master helps surface, track, and remove.

The servant leader and chief Scrum Master for the Agile Release Train, facilitating ART events such as PI Planning and Inspect and Adapt and helping teams manage cross-team dependencies.

The team member accountable for defining and prioritizing the Team Backlog, clarifying stories, and ensuring the team builds what delivers the most value.

A team that owns how it does its work, including planning, estimating, assigning tasks, and improving its process, while leaders set direction and guardrails instead of giving instructions.

A regular, usually two-day, in-person or virtual event where all ART teams align on a shared mission, agree on dependencies, and produce team PI Objectives and a draft plan.

A summary of the business and technical outcomes a team intends to achieve in the coming PI, stated in plain language and scored for business value to guide decisions.

A visual planning aid used during PI Planning that shows features by team and iteration along with the dependencies and milestones that must be managed across the ART.

The preliminary set of team objectives, features, and dependencies captured during PI Planning and refined in breakout sessions before the final plan review.

A quick, typically fist-of-five poll taken at the end of PI Planning to show how confident each team is in delivering its plan, prompting discussion when confidence is low.

A session during PI Planning where management and stakeholders review the draft plans, resolve cross-team issues and resource constraints, and adjust scope so the ART can commit.

A service or capability that delivers value to the customer, sized to be completed by one team within a PI and broken down into stories for the team's backlog.

A team event at the start of an iteration where the team selects backlog items, agrees on iteration goals, and defines the work needed to deliver them.

A short set of outcomes the team commits to for the current iteration, summarizing the value of the selected backlog items and helping the team keep focus and alignment.

A brief daily team event to inspect progress toward the iteration goals, re-plan the day's work, and surface impediments and dependencies.

An end-of-iteration event where the team demonstrates the working increment to stakeholders, inspects results against the iteration goals, and adapts the backlog.

A team event at the end of each iteration to reflect on how the team worked, identify improvement actions, and track progress on actions from earlier retrospectives.

A regularly scheduled demonstration of the integrated work of all teams in the ART, giving stakeholders a view of the whole solution as it evolves across the PI.

The ongoing practice of reviewing, splitting, and clarifying backlog items so they are small, understood, and ready to be pulled into an upcoming iteration.

A team's shared checklist of criteria an item must meet to be considered complete, supporting built-in quality and consistent, transparent increments.

An ART-level event at the end of each PI where teams demonstrate the solution, review metrics, and run a structured problem-solving workshop to improve the system.

A structured I&A activity in which ART members analyze a significant problem using root cause analysis, agree on actions, and assign owners for the next PI.

A special iteration at the end of each PI that provides time for innovation, hackathons, PI Planning preparation, and learning, while the ART also delivers planned work.

The practice of using data, such as predictability measures, flow metrics, and team self-assessments, during Inspect and Adapt so improvement decisions rest on facts rather than opinions.

AI systems that produce text, images, or code from prompts, useful to Scrum Masters for drafting, summarizing, and brainstorming, always with human review of the output.

The skill of writing clear, contextual instructions, including role, context, constraints, and desired format, so an AI tool produces useful and accurate responses.

The practice of using AI transparently, fairly, and securely, protecting sensitive data, checking for bias and errors, and keeping humans accountable for decisions.

Using AI tools to support Scrum Master duties such as summarizing meetings, analyzing retrospective themes, drafting communications, and surfacing trends, while the Scrum Master retains judgment.