Cross-Framework Reference
Agile Glossary
216 Agile terms normalized across Scrum, SAFe, LeSS, and Nexus. Where frameworks use different names for the same concept — or the same name for different concepts — the glossary surfaces the difference rather than hiding it.
Sourced against the Scrum Guide (Nov 2020), SAFe 6.0, Large-Scale Scrum (Larman & Vodde), and the Nexus Guide.
Acceptance Criteria
Specific conditions a PBI must satisfy to be accepted by the Product Owner.
Adaptation
Adjusting the process or artifacts as soon as variance from acceptable limits is detected.
Architectural Runway
Existing code, components, and infrastructure that enable near-term Features to be implemented without excessive redesign.
Area Product Owner
A LeSS Huge-only role — a PO-like accountability for one Requirement Area when scaling beyond 8 teams.
ART
In Nexus terminology, a collection of 3–9 Scrum Teams working together on a single product.
ART Backlog
A SAFe artifact — the prioritized list of Features and Enablers for an Agile Release Train.
ART Kanban
A SAFe Kanban system at the ART level visualizing Feature flow through the Continuous Delivery Pipeline.
ART Planning Board
A SAFe PI Planning visualization showing Features, dependencies, and milestones across all ART teams.
ART Sync
A SAFe event combining Coach Sync and PO Sync into a single cross-team coordination touchpoint.
Backlog Refinement
An ongoing activity (not a formal Scrum event) to add detail, estimates, and ordering to Product Backlog items.
Batch Size
The amount of work processed together — small batches are favored for faster flow.
BDD
Behavior-Driven Development — extending TDD with natural-language, specification-by-example tests.
Behavior Driven Development
Synonym for BDD.
Benefit Hypothesis
A SAFe artifact at the Feature level — a hypothesis about the business benefit of a Feature.
Built-in Quality
Agile Manifesto principle — continuous attention to technical excellence enhances agility.
Burn Rate
Informal term for how quickly a team is consuming budget or capacity.
Burndown Chart
A chart showing remaining work against time — historically a key Scrum transparency artifact.
Burnup Chart
A chart showing completed work rising against total scope — alternative to burndown favored for scope changes.
Business Value
A SAFe measure assigned by Business Owners to each PI Objective (1–10).
Capability
A Large Solution SAFe artifact — a high-level behavior sized to span multiple ARTs within one PI.
Capacity
The amount of work a team can complete in a Sprint, Iteration, or PI.
Certified LeSS Trainer
Certified LeSS Trainer (CLT) — the only role authorized to deliver Certified LeSS Practitioner courses.
Certified Scrum Trainer
Scrum Alliance's senior trainer certification (CST) authorized to deliver CSM, CSPO, and other foundational courses.
Chief Product Owner
A LeSS Huge role — the overall Product Owner who coordinates multiple Area Product Owners.
Coach of Coaches
Informal SAFe-community term for experienced coaches who mentor newer coaches and SPCs during large transformations.
Coach Sync
Historical term for a cross-team coordination meeting; in SAFe 6.0, formally replaced by "Coach Sync."
Commitment
A Scrum value — personally committing to achieving goals of the Scrum Team.
Compliance Requirements
Legal, regulatory, or contractual requirements governing a product.
Component Teams
Teams organized around technical layers (frontend, backend, database) rather than end-to-end features.
Confidence Vote
A fist-of-five vote at the end of PI Planning gauging each team's confidence in meeting PI Objectives.
Continuous Delivery Pipeline
Deploying software to production frequently and reliably through automation.
Continuous Delivery Pipeline
SAFe's model of the flow from idea to production: Continuous Exploration → Continuous Integration → Continuous Deployment → Release on Demand.
Continuous Deployment
Automated deployment of every code change to production.
Continuous Improvement
Ongoing incremental betterment of process and outcomes — foundational to all frameworks.
Continuous Integration
Integrating code changes frequently (multiple times daily) with automated build and test.
Cost of Delay
The economic impact of delaying an outcome — a key input to SAFe's WSJF prioritization.
Courage
A Scrum value — to do the right thing and work on tough problems.
Cross Functional
A team containing all the skills needed to deliver its work without depending on other teams.
Cumulative Flow Diagram
A chart showing the quantity of work in each workflow state over time.
Customer
The person or organization that uses or pays for the product.
Cycle Time
The elapsed time from when work starts to when it's completed.
Daily Scrum
A 15-minute daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan.
Definition of Done
A formal description of the state of the Increment when it meets required quality measures for release.
Definition of Ready
Informal criteria indicating a Product Backlog item is sufficiently refined to be pulled into a Sprint.
Definition of Workflow
In Kanban, the explicit policies governing how work moves through states.
Demo
Informal term for any event demonstrating working software — usually Sprint Review or System Demo.
Developers
Members of the Scrum Team committed to creating any aspect of a usable Increment each Sprint.
Devops
A cultural and technical movement bridging development and operations for faster, reliable delivery.
Dot Voting
A facilitation technique where participants distribute dots to express preferences among options.
Economic Framework
A SAFe artifact capturing the economic assumptions underlying prioritization decisions.
Empiricism
The basis of Scrum's process control — knowledge comes from experience, decisions from what's known.
Enabler
A SAFe work item supporting future business value — infrastructure, architecture, compliance, or exploration.
Enabler Epic
A Portfolio-level SAFe Epic supporting technical enablement rather than business value directly.
Enterprise Architect
A SAFe Portfolio-level role aligning technical strategy across multiple ARTs and value streams.
Epic
A large body of work — a formal Portfolio artifact in SAFe, informal and PBI-level elsewhere.
Epic Hypothesis Statement
A concise, testable statement describing a SAFe Portfolio Epic's intent and success criteria.
Epic Owner
A SAFe role accountable for shepherding a single Portfolio Epic through the Portfolio Kanban.
Essential SAFe
The minimum SAFe configuration — one ART without Portfolio or Large Solution extensions.
Estimation
The practice of predicting effort or size for upcoming work.
Exploration Enabler
A SAFe Enabler type used for research, spikes, and learning — reducing uncertainty before commitment.
Facilitator
Someone who guides a group through a process toward its own conclusions, without directing outcomes.
Feature
In SAFe, a service fulfilling a stakeholder need — sized to fit in one PI.
Feature Team
Cross-functional, cross-component teams capable of delivering end-to-end customer features without handoffs.
Feature Toggle
A mechanism allowing incomplete or risky features to be deployed without being visible or active.
Fist of Five
A consensus technique where participants show 1–5 fingers to indicate agreement level.
Flow
The movement of value through a system with minimal waste, delay, and interruption.
Flow Metrics
The set of SAFe metrics measuring flow: velocity, predictability, time, load, efficiency, distribution.
Focus
A Scrum value — focus on the work of the Sprint and goals of the Scrum Team.
Full SAFe
The most complete SAFe configuration combining Essential, Large Solution, and Portfolio.
Gemba
Japanese for "the actual place" — where work happens. Used in LeSS and Lean contexts.
Go See
A LeSS principle (from Toyota) of going to where work happens to observe and understand firsthand.
Guardrails
SAFe Lean Budget Guardrails — policies governing how value streams spend their budget.
Increment
A concrete stepping stone toward the Product Goal — a usable, valuable addition meeting the Definition of Done.
Innovation Accounting
Eric Ries's approach to measuring progress on innovation Epics through learning milestones.
Inspect & Adapt
A SAFe event at the end of each PI combining a System Demo, quantitative review, and problem-solving workshop.
Inspection
Frequent examination of artifacts and progress toward goals to detect unwanted variances.
Integrated Product Increment
In Nexus and LeSS, the combined work of all teams integrated into a single usable Increment each Sprint.
Integrated Product Increment
A SAFe artifact — the integrated work of all ART teams in a single testable Iteration increment.
Invest
An acronym for well-formed user stories: Independent, Negotiable, Valuable, Estimable, Small, Testable.
IP Iteration
A SAFe buffer Iteration at the end of each PI for innovation, PI Planning, Inspect & Adapt, and slack.
Kaizen
Japanese for "change for better" — the philosophy of continuous, incremental improvement.
Kanban
A method emphasizing pull, visualization, WIP limits, and flow — distinct from Scrum's timeboxed iterations.
KPI
Key Performance Indicator — a measurable value demonstrating effectiveness toward an objective.
Large Solution SAFe
A SAFe configuration for very large solutions requiring multiple ARTs coordinated by a Solution Train.
Lead Time
The elapsed time from when work is requested to when it's completed.
Lean Agile Mindset
A SAFe term for the combination of Lean, Agile, and SAFe Core Values that underlies all SAFe practice.
Lean Budget
SAFe's approach to funding — allocate budgets to value streams, not projects.
Lean Business Case
A SAFe document describing the outcome, cost, benefit, and leading indicators for a Portfolio Epic.
Lean Metrics
A category of metrics emphasizing flow, value, and waste — cycle time, lead time, throughput, WIP.
Lean Portfolio Management
Senior SAFe role managing Lean Portfolio Management — funding value streams and guiding Epic flow.
Lean Portfolio Management
SAFe's approach to aligning strategy, investment, and execution at the portfolio level.
Lean Thinking
A philosophy emphasizing waste elimination, value flow, and respect for people — adopted into SAFe and LeSS.
LeSS Huge
The LeSS configuration for 8+ teams (up to thousands), dividing the product into Requirement Areas.
LeSS Principles
Ten principles guiding LeSS: Scrum, empiricism, transparency, more with less, whole-product focus, customer-centric, continuous improvement, lean thinking, systems thinking, queueing theory.
Little's Law
Little's Law — average cycle time = work-in-progress ÷ throughput.
Manager-as-teacher
In LeSS, managers serve as teachers applying systems thinking and lean thinking, and practice "Go See."
MMF
Minimum Marketable Feature — the smallest feature that delivers marketable value.
Mob Programming
An extension of pair programming where the whole team works together on one task at one workstation.
Muda
Japanese for "waste" — the core Lean category of activities that don't add customer value.
Multi-team PBR
A LeSS and Nexus practice of cross-team Product Backlog Refinement to align on upcoming work.
MVP
Minimum Viable Product — the smallest product version that delivers value and tests key hypotheses.
Net Promoter Score
A customer satisfaction metric (would you recommend?) used as a SAFe outcome indicator.
Nexus
A SAFe long-lived team of Agile Teams (50–125 people) that incrementally develops and delivers solutions.
Nexus Daily Scrum
A daily cross-team event in Nexus where representatives inspect integration status and identify issues.
Nexus Integration Team
A cross-team group in Nexus accountable for the Integrated Increment every Sprint.
Nexus Integration Team
A specialized SAFe team supporting the ART with infrastructure, integration, and end-to-end testing.
Nexus Sprint Goal
A cross-team goal in Nexus aligning all teams' Sprint work toward a shared outcome.
Nexus Sprint Planning
A Nexus event where team representatives plan cross-team dependencies before per-team Sprint Planning.
Nexus Sprint Retrospective
A cross-team retrospective in Nexus held after team retrospectives each Sprint.
Nexus Sprint Review
A single joint Sprint Review for all teams in the Nexus presenting the Integrated Increment.
Non Functional Requirements
Requirements describing how a system behaves (performance, security, reliability) rather than what it does.
OKR
Objectives and Key Results — a goal-setting framework used alongside Agile.
Openness
A Scrum value — the Scrum Team and stakeholders agree to be open about work and challenges.
Outcome
A measurable change in user behavior, business metrics, or value — as opposed to output (features delivered).
Output
The quantity of work delivered (features shipped, stories completed) — distinct from outcome.
Overall Retrospective
A LeSS cross-team retrospective held after individual team retrospectives each Sprint.
Pair Programming
Two developers working together at one workstation — one driving, one navigating.
PBI
Any item in the Product Backlog — the fundamental unit of work in Scrum.
Perfection Goal
A LeSS-specific concept — the aspirational state of shipping every Sprint with zero defects.
Perfection Goal
SAFe Core Value — quality must be built into every Iteration, Feature, and PI, not inspected in at the end.
PI Objectives
Summary of the business and technical goals a team or ART intends to achieve in a PI.
PI Planning
A 2-day event where all ART members plan the next Program Increment together.
PI Planning
Historical term for longer-horizon planning, largely replaced by PI Planning in SAFe and continuous planning elsewhere.
PI Planning Day 1
First day of PI Planning — business context, architecture vision, and team breakout planning.
PI Planning Day 2
Second day of PI Planning — plan adjustments, final review, risk ROAMing, confidence vote.
PI Roadmap, Solution Roadmap, Portfolio Roadmap
A schedule of events or milestones showing near-term and longer-term deliverables.
Planning Poker
A consensus-based estimation technique using cards showing Fibonacci-like values.
PO Sync
A SAFe event where Product Owners across the ART align on scope, priorities, and feature progress.
Portfolio Backlog
A SAFe artifact — the top-level backlog of approved Portfolio Epics awaiting implementation.
Portfolio Kanban
A SAFe Kanban system at the Portfolio level visualizing Epic flow through Funnel → Analyzing → Portfolio Backlog → Implementing → Done.
Portfolio SAFe
A SAFe configuration adding Lean Portfolio Management — funding, strategy, and Epic flow above ART level.
Post PI Planning
In Large Solution SAFe, a wrap-up event consolidating ART-level PI Plans into a Solution-level view.
Pre PI Planning
In Large Solution SAFe, a preparatory event where Solution-level alignment precedes per-ART PI Planning.
Predictability Measure
A SAFe PI-level metric comparing planned business value vs. achieved business value across teams.
Product Backlog
An ordered list of everything known to be needed in the product — the single source of work.
Product Goal
A long-term objective describing a future state of the product — introduced in the 2020 Scrum Guide.
Product Manager
A strategic SAFe role owning ART-level product vision and the ART Backlog; has no direct equivalent in Scrum, LeSS, or Nexus.
Product Owner
The single person accountable for maximizing the value of the product and managing the Product Backlog.
Product Vision
A concise description of the desired future state of the product, guiding long-term direction.
Professional Scrum Trainer
Scrum.org's trainer certification authorized to deliver PSM, PSPO, PSD, and other professional Scrum courses.
Refactoring
Restructuring existing code without changing its external behavior to improve design quality.
Release on Demand
A SAFe practice of releasing functionality to customers when it provides value, not on a fixed cadence.
Release Train Engineer
A SAFe-specific servant leader and chief facilitator for the Agile Release Train (50–125 people).
Requirement Area
In LeSS Huge, a division of the product assigned to 4–8 teams led by an Area Product Owner.
Respect
A Scrum value — respect team members as capable, independent people.
Retrospective
Any structured reflection event aimed at inspecting and adapting team process.
Retrospective Techniques
Facilitation formats for Sprint Retrospectives — Start/Stop/Continue, 4Ls, Sailboat, etc.
Roam
SAFe risk categorization at PI Planning: Resolved, Owned, Accepted, Mitigated.
Roam Risks
A SAFe risk categorization at PI Planning: Resolved, Owned, Accepted, Mitigated.
SAFe Core Values
SAFe's four Core Values: alignment, built-in quality, transparency, program execution.
SAFe Practice Consultant
A person who helps individuals, teams, or organizations improve Agile practices and outcomes.
Scrum Master
Accountable for the team's effectiveness, coaching the team and organization in Scrum, and removing impediments.
Scrum of Scrums
A SAFe event where Scrum Masters across the ART sync on impediments, flow, and coaching.
Scrum Team
A SAFe term for a cross-functional 5–11 person team — roughly equivalent to a Scrum Team.
Scrum Team
A small (≤10) cross-functional team consisting of one Scrum Master, one Product Owner, and Developers.
Scrum Values
The five values of Scrum: commitment, courage, focus, openness, respect.
Scrumban
A hybrid approach combining Scrum's events and roles with Kanban's WIP limits and pull.
Self Organizing
Teams deciding how to accomplish work — the pre-2020 term that Scrum rebranded to "self-managing."
Self Selection
A practice where team members choose their team or work rather than being assigned.
Self-management
Teams internally decide who does what, when, and how — the successor term to "self-organizing" in the 2020 Scrum Guide.
Servant Leader
A leadership philosophy prioritizing service to others — core to the Scrum Master and RTE roles.
Servant Leadership
A leadership philosophy prioritizing service to others, drawn from Robert Greenleaf's work.
Shared Services
SAFe specialists outside Agile Teams whose skills are needed by multiple teams but not full-time.
Solution Architect / Engineer
A SAFe role providing architectural direction across a Solution Train's multiple ARTs.
Solution Backlog
A SAFe Large Solution artifact — Capabilities prioritized across multiple ARTs contributing to one Solution.
Solution Demo
In Large Solution SAFe, a PI-end demonstration of the integrated Solution across multiple ARTs.
Solution Increment
In Large Solution SAFe, the combined System Increments from multiple ARTs forming a single Solution.
Solution Intent
A SAFe Large Solution repository of fixed and variable Solution design decisions.
Solution Management
SAFe Large Solution role responsible for the Solution Backlog and Solution vision.
Solution Train
A SAFe Large Solution organizing unit — multiple ARTs building a large Solution together.
Solution Train Engineer
A SAFe role facilitating Solution Trains (multiple ARTs coordinating on one large solution).
SPC / SPCT
A SAFe certified change agent (formerly SPCT/SPC) who trains and coaches organizations implementing SAFe.
Specification By Example
A technique for specifying requirements through concrete examples that can become tests.
Spike
A time-boxed investigation or research activity, named by XP and adopted across frameworks.
Sprint
A timeboxed iteration (1–4 weeks) during which a usable product Increment is created.
Sprint
SAFe's name for a 2-week Sprint, nested inside an 8–12 week Program Increment.
Sprint Backlog
The set of Product Backlog items selected for the Sprint plus a plan for delivering the Increment.
Sprint Goal
The single objective for the Sprint that commits the Scrum Team to a coherent purpose.
Sprint Kickoff
Informal name for the transition into a new Sprint, usually encompassing Sprint Planning.
Sprint Planning
The event that kicks off the Sprint by deciding what can be delivered and how the work will be done.
Sprint Planning
SAFe's name for Sprint Planning — a team-level event where the team commits to Iteration goals.
Sprint Planning Part 1
A LeSS multi-team planning event where all teams and the PO align on priorities and self-select work.
Sprint Planning Part 2
In LeSS, the per-team Sprint Planning phase following the multi-team Part 1.
Sprint Retrospective
An event at the end of the Sprint for the Scrum Team to inspect itself and plan improvements.
Sprint Retrospective
SAFe's name for the Sprint Retrospective — a biweekly team improvement event.
Sprint Review
An event at the end of the Sprint to inspect the Increment and adapt the Product Backlog.
Stakeholders
Key SAFe stakeholders accountable for business outcomes, ROI, and governance of the ART.
Stakeholders
Anyone with an interest in the product — customers, users, sponsors, or others impacted by outcomes.
Standup
Informal term for the Daily Scrum / Daily Stand-up.
Story
A short, simple description of functionality told from a user's perspective — the smallest planning unit in SAFe.
Story Points
A relative unit of estimation used to size Product Backlog items.
Stretch Objective
A SAFe PI Objective that is planned but uncommitted — a target to pursue if capacity allows.
System Architect / Engineer
A SAFe role defining overall architecture, NFRs, and architectural runway across the ART.
System Demo
A SAFe event demonstrating the integrated system to stakeholders every Iteration (2 weeks).
Systems Thinking
Understanding the whole system rather than optimizing parts — explicit in LeSS, embedded in SAFe.
T-Shaped
A skill profile where a person has deep expertise in one area and broad competence across others.
T-Shirt Sizing
Rough categorical sizing (XS/S/M/L/XL) used for larger items before detailed estimation.
TDD
Test-Driven Development — writing tests before implementation code.
Team Backlog
A SAFe artifact — an Agile Team's prioritized list of Stories, Spikes, Enablers, and Defects.
Team Health
A qualitative assessment of team well-being, often captured through surveys or retrospective themes.
Team Kanban
A SAFe team-level Kanban system visualizing Story and Enabler flow.
Team Velocity
Synonym for velocity; distinguishes team-level from ART velocity in SAFe.
Technical Debt
The implied cost of future rework caused by choosing a quick solution instead of a better one.
Three CS
Card, Conversation, Confirmation — Ron Jeffries' heuristic for user stories.
Throughput
The amount of work completed per unit of time.
Transparency
One of Scrum's three pillars — all information affecting outcomes must be visible to those making decisions.
Trunk Based Development
A branching model where developers integrate to a single main branch at least daily.
Value Stream
The sequence of steps an organization uses to deliver value to a customer.
Value Stream Coordinator
Informal SAFe role coordinating across ARTs within a single development value stream.
Value Stream Mapping
A Lean technique for visualizing steps, delays, and handoffs from idea to customer to identify waste.
Velocity
A team's measure of how much work they complete per Sprint, typically in story points.