SA — AI-EMPOWERED SAFe Agilist (Leading SAFe) Quick Reference

Compact independent quick reference for the Scaled Agile SA exam: SAFe roles, PI Planning, Lean Portfolio Management, flow, WSJF, DevOps, and AI-enabled decision points.

Exam identity and use

ItemReference
ProviderScaled Agile
Official exam titleAI-EMPOWERED SAFe Agilist (SA) (Leading SAFe)
Exam codeSA
Page purposeIndependent Quick Reference for last-mile review and scenario practice

Use this as a compact decision aid: connect SAFe principles to roles, events, artifacts, Lean Portfolio Management, PI Planning, flow, DevOps, and AI-enabled ways of working. For scenario questions, prefer the answer that improves value flow, transparency, alignment, customer outcomes, and decentralized decision-making within clear economic guardrails.

SAFe big picture

    flowchart LR
	    A[Strategic Themes] --> B[Portfolio Vision and Epics]
	    B --> C[Lean Portfolio Management]
	    C --> D[Value Streams and ARTs]
	    D --> E[ART Backlog: Features and Enablers]
	    E --> F[Team Backlogs: Stories]
	    F --> G[Integrated Increments]
	    G --> H[System Demo and Measure]
	    H --> I[Release on Demand]
	    H --> E
ConceptHigh-yield meaningExam trap
Business AgilityAbility to compete and thrive by responding quickly to market, customer, and business changesNot just “doing Scrum at scale”
Agile Release TrainLong-lived team of Agile Teams aligned to a value stream and common cadenceDo not treat ART as a temporary project team
Value StreamSequence of activities needed to deliver valueDo not organize primarily around functional departments
PIPlanning Interval; timebox for ART planning, execution, review, and learningPI is not a waterfall phase gate
CadenceRegular rhythm for planning, integration, demos, and learningCadence does not mean releases happen only on fixed dates
Release on DemandCapability to release value when customers/business are readyDeployment and release are not the same
Lean Portfolio ManagementConnects strategy, investment funding, Agile portfolio operations, and Lean governanceNot a traditional annual project funding office
AI-enabled workAI augments analysis, synthesis, planning, and learningAI does not replace accountability, customer validation, or SAFe economics

AI-empowered SAFe Agilist lens

For the AI-EMPOWERED SAFe Agilist (SA) (Leading SAFe), answer AI-related scenarios through SAFe principles: economic thinking, systems thinking, transparency, fast feedback, decentralized decisions, and respect for people.

AI use caseGood SAFe-aligned usePoor exam answer
Customer discoverySummarize interviews, cluster feedback, draft personas, identify themes for validationTreat AI output as verified customer truth
Backlog refinementDraft feature hypotheses, acceptance criteria, story splits, dependency questionsLet AI prioritize without WSJF, context, or human review
PI PlanningSurface risks, draft objective wording, analyze dependencies, suggest ROAM promptsReplace team planning conversations with generated plans
Portfolio analysisSummarize epic hypotheses, compare options, identify data gapsBypass LPM governance or participatory funding
Flow improvementAnalyze bottlenecks, WIP, handoffs, queues, escaped defectsOptimize local utilization while worsening system flow
Inspect and AdaptSummarize retrospective inputs and propose improvement experimentsSkip root-cause analysis because AI produced an answer
Knowledge workCreate drafts, check consistency, explain concepts, support learningHide AI usage when transparency is expected

Responsible AI checklist for SAFe scenarios

  • Define the decision, outcome, and constraints before prompting.
  • Protect confidential, customer, employee, and proprietary information.
  • Validate AI outputs with domain experts, real data, and customer feedback.
  • Watch for bias, hallucination, stale assumptions, and overconfidence.
  • Keep humans accountable for prioritization, commitments, governance, and ethical trade-offs.
  • Prefer AI to increase learning speed, not to centralize control or reduce collaboration.

Lean-Agile mindset

