Overview
Build a Foundation with Mindset, Value, and Principles carries 21-23% of the AI-Empowered SA exam. It covers the Lean-Agile mindset (thinking Lean, as summarized in the SAFe House of Lean, plus embracing agility through the Agile Manifesto), the four SAFe Core Values of alignment, transparency, respect for people and relentless improvement, and the ten SAFe Lean-Agile Principles. The new third topic, Empower Agility with AI, asks how AI can speed up learning and remove toil while people keep responsibility for judgment and outcomes.
This is the reasoning layer of SAFe. Every practice in later domains, from WSJF in Product Development Flow to Lean budgets in Lean Portfolio Management, is an application of a principle taught here. The exam expects you to match a scenario to the principle it illustrates, and to pick the action a Lean-Agile leader would take.
How it's tested
Expect principle-matching and BEST-action scenarios. A stem describes a leader's decision or a team's behavior and asks which principle applies, which Core Value is at stake, or what a Lean-Agile leader should do. AI items present a use of AI and ask which approach keeps humans accountable and manages risk. The right answer usually favors flow, fast feedback, decentralization and respect for people.
-
Name the principle
A scenario describes a practice, such as carrying several design options forward, and you identify the Lean-Agile Principle it applies.
-
Centralize or decentralize
You decide whether a decision should be made centrally (infrequent, long-lasting, economies of scale) or by the people closest to the work (frequent, time-critical, needing local information).
-
Responsible AI use
A team wants to use AI for a task. You choose the option that gets the benefit while keeping human oversight and protecting data.
A leader insists every team stay 100% utilized so no capacity is wasted, yet lead times keep growing. The options include adding staff, tighter status reporting, and limiting work in process. The clue is high utilization alongside long waits: queues grow sharply as utilization approaches full, so Principle #6, make value flow without interruptions, points to limiting WIP and reducing queue length. Adding staff ignores the cause.
Topics 3
Official topics from the Scaled Agile outline, in outline order.
2.1 Understand the Lean-Agile Mindset and SAFe Core ValuesThinking Lean, embracing agility, and the four Core Values.
- What it means
- The Lean-Agile mindset combines thinking Lean, captured in the House of Lean with value as the goal, pillars of respect for people, flow, innovation and relentless improvement, and leadership as the foundation, with the values and principles of the Agile Manifesto. The SAFe Core Values are alignment, transparency, respect for people and relentless improvement.
- What to understand
- The mindset is a set of beliefs that drives behavior, and the Core Values are how you judge whether behavior fits. Transparency, for example, requires making problems visible early, and respect for people extends to customers and suppliers, not only employees.
- How it shows up
- A stem describes a behavior, such as hiding a slipped deadline or bypassing a supplier's input, and asks which Core Value is violated or what the leader should do instead.
- Common confusion
- Older SAFe versions listed built-in quality and program execution as core values. SAFe 6.0 and later list alignment, transparency, respect for people and relentless improvement.
2.2 Apply the SAFe Lean-Agile PrinciplesThe ten principles and the decisions each one drives.
- What it means
- The ten principles are: take an economic view; apply systems thinking; assume variability, preserve options; build incrementally with fast, integrated learning cycles; base milestones on objective evaluation of working systems; make value flow without interruptions; apply cadence, synchronize with cross-domain planning; unlock the intrinsic motivation of knowledge workers; decentralize decision-making; organize around value.
- What to understand
- Each principle replaces a traditional habit. Objective evaluation of working systems replaces document-based phase gates, set-based design replaces committing early to one point solution, and decentralization keeps only strategic, infrequent, long-lasting decisions central.
- How it shows up
- A practice is described and you must name the principle, or a principle is named and you must pick the practice that applies it.
- Common confusion
- Principles #3 and #4 are mixed up: #3 keeps multiple design options open under uncertainty, while #4 integrates frequently to learn fast from a working system.
2.3 Empower Agility with AIUsing AI to amplify Lean-Agile ways of working, responsibly.
- What it means
- SAFe describes AI-empowered agility as shifting human effort from execution toward intent and strategy, accelerating learning and experimentation cycles, unlocking innovation at scale and augmenting teams with AI capabilities, inside a human-centric culture where people remain the final check on value, safety and purpose.
- What to understand
- AI speeds up work such as summarizing feedback, drafting stories or analyzing data, but outputs can be biased or hallucinated, and pasting confidential data into external tools risks leaks. SAFe's Responsible AI guidance aims for AI that is trustworthy, explainable and human-centric.
- How it shows up
- A team proposes letting an AI tool make or publish decisions on its own, or feeding it sensitive data. The best answer keeps a human accountable, validates outputs and follows the organization's AI policies.
- Common confusion
- Treating AI as a replacement for team judgment or for Lean-Agile practices. In SAFe, AI amplifies the mindset and principles; it does not substitute for them.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
SAFe House of Lean
The House of Lean has value as its roof, four pillars (respect for people, flow, innovation, relentless improvement) and leadership as its foundation.
- Remember
- Leadership is the foundation, which is why SAFe puts leaders, not teams, first in the transformation.
- Tested as
- Questions ask which pillar a behavior supports or what the goal of Lean thinking is.
- Trap
- Naming speed or cost reduction as the goal instead of delivering value in the shortest sustainable lead time.
-
SAFe Core Values
Alignment, transparency, respect for people and relentless improvement are the four values that guide behavior across the enterprise.
- Remember
- These are the SAFe 6.0 and later values; built-in quality is now a practice area, not a Core Value.
- Tested as
- Scenarios describe a behavior and ask which value it supports or violates.
- Trap
- Selecting built-in quality or program execution from an outdated list.
-
Principle #1: Take an economic view
Decisions should weigh lead time, cost, value and risk together, delivering value early and incrementally within an economic framework.
- Remember
- Cost of Delay and WSJF are the main tools that put this principle into practice.
- Tested as
- Stems about trade-offs or sequencing work by value point here.
- Trap
- Choosing the cheapest option when the scenario stresses the cost of delaying delivery.
-
Principle #3: Assume variability; preserve options
Under uncertainty, carry several design options forward (set-based design) and narrow them as evidence arrives, instead of choosing one design up front.
- Remember
- Keeping options open is deliberate risk management, not indecision.
- Tested as
- A team evaluating two architectures in parallel until testing settles it illustrates this principle.
- Trap
- Confusing it with Principle #4, which is about frequent integration.
-
Principle #5: Objective milestones
Milestones should be based on objective evaluation of working systems, such as a system demo, rather than on documents completed at phase gates.
- Remember
- Phase-gate approvals of requirements or design documents create false confidence because nothing has been proven.
- Tested as
- Questions on how to measure progress expect the working-system answer.
- Trap
- Accepting a signed-off design document as evidence of progress.
-
Principle #6: Make value flow without interruptions
Flow improves when you visualize and limit work in process, reduce batch size, manage queue lengths and remove bottlenecks and hand-offs.
- Remember
- Little's Law: average wait time equals average queue length divided by average processing rate, so shorter queues mean faster delivery.
- Tested as
- Scenarios with long lead times and busy teams expect a WIP or batch-size answer.
- Trap
- Maximizing utilization, which makes queues and wait times grow.
-
Principle #7: Cadence and synchronization
Cadence makes routine events predictable, and synchronization brings multiple perspectives together at the same time, as in PI Planning.
- Remember
- Cadence lowers transaction costs; synchronization enables cross-domain integration and planning.
- Tested as
- Asked why all ART teams share the same iteration and PI boundaries.
- Trap
- Thinking cadence means releasing only at fixed dates; SAFe develops on cadence but can release on demand.
-
Principle #9: Decentralize decision-making
Centralize decisions that are infrequent, long-lasting and have significant economies of scale; decentralize decisions that are frequent, time-critical and need local information.
- Remember
- Strategic platform choices stay central; day-to-day technical and scope choices go to teams.
- Tested as
- A common question asks which of four decisions should be centralized.
- Trap
- Decentralizing everything because it sounds more Agile.
-
Principle #8: Intrinsic motivation
Knowledge workers are motivated by autonomy, mastery and purpose, and individual incentive pay can undermine collaboration.
- Remember
- Leaders provide purpose and minimize constraints instead of directing every task.
- Tested as
- Stems about incentive schemes or micromanagement point here.
- Trap
- Choosing individual performance bonuses to raise team output.
-
AI-empowered agility
SAFe frames AI as shifting effort from execution to intent and strategy, speeding learning cycles, enabling innovation at scale and augmenting teams.
- Remember
- A human-centric AI culture keeps people as the final check on value, safety and purpose.
- Tested as
- AI questions reward options that combine AI speed with human accountability.
- Trap
- Letting AI decide or publish without review because it is faster.
-
Responsible AI
SAFe describes Responsible AI as AI that is trustworthy (private, secure, reliable, accurate), explainable (transparent, interpretable, accountable) and human-centric (safe, fair, ethical, compliant).
- Remember
- Key risks are bias, hallucination and leaking confidential data into external tools.
- Tested as
- Scenarios involving customer data or automated decisions test these risks.
- Trap
- Assuming an AI output is correct because it is fluent and detailed.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Principle #3 vs. Principle #4 vs. Principle #5
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| #3 Assume variability; preserve options | Keep several design options open until evidence narrows them | About choosing designs under uncertainty | Calling it indecision or waste |
| #4 Build incrementally with fast, integrated learning cycles | Integrate often so each cycle produces learning from a working system | About short PDCA cycles and integration points | Mistaking it for keeping options open |
| #5 Objective milestones | Measure progress by evaluating working systems | About how progress is judged, replacing phase gates | Treating document sign-off as a milestone |
Centralized vs. decentralized decisions
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Centralize | Decisions that are infrequent, long-lasting and have significant economies of scale | Example: choosing an enterprise-wide cloud platform | Pushing strategic, hard-to-reverse choices to individual teams |
| Decentralize | Decisions that are frequent, time-critical and need local information | Example: how a team implements a story | Escalating routine choices and creating delay |
AI assisting vs. AI deciding
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| AI assists | AI drafts, summarizes or analyzes and a person reviews and decides | Human remains accountable; output is validated | Skipping the review because output looks plausible |
| AI decides unchecked | AI output is acted on or published without human review | Risks bias, hallucination and policy breaches going unnoticed | Choosing it because it is the fastest option |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Full utilization
- What candidates pick
- Keep every team member fully loaded so no capacity is idle.
- Why it looks right
- Idle capacity looks like waste in a cost-focused organization.
- Why it's wrong
- As utilization approaches 100%, queues and wait times grow sharply, which slows flow. Principle #6 favors limiting WIP and keeping slack.
Clue to watch for The stem pairs busy teams with long or growing lead times.
-
Phase-gate milestones
- What candidates pick
- Approve the next phase once the requirements and design documents are signed off.
- Why it looks right
- Sign-offs look like disciplined governance.
- Why it's wrong
- Principle #5 bases milestones on objective evaluation of working systems. Documents do not prove the solution works.
Clue to watch for The question asks how to measure progress or reduce risk.
-
Pick one design early
- What candidates pick
- Commit to the most promising architecture at the start to avoid rework.
- Why it looks right
- It feels efficient and decisive.
- Why it's wrong
- Under high uncertainty, Principle #3 keeps multiple options open until evidence from testing shows which works.
Clue to watch for The stem stresses uncertainty about technology or requirements.
-
Decentralize everything
- What candidates pick
- Let each team choose its own enterprise database platform.
- Why it looks right
- Decentralized decision-making is a SAFe principle.
- Why it's wrong
- Infrequent, long-lasting decisions with economies of scale should be centralized under Principle #9.
Clue to watch for The decision is enterprise-wide, costly to reverse, or benefits from standardization.
-
Incentive pay for speed
- What candidates pick
- Introduce individual bonuses tied to story points completed.
- Why it looks right
- Incentives seem to raise output.
- Why it's wrong
- Principle #8 relies on autonomy, mastery and purpose; individual incentives can undermine collaboration and distort estimates.
Clue to watch for A proposal rewards individuals for team-level outcomes.
-
Unchecked AI
- What candidates pick
- Let an AI tool publish customer-facing release notes automatically from commit history.
- Why it looks right
- It removes toil and is clearly faster.
- Why it's wrong
- SAFe's human-centric approach keeps people as the final check; unreviewed output can contain hallucinations or expose confidential details.
Clue to watch for Output reaches customers or decisions without a person reviewing it.
Answer framework
For a Domain 2 scenario, test each option against the mindset and principles in this order.
- Identify the underlying decision: sequencing work, measuring progress, choosing a design, assigning authority, motivating people or using AI.
- Map the decision to the Lean-Agile Principle that governs it, for example economics, variability, milestones, flow or decentralization.
- Check each option against the four Core Values and eliminate any that hide information, disrespect people or block improvement.
- Prefer options that reduce WIP and batch size, shorten feedback loops, and push frequent, time-critical decisions to the people doing the work.
- For AI scenarios, choose the option that uses AI to speed learning while keeping a named human accountable, validating outputs and protecting confidential data.
Practice question
Want more like this? The SAFe Agilist practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Begin with the mindset and Core Values, because they are short and give you the vocabulary for the principles. Then spend most of your time on the ten principles. For each one, write a one-line traditional habit it replaces and one practice from later lessons that applies it: WSJF for #1, set-based design for #3, PDCA and integration points for #4, system demos for #5, WIP limits for #6, PI Planning for #7, and ARTs for #10.
High-priority concepts are Principle #6 with Little's Law, Principle #9 with the centralize-or-decentralize test, and Principle #5 against phase gates, because they generate clear right-or-wrong scenarios. Commonly underestimated areas are the exact current Core Values, which differ from older SAFe material, and the difference between Principles #3 and #4.
For Empower Agility with AI, read the SAFe framework articles on AI-empowered agility and Responsible AI, and practice judging AI use cases: who reviews the output, what data goes in, and which risk is present. Afterwards, practice mixed question sets and, for each miss, name the principle the correct answer applied. That habit transfers directly to Product Development Flow and Lean Portfolio Management questions.
FAQ
How much of the SAFe Agilist exam is this domain?
Scaled Agile weights it at 21-23% of the 45-question AI-Empowered SA exam. As an editorial estimate, that is about nine or ten questions.
Do I need to memorize all ten Lean-Agile Principles?
Yes, and in a form you can apply. Most questions describe a practice or decision and expect you to recognize which principle drives it, so a list alone is not enough.
What are the current SAFe Core Values?
Alignment, transparency, respect for people and relentless improvement. Older SAFe versions listed built-in quality and program execution, which you should not select on this exam.
Which decisions should be centralized in SAFe?
Decisions that are infrequent, long-lasting and have significant economies of scale, such as enterprise platforms. Frequent, time-critical decisions that need local information go to the teams.
How deep is the AI content in this domain?
The study guide lists Empower Agility with AI as one of three topics, without further detail. Expect conceptual questions on using AI to speed learning while keeping humans accountable and managing risks such as bias, hallucination and data leaks.
How does this domain relate to Product Development Flow?
Product Development Flow applies these principles: WSJF puts the economic view into practice, PI Planning applies cadence and synchronization, and system demos apply objective milestones.
How long should I study this domain?
As a planning estimate, seven to ten hours, weighted toward applying the principles to scenarios rather than rereading definitions.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 2 knowledge
You have covered the Lean-Agile mindset, the Core Values, all ten principles and responsible AI use. Practice matching scenarios to principles under timed conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the SAFe Agilist AI tutor Get any concept explained your way