33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business agility
- The ability of an organization to sense and respond to market changes quickly and confidently, delivering value continuously while maintaining stability and quality across the enterprise.
- SAFe core competencies
- Seven competencies: Lean-Agile Leadership, Team and Technical Agility, Agile Product Delivery, Enterprise Solution Delivery, Lean Portfolio Management, Organizational Agility, and Continuous Learning Culture.
- SAFe core values
- Alignment, Transparency, Respect for People, and Relentless Improvement; newer versions add Built-in Quality as a fifth value that teams apply to every increment they deliver.
- Decentralize decision-making
- SAFe Principle #9: push decisions to the lowest competent level by defining clear decision rights and boundaries, so teams act fast without waiting for leadership approval.
- Take an economic view
- SAFe Principle #1: sequence work and make decisions to maximize economic outcomes, considering cost of delay, capacity, and the trade-offs of each option.
- Servant leader
- The SAFe Scrum Master's stance: serving the team, Product Owner, and organization by coaching, facilitating, removing impediments, and enabling self-management rather than directing work.
- Scrum Master in SAFe
- A servant leader and team coach who facilitates team events, supports PI Planning, removes impediments, coaches the team and Product Owner, and represents the team in the Scrum of Scrums.
- Release Train Engineer
- The ART's chief Scrum Master and servant leader; facilitates PI Planning, ART Sync, and Inspect & Adapt, and manages cross-team risks, dependencies, and continuous improvement.
- Scrum of Scrums
- A recurring coordination event where Scrum Masters and Team Coaches share progress, surface impediments, and manage cross-team dependencies across the Agile Release Train during the PI.
- Product Owner in SAFe
- The team member who owns the team backlog, defines and prioritizes stories, accepts completed work against the Definition of Done, and contributes to features and PI objectives.
- Agile team size
- SAFe Agile Teams are typically 3 to 11 members, cross-functional and self-managing, with 5 to 9 members being the most common size for effective collaboration.
- Definition of Done
- An explicit, team-owned checklist of quality criteria a story must satisfy to be considered complete; work that fails the DoD returns to the backlog instead of counting as done.
- Iteration Goals
- A short set of business-oriented outcomes the team commits to for the iteration; they summarize the value of planned stories and align the team with PI objectives.
- Built-in Quality
- A SAFe value and practice ensuring quality is designed and verified continuously through pair work, test-driven development, automated testing, continuous integration, and refactoring.
- Enablers
- Backlog items that support delivery of future business value rather than delivering it directly; types include Exploration, Architecture, Infrastructure, and Compliance enablers.
- Iteration cadence
- A fixed, protected timebox, commonly two weeks, containing Iteration Planning, daily stand-ups, Iteration Review, and Retrospective; the length does not stretch to fit work.
- Tuckman stages
- Forming, Storming, Norming, Performing, and Adjourning; teams pass through these stages, and the Scrum Master shifts from directing to delegating as maturity grows.
- Psychological safety
- The shared belief that team members can speak up, admit mistakes, and challenge ideas without punishment; it is a prerequisite for learning and high performance.
- Intrinsic motivation
- Drive that comes from autonomy, mastery, and purpose rather than external rewards; SAFe Principle #8 states engaged, motivated knowledge workers are essential to effectiveness.
- Working agreements
- Explicit team norms covering communication, core hours, decision-making, and tooling; especially important for distributed teams to maintain trust and coordination.
- Retrospective improvement actions
- A small number of owned, measurable actions the team commits to after each retrospective; unresolved systemic issues escalate to the ART's Inspect & Adapt event.
- PI Planning
- A two-day event where all teams on an Agile Release Train align to a shared mission, produce PI Objectives and a Program Board, and identify risks and dependencies.
- Program Increment
- A fixed timebox of typically 8 to 12 weeks, often five two-week iterations, ending with an Innovation and Planning iteration that also hosts Inspect & Adapt.
- PI Objectives
- Business summaries of what a team intends to deliver in the PI; each is scored 1 to 10 for business value, and the sum gives the team's planned business value.
- Program Board
- A visual planning artifact showing features, milestones, and cross-team dependencies for the PI; dependencies are highlighted and tracked throughout execution.
- ART Sync
- A weekly event where Scrum Masters, Team Coaches, the RTE, and Product Management coordinate progress, resolve dependencies, and address risks across the Agile Release Train.
- System Demo
- An event at the end of every iteration where all teams' work is integrated and demonstrated together, letting stakeholders inspect the working increment and give feedback.
- Inspect and Adapt
- The PI-closing event where the ART reviews flow, quality, and predictability metrics, runs a problem-solving workshop, and produces improvement backlog items for the next PI.
- Lean-Agile Leaders
- Leaders who lead the transformation by example: they adopt and teach SAFe principles, create psychological safety, remove impediments, and unlock intrinsic motivation across the organization.
- Product Manager
- The role that owns the ART backlog, defines and prioritizes features, and validates that delivered features achieve the intended customer and business outcomes.
- Lean Portfolio Management
- The function that aligns strategy with execution using the Portfolio Kanban, Lean Budgets, and value stream funding, and approves epics through a lightweight business case.
- SAFe Implementation Roadmap
- A twelve-step path from reaching the tipping point through ART launch, expansion, and flow optimization; the first ART typically launches around step five.
- Continuous Delivery Pipeline
- Four aspects - Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand - that move value from idea to customer continuously.