SAFe’s Lean-Agile mindset combines the Agile Manifesto with Lean product development and systems thinking.

AreaQuick reference
Agile value preferenceIndividuals/interactions, working solutions, customer collaboration, responding to change
SAFe House of Lean roofValue
House of Lean pillarsRespect for People and Culture, Flow, Innovation, Relentless Improvement
House of Lean foundationLeadership
Leadership behaviorModel principles, create alignment, enable flow, decentralize decisions, remove impediments
Exam preferenceChoose collaboration, transparency, fast feedback, and working integrated solutions over command-and-control planning

SAFe core values

Core valueWhat it looks likeCommon wrong turn
AlignmentShared vision, strategy, roadmaps, PI objectives, cadence, prioritiesLocal optimization by teams or departments
TransparencyVisible work, risks, impediments, progress, quality, and factsReporting only “green” status
Respect for PeopleEmpowered knowledge workers, collaboration, psychological safety, customer empathyTreating people as interchangeable capacity
Relentless ImprovementInspect and Adapt, problem-solving, innovation, learning culture“Plan better next time” without systemic change

Ten SAFe Lean-Agile principles

#PrinciplePractical exam behavior
1Take an economic viewMake trade-offs using value, cost, risk, timing, and opportunity cost
2Apply systems thinkingOptimize the whole value stream, not one team, function, or metric
3Assume variability; preserve optionsKeep options open early; narrow with learning and evidence
4Build incrementally with fast, integrated learning cyclesIntegrate, demo, test, and learn frequently
5Base milestones on objective evaluation of working systemsPrefer evidence from working solutions over document sign-offs
6Make value flow without interruptionsVisualize work, limit WIP, reduce queues, manage bottlenecks
7Apply cadence; synchronize with cross-domain planningAlign teams through common events and planning intervals
8Unlock intrinsic motivation of knowledge workersProvide autonomy, mastery, purpose, and mission clarity
9Decentralize decision-makingPush frequent, local, time-critical decisions to the people closest to the work
10Organize around valueStructure ARTs and portfolios around value streams

Centralize vs decentralize decisions

Decision typePrefer centralization when…Prefer decentralization when…
Strategic investmentLong-lasting, broad economic impact, significant economies of scaleLocal feature trade-off within agreed strategy and guardrails
ArchitectureEnterprise-wide standards or irreversible platform choicesTeam-level design implementation choices
Compliance/governancePolicy, auditability, or common risk approach is neededEvidence gathering and built-in quality can happen continuously in teams
Backlog sequencingPortfolio-level epic or funding decisionFeature/story order within ART/team context
Operational issueSystemic impediment across ARTsTeam can resolve quickly with local knowledge

Business Agility and core competencies

CompetencyFocusHigh-yield dimensions
Lean-Agile LeadershipLeaders drive and model changeLeading by example, mindset and principles, leading change
Team and Technical AgilityAgile Teams and teams of Agile Teams deliver qualityAgile Teams, ARTs, built-in quality
Agile Product DeliveryCustomer-centric, value-driven deliveryCustomer centricity/design thinking, cadence and release on demand, DevOps/CDP
Enterprise Solution DeliveryLarge, complex solution developmentLean systems engineering, solution coordination, evolving live systems
Lean Portfolio ManagementStrategy, funding, governanceStrategy and investment funding, Agile portfolio operations, Lean governance
Organizational AgilityAdaptable people, operations, and strategyLean-thinking people, Lean business operations, strategy agility
Continuous Learning CultureLearning and improvement at scaleLearning organization, innovation culture, relentless improvement

Configurations and levels

ConfigurationUse when…Adds/contains
Essential SAFeOne or more ARTs deliver valueTeam and ART levels; foundational SAFe
Large Solution SAFeMultiple ARTs/suppliers build a large complex solutionSolution Train, capabilities, solution intent, pre/post-PI planning
Portfolio SAFeStrategy, investment funding, and governance must align to value streamsLPM, portfolio Kanban, epics, strategic themes
Full SAFeEnterprise requires portfolio plus large-solution coordinationAll major levels and competencies

