click to reveal definition
click to flip back
You know 0 of 37 cards in current set.
Ready to get certified?
Get CertifiedNeed this expertise applied inside your organization?
Explore Our ServicesFull Glossary
Scrum in SAFe
- SAFe Scrum Master (SSM)
- A servant leader and coach for an Agile team in a SAFe enterprise. Unlike traditional Scrum Master training, the SSM role is understood in the context of the entire enterprise and the Agile Release Train, not just a single team.
- Scrum in a SAFe Enterprise
- SAFe applies Scrum at the team level while integrating teams into an Agile Release Train. The Scrum Master helps the team deliver value each iteration and contribute to the ART's shared PI objectives.
- SAFe Scrum
- SAFe's blend of Scrum and Kanban that teams use to plan and execute iterations, build quality in, and deliver value on the ART's cadence, guided by Lean-Agile principles.
- Agile Team
- A cross-functional group of 5–11 people who can define, build, test, and deliver an increment of value in an iteration. The Scrum Master supports the team's effectiveness and self-organization.
- Agile Release Train (ART)
- A long-lived team of Agile teams (50–125 people) that develops and delivers value on a Program Increment cadence. The Scrum Master helps their team align to and execute within the ART.
Scrum Master Role
- Servant Leadership
- The core stance of the Scrum Master: serving the team by removing impediments, facilitating events, coaching toward self-organization, and fostering an environment of trust rather than directing work.
- Scrum Master as Coach
- The Scrum Master coaches the team on Agile values, SAFe practices, and continuous improvement, helping the team grow its capability and deliver maximum business results.
- Facilitator
- The Scrum Master facilitates Scrum events and team discussions so they are effective, timeboxed, inclusive, and outcome-focused, while staying neutral on content.
- Impediment Removal
- Identifying and resolving obstacles that slow the team, escalating those beyond the team's control (often to the RTE) so flow of value is protected.
- Scrum Master vs. Project Manager
- The Scrum Master is not a project manager assigning work; they coach a self-organizing team, facilitate events, and foster flow, rather than command-and-control task management.
Scrum Events
- Iteration Planning
- The event where the team commits to iteration goals and selects stories from the team backlog, breaking them into tasks. The Scrum Master facilitates and ensures shared understanding.
- Daily Stand-up (DSU)
- A short (≤15 min) daily synchronization where the team coordinates work toward the iteration goals and surfaces impediments. It is for the team, facilitated lightly by the Scrum Master.
- Iteration Review
- An event at the end of the iteration where the team demonstrates working, integrated increments and gathers feedback to measure progress against iteration goals.
- Iteration Retrospective
- A team reflection at the end of each iteration on what went well and what to improve, producing concrete improvement actions — central to relentless improvement.
- Backlog Refinement
- Ongoing work to detail, estimate, and order team backlog items so upcoming stories are ready for iteration planning, reducing uncertainty and improving flow.
Iteration Execution
- Iteration (Sprint)
- A fixed timebox (typically two weeks) in which the team plans, builds, tests, and reviews a working increment aligned to the Program Increment.
- Iteration Goals
- A concise set of objectives for the iteration that provide focus and alignment and connect the team's work to the PI objectives.
- Team Kanban & Flow
- Visualizing work and limiting work in process to expose bottlenecks and improve the flow of value through the team's process during iteration execution.
- Built-In Quality
- Practices that ensure each increment meets quality standards throughout development (e.g., definition of done, test-first, continuous integration) rather than inspecting quality in at the end.
- Definition of Done (DoD)
- A shared checklist of criteria that work must satisfy to be considered complete, ensuring consistent quality across stories, iterations, and the PI.
PI Execution
- Program Increment (PI)
- A timebox (typically 8–12 weeks) during which the ART delivers value. The PI is the primary enabler of alignment across all levels of a SAFe organization.
- PI Planning
- The cadence-based event where all ART teams plan the upcoming PI together. The Scrum Master helps their team prepare, plan, identify dependencies, and commit to PI objectives.
- PI Objectives
- Business and technical goals a team commits to for the PI, assigned business value by Business Owners, giving focus and a basis for measuring success.
- Program Board & Dependencies
- A visualization of features, milestones, and cross-team dependencies created in PI Planning. The Scrum Master helps manage their team's dependencies through the PI.
- ART Sync / Scrum of Scrums
- Cross-team coordination events where Scrum Masters and representatives align on progress toward PI objectives, dependencies, and impediments across the train.
- System Demo
- An integrated demonstration of new features from all teams on the ART, providing an objective measure of PI progress.
- Inspect & Adapt (I&A)
- The end-of-PI event combining a solution demo, measurement, and a structured problem-solving workshop that produces improvement items for the next PI.
Coaching the Team
- Building High-Performing Teams
- Helping teams progress through formation and growth toward stable, self-organizing, high-performing units that reliably deliver value together.
- Coaching for Business Results
- Focusing the team's improvement on outcomes and value delivery, not just process compliance, so coaching translates into measurable business results.
- Powerful Questions & Active Listening
- Core coaching skills the Scrum Master uses to help the team surface issues, generate their own solutions, and take ownership of improvements.
- Addressing Anti-Patterns
- Recognizing and helping resolve common team dysfunctions — such as skipped ceremonies, poor collaboration, or lack of focus — that undermine flow and quality.
Supporting DevOps
- DevOps and CALMR
- SAFe's DevOps approach — Culture, Automation, Lean flow, Measurement, Recovery — that the Scrum Master supports to help the team improve its flow through the delivery pipeline.
- Continuous Delivery Pipeline
- The flow of Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand that the team contributes to in delivering value frequently.
AI-Empowered SSM
- AI for Routine Tasks
- Using Large Language Models to speed up routine work such as drafting retrospective agendas, summarizing notes, and preparing facilitation materials — freeing the Scrum Master to focus on people and flow.
- AI-Assisted Facilitation
- Leveraging AI to generate event agendas, discussion prompts, and improvement ideas, helping the Scrum Master run more effective Scrum events.
- Risks of AI (Bias, Data Leaks)
- Using AI responsibly means being aware of risks such as biased outputs and leaking sensitive or proprietary data, and applying guardrails so AI use is safe and appropriate.
- Responsible AI Use
- Keeping humans accountable for decisions and outcomes while AI accelerates routine tasks — verifying AI output and protecting confidential information.