Value streams and ARTs

TermMeaningExam distinction
Operational Value StreamSteps used to deliver products/services to customers or usersDescribes how the business delivers value
Development Value StreamPeople, systems, and steps that build solutions used by operational value streamsOften where ARTs are organized
Agile Release TrainLong-lived virtual organization of Agile Teams delivering on a shared missionAligns to value; not a project team
Solution TrainCoordinates multiple ARTs and suppliers for large solutionsUsed in Large Solution context
ART launchForm teams, train people, prepare backlog, establish cadence, conduct PI PlanningLaunching requires leadership preparation, not just scheduling an event

Roles and responsibilities

RolePrimary accountabilityKey interactionsExam trap
Lean-Agile LeaderModel mindset, lead change, create environment for flowAll levelsDelegating transformation only to coaches
Business OwnerBusiness outcomes, governance, economic decisions, PI objective valueRTE, Product Management, teamsBusiness Owners assign business value to PI objectives
Release Train EngineerServant leader and chief facilitator for ART executionScrum Masters/Team Coaches, Product Management, System Architect, Business OwnersRTE does not own product priorities
Product ManagementCustomer needs, ART backlog, features, roadmap, visionPOs, Business Owners, customersProduct Management owns features, not every team story
Product OwnerTeam backlog, story clarity, iteration priorities, acceptanceTeam, Product ManagementPO does not set portfolio strategy alone
Scrum Master / Team CoachTeam facilitation, flow, improvement, impediment removalTeam, RTENot a status collector or task assigner
Agile TeamDefine, build, test, and deliver stories and incrementsPO, SM/Team Coach, other teamsQuality is not handed off to a separate phase
System Architect / EngineeringTechnical vision, architecture runway, NFRs, design guidanceProduct Management, teamsArchitecture is intentional and emergent, not big design up front
System TeamIntegration, environments, tooling, test support, demo supportART teams, RTEDoes not absolve teams from integrating and testing
Epic OwnerDrives portfolio epic through Kanban and MVP learningLPM, stakeholders, ARTsDoes not guarantee full funding before MVP evidence
Lean Portfolio ManagementStrategy, investment funding, Agile portfolio operations, Lean governanceExecutives, Enterprise Architects, Epic OwnersLPM funds value streams, not just projects
Enterprise ArchitectEnterprise technical strategy and architectural runwayLPM, System/Solution ArchitectsArchitecture must support business strategy and flow
Solution Train EngineerFacilitates Solution Train events and coordinationRTEs, Solution ManagementUsed for large-solution coordination

Artifacts by level

LevelBacklog itemPlanning artifactOutcome/evidence
PortfolioEpicPortfolio vision, strategic themes, Lean business caseMVP results, pivot/persevere decision, portfolio outcomes
Large SolutionCapabilitySolution intent, solution roadmap, solution backlogIntegrated solution demo, compliance/objective evidence
ARTFeatureART backlog, PI objectives, program board, roadmapSystem demo, ART predictability, released value
TeamStoryTeam backlog, iteration goals, Definition of DoneWorking tested stories, iteration review
EnablersEnabler epic/capability/feature/storyArchitecture runway, exploration, infrastructure, compliance workFuture business features can flow faster and safely

Backlog item sizing distinctions

ItemTypical scopeOwner focus
EpicSignificant initiative, often spans PIs and ARTsEpic Owner and LPM
CapabilityLarge-solution behavior, may span ARTsSolution Management / Solution Train
FeatureService or functionality deliverable by an ART in a PIProduct Management
StorySmall slice deliverable by a team in an iterationProduct Owner and Agile Team
EnablerWork that supports future business functionalityArchitects, teams, Product Management/POs

Cadences and events

EventLevelPurposeKey outputs
Iteration PlanningTeamPlan stories for iterationIteration goals, committed work
Daily Stand-upTeamCoordinate, surface impedimentsUpdated plan, impediments
Backlog RefinementTeam/ARTClarify, split, estimate, prepare workReady stories/features
Iteration ReviewTeamDemonstrate completed workFeedback and accepted stories
Iteration RetrospectiveTeamImprove team processImprovement actions
PI PlanningARTAlign all teams to mission, features, dependencies, risksTeam PI objectives, program board, risks, confidence vote
ART SyncARTCoordinate executionDependency and impediment visibility
Scrum of ScrumsARTTeam execution coordinationCross-team impediment handling
PO SyncARTBacklog, scope, feature, and priority coordinationAligned priorities and scope trade-offs
System DemoARTDemonstrate integrated work from the ARTObjective progress and feedback
Inspect and AdaptARTEnd-of-PI demo, metrics, problem-solvingImprovement backlog items
IP IterationARTInnovation, planning, learning, final validationPI Planning readiness and improvement work
Portfolio SyncPortfolioCoordinate portfolio executionEpic, dependency, and impediment alignment
Strategic Portfolio ReviewPortfolioReview strategy, budgets, portfolio performanceAdjusted direction and investment decisions

PI Planning quick reference

PI Planning inputs and outputs

InputsOutputs
Business contextCommitted team PI objectives
Product/Solution visionUncommitted objectives where appropriate
Architecture vision and development practicesProgram board with dependencies and milestones
Prioritized ART backlogIdentified risks and ROAM status
Team capacity and known constraintsART PI confidence vote
Business Owners and key stakeholders presentAlignment on mission and priorities

Typical PI Planning flow

StepWhat happensWatch for
Business contextLeaders explain market, strategy, and business prioritiesTeams need economic context, not just feature lists
Product/Solution visionProduct Management presents top features and directionVision connects work to customer value
Architecture visionArchitects explain runway, NFRs, and technical guidanceArchitecture supports flow, quality, and future options
Team breakoutsTeams plan stories, dependencies, risks, objectivesTeams own planning; managers do not assign detailed tasks
Draft plan reviewTeams present draft plans, risks, and dependenciesMake conflicts visible early
Management review/problem-solvingLeaders address scope, people, dependency, and priority issuesThis is not a private re-planning command session
Final plan reviewTeams present final objectives and plansBusiness value is assigned to objectives
ART PI risksRisks are ROAMedRisks are not hidden to preserve confidence
Confidence voteTeams and ART vote on plan confidenceLow confidence triggers discussion/rework
Planning retrospectiveImprove next PI PlanningRelentless improvement applies to planning too

ROAM risk handling

ROAM statusMeaning
ResolvedRisk is no longer a concern
OwnedSomeone accepts responsibility to manage it
AcceptedRisk is understood and accepted as is
MitigatedAction has reduced probability or impact

PI objectives

ConceptReference
Team PI objectivesSummarize planned business and technical goals for the PI
Business valueAssigned by Business Owners to objectives
Committed objectivesObjectives the team agrees to deliver if conditions hold
Uncommitted objectivesProvide flexibility for uncertainty without overcommitting
ART PI objectivesSummarized from team objectives to communicate ART outcomes
Exam trapFeatures are important inputs, but PI objectives communicate business outcomes and alignment

Inspect and Adapt

PartPurposeExam focus
PI System DemoDemonstrate integrated work from the full PIObjective evidence from working solution
Quantitative and qualitative measurementReview predictability, flow, quality, feedbackMetrics guide learning, not blame
Problem-solving workshopIdentify systemic root causes and improvement actionsFix the system, not individuals

Problem-solving pattern

  1. Agree on the problem.
  2. Apply root-cause analysis, such as 5 Whys or fishbone.
  3. Identify the biggest root cause or leverage point.
  4. Restate the problem based on learning.
  5. Brainstorm solutions.
  6. Create improvement backlog items.
  7. Follow through in the next PI or iteration.

Lean Portfolio Management

LPM responsibilityWhat it doesKey artifacts/events
Strategy and investment fundingAligns portfolio to enterprise strategy and funds value streamsStrategic themes, portfolio vision, portfolio canvas, budgets
Agile portfolio operationsCoordinates execution across value streamsPortfolio sync, value stream coordination, operational support
Lean governanceForecasting, budgeting, measuring, compliance, and oversight using Lean-Agile practicesGuardrails, objective evidence, portfolio metrics

Lean budget guardrails

GuardrailPractical meaning
Guide investments by horizonBalance current, emerging, future, and retiring investments
Apply capacity allocationReserve capacity for different work types such as features, enablers, maintenance, innovation
Approve significant initiativesUse portfolio Kanban, Lean business cases, and MVP evidence for epics
Continuous Business Owner engagementKeep economic decision-makers involved throughout execution

Portfolio Kanban

StatePurposeKey decision
FunnelCapture new ideasIs this worth exploring?
ReviewingInitial assessmentDoes it align to strategy?
AnalyzingDefine epic hypothesis, MVP, cost, impact, alternativesIs there enough evidence for a Lean business case?
Portfolio BacklogApproved and prioritizedWhen should it be implemented?
ImplementingMVP and epic executionContinue, pivot, persevere, or stop?
DoneEpic is completed or stoppedWere outcomes achieved and learning captured?

Epic hypothesis and MVP

ItemMeaning
Epic hypothesis statementStates expected benefit, leading indicators, business outcomes, and scope
Lean business caseLightweight economic justification for a significant initiative
MVPMinimum solution needed to test the epic hypothesis and produce learning
Pivot/persevere decisionContinue, change direction, or stop based on evidence
TrapMVP is not the smallest list of requirements management will accept; it is a learning vehicle

WSJF and economic prioritization

Weighted Shortest Job First is used to sequence jobs economically where relative cost of delay and job size are known.

\[ \text{WSJF} = \frac{\text{Cost of Delay}}{\text{Job Size}} \]\[ \text{Cost of Delay} = \text{User-Business Value} + \text{Time Criticality} + \text{Risk Reduction / Opportunity Enablement} \]
ComponentMeaning
User-business valueRelative value to customers and the business
Time criticalityHow value changes with time, deadlines, market windows, or urgency
Risk reduction / opportunity enablementLearning, risk removal, future options, architecture runway, compliance enablement
Job sizeRelative effort, complexity, duration, and uncertainty
Highest WSJFUsually sequenced first, subject to dependencies, capacity allocation, and strategy

Example:

Work itemUser-business valueTime criticalityRR/OECost of DelayJob sizeWSJFSequence
Feature A87520102.0After B
Feature B5431234.0First

Exam traps:

  • WSJF uses relative estimates; do not over-precision it.
  • A large high-value item may rank lower than a smaller urgent item.
  • Enablers can score high when they reduce risk or enable future value.
  • WSJF informs sequencing; it does not replace strategy, dependencies, or capacity allocation.

Flow, metrics, and improvement

Metric/conceptMeaningHealthy use
Flow distributionMix of work types, such as features, defects, risks, debt, enablersCheck if capacity matches strategy
Flow velocityAmount of work completed over timeObserve trends, not individual productivity
Flow timeTime from work start to completionReduce queues, waits, rework, and handoffs
Flow loadWork in processLimit WIP to improve flow
Flow efficiencyActive work time compared with total elapsed timeIdentify waiting and delays
PredictabilityPlanned business value compared with actual business valueImprove planning and execution reliability
Escaped defectsDefects found after release or later stagesImprove built-in quality and feedback loops
Employee engagementMotivation and sustainabilityRespect for people and durable delivery
Customer outcomesValue realized by users/customersAvoid measuring only output volume

ART predictability is commonly reviewed using planned versus actual business value.

\[ \text{ART Predictability} = \frac{\text{Actual Business Value}}{\text{Planned Business Value}} \times 100\% \]

Use metrics for learning and systemic improvement. In SAFe scenarios, avoid punitive uses of metrics, local optimization, or maximizing utilization at the expense of flow.

DevOps and Continuous Delivery Pipeline

ElementPurposeExamples
Continuous ExplorationDiscover customer needs and define what to buildPersonas, journey maps, hypotheses, features, MVPs
Continuous IntegrationBuild, integrate, test, and validate frequentlyAutomated tests, CI, trunk-based practices, integrated demos
Continuous DeploymentMove validated changes toward production-like or production environmentsDeployment automation, feature toggles, canary releases
Release on DemandRelease value when business and customers are readyDark launches, phased rollout, rollback/recovery practices

CALMR

CALMR elementMeaning
CultureShared responsibility for delivery, operations, learning, and quality
AutomationAutomate build, test, deployment, environment, and compliance evidence where useful
Lean FlowSmall batches, WIP limits, fast feedback, reduced handoffs
MeasurementMeasure value, flow, quality, recovery, and outcomes
RecoveryDesign for fast detection, rollback, restore, and learning

Built-in quality

PracticeWhy it matters
Definition of DoneShared quality threshold for completed work
Test-first / test automationFast feedback and regression protection
Continuous integrationFrequent integration reduces late surprises
Pairing/peer reviewImproves knowledge sharing and quality
RefactoringMaintains design quality and adaptability
Collective ownershipReduces bottlenecks around specialists
Nonfunctional requirementsMakes performance, security, reliability, usability, and compliance visible
Shift-left qualityPrevents defects rather than detecting them late

Exam preference: quality is built into every increment by every team; it is not inspected in at the end by a separate group.

Customer centricity and design thinking

ConceptQuick reference
Customer centricityFocus decisions on customer needs and value
Design thinkingUnderstand the problem and design the right solution
DesirableCustomers/users want it
FeasibleThe organization can build and operate it
ViableIt supports business goals
SustainableIt can be maintained responsibly over time
GembaGo to where the work happens to understand reality
PersonaRepresentation of a user/customer segment
Customer journey mapVisualizes user experience across touchpoints
Whole product thinkingDeliver the full experience needed for value, not only core features
Hypothesis-driven developmentTreat product decisions as testable assumptions

Architecture and enablers

ConceptMeaningExam distinction
Architecture runwayExisting technical foundation that supports near-term featuresBuilt incrementally, not all upfront
Intentional architecturePlanned architecture guidance for alignment and NFRsBalances emergent design
Emergent designDesign evolves from team learning and implementationDoes not mean no architecture
Enabler workExploration, architecture, infrastructure, compliance, or technical work supporting future valueShould be visible in backlogs
Set-based designPreserve multiple options until evidence supports narrowingAvoid premature point solutions
Solution intentRepository for intended and actual solution behaviorUseful in large, complex, regulated, or long-lived solutions

Implementation roadmap

StepPurpose
Reach the tipping pointEstablish need and urgency for change
Train Lean-Agile change agentsBuild internal change capability
Train executives, managers, and leadersAlign leadership on mindset and responsibilities
Create a Lean-Agile Center of ExcellenceCoordinate transformation support
Identify value streams and ARTsOrganize around value
Create the implementation planSequence ART launches and change work
Prepare for ART launchTrain roles, refine backlog, set up tooling and logistics
Train teams and launch the ARTConduct training and PI Planning
Coach ART executionSupport early execution, demos, I&A, and improvement
Launch more ARTs and value streamsExpand based on learning
Extend to the portfolioApply LPM, Lean budgets, and portfolio flow
AccelerateSustain relentless improvement and business agility

Scenario decision table: what should the SAFe leader do next?

ScenarioBest next actionAvoid
Teams are busy but value is not flowingVisualize work, identify bottlenecks, reduce WIP, address queuesPush for higher utilization
Stakeholder demands new mid-PI scopeDiscuss with PO/Product Management, assess impact, trade off transparentlyAdd work silently and keep commitments unchanged
Teams disagree on prioritiesReconnect to vision, PI objectives, WSJF, Business Owners, and economic contextEscalate immediately to command-and-control assignment
Dependency threatens PI objectiveMake dependency visible, coordinate in ART Sync, adjust scope/objectives if neededHide risk until the System Demo
Architecture work is ignoredRepresent it as enablers, connect to risk reduction/opportunity enablementLet architects work outside the backlog
Business value is unclearEngage customers, Product Management, POs, and Business Owners to clarify outcomesContinue building because capacity is available
PI confidence vote is lowDiscuss concerns, revise plan, address risks, revote if neededPressure teams to vote higher
Defects appear lateStrengthen built-in quality, CI, test automation, and smaller batchesAdd a late hardening phase as the main answer
Portfolio has too many initiativesUse portfolio Kanban, WIP limits, WSJF, strategic themes, and budget guardrailsStart everything and hope teams absorb it
AI suggests a priority orderValidate assumptions, compare with WSJF/strategy, involve accountable humansAccept AI ranking as authoritative
Compliance evidence is neededBuild evidence incrementally into the delivery systemWait for a final compliance phase
Multiple ARTs need coordinationUse Solution Train mechanisms, pre/post-PI planning, shared intent, and dependency managementForce all details through one team-level board

Common exam traps

TrapCorrect SAFe interpretation
“SAFe is scaled Scrum.”SAFe combines Lean, Agile, DevOps, systems thinking, portfolio governance, and value-stream organization.
“The project manager assigns work during PI Planning.”Teams plan their work; leaders set context, priorities, and constraints.
“Business Owners write stories.”POs manage team backlogs and stories; Business Owners provide business context and value feedback.
“Product Owner and Product Management are the same.”PO focuses on team backlog/stories; Product Management focuses on ART backlog/features/vision.
“Commitment is to every feature.”PI objectives communicate planned business outcomes and allow trade-offs.
“Uncommitted objectives are failures.”They make uncertainty visible and support predictability.
“Architecture should be completed before Agile teams start.”Architecture runway evolves continuously through intentional architecture and emergent design.
“DevOps is only automation.”DevOps includes culture, Lean flow, measurement, recovery, and automation.
“Release equals deploy.”Deployment is technical movement; release is making value available to users/customers.
“Metrics are for controlling teams.”Metrics support learning, transparency, and systemic improvement.
“AI can make the decision.”AI can assist; accountable people decide using SAFe principles and evidence.
“Portfolio governance means annual project approval.”LPM uses Lean budgets, portfolio Kanban, participatory budgeting, and continuous governance.

Last-mile study checklist

  • Explain all 10 SAFe principles in scenario language.
  • Distinguish PO vs Product Management vs Business Owner vs RTE.
  • Know PI Planning inputs, outputs, risks, confidence vote, and business value assignment.
  • Practice ROAM risk handling.
  • Calculate and interpret WSJF from relative values.
  • Connect Lean Portfolio Management to strategic themes, budgets, portfolio Kanban, and epics.
  • Distinguish epics, capabilities, features, stories, and enablers.
  • Explain Continuous Exploration, Integration, Deployment, and Release on Demand.
  • Tie quality questions to built-in quality, CI, Definition of Done, and fast feedback.
  • For AI scenarios, choose augmentation, transparency, validation, and human accountability.
  • For flow scenarios, reduce WIP and bottlenecks before adding people or pushing utilization.
  • For change scenarios, use backlog transparency, trade-offs, and economic decision-making.

Practical next step

Use this Quick Reference as a recall sheet, then complete timed SA scenario practice. After each missed question, tag the miss by category: principle, role, PI Planning, LPM, flow, DevOps, artifact, or AI decision point, and review the matching table before the next set.