SA — AI-EMPOWERED SAFe Agilist (Leading SAFe) Study Plan
A practical 7-, 14-, 30-, and 60/90-day study plan for Scaled Agile AI-EMPOWERED SAFe Agilist (SA) (Leading SAFe) candidates.
This Study Plan is for candidates preparing for the Scaled Agile AI-EMPOWERED SAFe Agilist (SA) (Leading SAFe) exam, code SA. Use it to turn your remaining time into a realistic review schedule focused on SAFe concepts, Lean-Agile leadership, value delivery, ART execution, portfolio thinking, stakeholder alignment, risk, change, and scenario judgment.
Use your official Scaled Agile course materials, glossary, study guide, and any approved practice resources as the source of truth. This plan is independent study guidance and does not replace official Scaled Agile instructions.
Which Plan Should You Use?
| Time until exam | Best plan | Use this if | Main goal |
|---|---|---|---|
| 7 days | Final Review Plan | You already completed the course or most reading | Close gaps, review missed questions, rehearse timing |
| 14 days | Focused Plan | You know the basics but need structure | Build recall, practice scenarios, complete timed sets |
| 30 days | Balanced Plan | You can study most days | Learn, practice, review, and stabilize performance |
| 60/90 days | Full Preparation Path | You are starting early or studying around work | Build strong SAFe understanding before heavy mock practice |
If you are unsure, take a short diagnostic set first. Then choose based on your results:
| Diagnostic result | Recommended action |
|---|---|
| You miss basic SAFe vocabulary | Use the 30-day or 60/90-day plan |
| You know terms but miss scenarios | Use the 14-day plan with heavy explanation review |
| You perform well untimed but poorly timed | Use the 7-day plan’s mock and pacing structure |
| You are inconsistent across topics | Use the 30-day plan and maintain a strict error log |
| You are within your personal target but guessing often | Spend the final week on explanation review, not new material |
Core SA Topics to Organize Your Study
Do not study the SA exam as isolated flashcards only. The exam rewards understanding how SAFe concepts work together in enterprise delivery.
| Area | What to know | Practice focus |
|---|---|---|
| SAFe overview and business agility | Why organizations use SAFe, value streams, business agility, operating model concepts | Explain SAFe purpose in plain language |
| Lean-Agile mindset | Lean thinking, Agile values, SAFe principles, decentralized decision-making | Choose responses that improve flow, feedback, and value |
| Lean-Agile leadership | Leadership behaviors, culture, change leadership, alignment | Identify what leaders should do in a scenario |
| Team and ART execution | Agile Teams, Agile Release Trains, PI Planning, iterations, demos, Inspect and Adapt | Match roles, events, artifacts, and decisions |
| Product and value delivery | Customer centricity, design thinking, backlog flow, DevOps, release on demand | Select actions that improve customer value and delivery flow |
| Portfolio and governance | Strategy alignment, Lean budgeting ideas, portfolio flow, guardrails, prioritization | Distinguish Lean governance from traditional control-heavy governance |
| Stakeholders, risk, and change | PI risks, dependencies, feedback loops, stakeholder engagement, adaptation | Decide how to respond without disrupting flow |
| AI-empowered context | Use the AI-related content included in your official materials | Connect AI-enabled practices to SAFe roles, flow, value, and governance where covered |
Recommended Weekly Study Hours
| Plan | Minimum useful time | Better target | Best use of time |
|---|---|---|---|
| 7 days | 10-12 hours | 15-20 hours | Review, timed practice, error log |
| 14 days | 18-22 hours | 25-35 hours | Topic repair plus scenario practice |
| 30 days | 30-40 hours | 45-60 hours | Full topic cycle plus mocks |
| 60/90 days | 45-60 hours | 70+ hours | Deep learning, spaced review, multiple timed rounds |
Shorter plans should not try to relearn everything from scratch. Longer plans should not postpone practice until the end.
Daily Practice Rhythm
Use this rhythm on most study days.
| Step | Time | Action |
|---|---|---|
| 1. Recall warm-up | 5-10 min | Write or recite key SAFe terms, roles, events, and principles without notes |
| 2. Topic review | 25-45 min | Review one focused area from official Scaled Agile materials |
| 3. Scenario practice | 25-45 min | Answer questions by identifying the role, problem, constraint, and SAFe principle involved |
| 4. Explanation review | 20-40 min | Review every missed and guessed question |
| 5. Error log update | 5-10 min | Record the root cause and next action |
| 6. Micro-review | 5 min | Revisit 3-5 items from prior missed questions |
For a 60-minute day, do steps 1, 3, 4, and 5. For a 2-hour day, do all steps and add a second practice block.
7-Day Final Review Plan
Use this plan when the exam is about one week away. The goal is not to consume large amounts of new material. The goal is to stabilize performance, improve timing, and remove repeat mistakes.
| Day | Focus | Study actions | Output |
|---|---|---|---|
| 1 | Diagnostic and planning | Take a timed diagnostic block. Review all missed and guessed answers. Sort misses by topic. | Error log and top 3 weak areas |
| 2 | Lean-Agile mindset and SAFe principles | Review principles, leadership behaviors, flow, feedback, and decentralized decision-making. Practice scenario questions. | One-page principle summary |
| 3 | ART, teams, and PI Planning | Review Agile Teams, ARTs, PI Planning, dependencies, objectives, risks, demos, and Inspect and Adapt. | Role/event/artifact map |
| 4 | Product, value, portfolio, and governance | Review value delivery, customer centricity, DevOps, portfolio alignment, prioritization, and Lean governance. | Value-flow checklist |
| 5 | Timed mock or long timed set | Take a full-length timed mock if available. If not, use a long timed set under exam-like conditions. | Timing notes and reviewed misses |
| 6 | Targeted repair | Drill only your weakest areas. Re-answer previously missed questions without looking at notes first. | Reduced repeat-miss list |
| 7 | Final review and rest | Review glossary, error log, key diagrams, and exam logistics. Stop heavy new learning. | Calm, organized final checklist |
Final 48-hour rule: do not add broad new study sources. Use only official materials, your notes, and your missed-question log.
14-Day Focused Plan
Use this plan if you have two weeks and need both review and practice.
| Day | Main focus | Practice task |
|---|---|---|
| 1 | Diagnostic | Timed diagnostic set and error log setup |
| 2 | SAFe overview and business agility | Define key terms and explain the purpose of SAFe |
| 3 | Lean-Agile mindset | Practice principle-based questions |
| 4 | SAFe principles | Connect each principle to a delivery scenario |
| 5 | Lean-Agile leadership | Review leader responsibilities and change behaviors |
| 6 | Agile Teams and ARTs | Drill roles, events, artifacts, and responsibilities |
| 7 | PI Planning and execution | Practice dependency, risk, objective, and alignment scenarios |
| 8 | Product delivery and customer centricity | Review value, feedback, design thinking, and backlog flow |
| 9 | DevOps and release on demand | Practice flow, automation, release, and feedback questions |
| 10 | Portfolio and governance | Review strategy alignment, prioritization, funding, and guardrails |
| 11 | Stakeholder, risk, and change | Practice scenarios involving resistance, risk, conflict, and adaptation |
| 12 | Timed mock or long timed set | Simulate exam conditions and review explanations deeply |
| 13 | Weak-area repair | Rework missed questions and review official definitions |
| 14 | Final review | Light practice, glossary review, logistics, and rest |
Recommended split for the 14-day plan:
| Activity | Approximate share |
|---|---|
| Official content review | 35% |
| Scenario practice | 35% |
| Missed-question review | 20% |
| Timed mock practice | 10% |
30-Day Balanced Plan
Use this if you want a complete preparation cycle without cramming.
| Week | Focus | Study actions | End-of-week checkpoint |
|---|---|---|---|
| 1 | Foundation | Review SAFe overview, business agility, Lean-Agile mindset, and SAFe principles. Build flashcards or a concept map. | Can explain core terms without notes |
| 2 | Roles, events, and execution | Study Agile Teams, ARTs, PI Planning, iteration execution, demos, Inspect and Adapt, risks, and dependencies. | Can map roles to decisions |
| 3 | Value delivery and governance | Review customer centricity, product delivery, DevOps, release on demand, portfolio alignment, prioritization, and governance. | Can answer scenario questions with reasoning |
| 4 | Mocks and final repair | Take timed sets, review explanations, revisit weak topics, and stop adding new content in the final days. | Consistent performance and controlled timing |
30-Day Detailed Cadence
| Days | Focus | Required output |
|---|---|---|
| 1-3 | Diagnostic and SAFe overview | Topic gap list |
| 4-7 | Lean-Agile mindset and principles | Principle-to-scenario notes |
| 8-11 | Lean-Agile leadership and change | Leadership scenario checklist |
| 12-16 | Teams, ARTs, PI Planning, execution | Role/event/artifact table |
| 17-20 | Product delivery, DevOps, release on demand | Value-flow notes |
| 21-23 | Portfolio, governance, prioritization | Portfolio decision notes |
| 24-26 | Stakeholder, risk, change, benefits | Scenario repair set |
| 27 | Timed mock or long timed set | Mock review log |
| 28-29 | Weak-area repair | Repeat-miss list cleared |
| 30 | Final review | Exam-day checklist |
60/90-Day Full Preparation Path
Use this path if you are starting early, balancing work, or new to SAFe.
| Phase | 60-day version | 90-day version | Goal |
|---|---|---|---|
| 1. Orientation | Days 1-7 | Days 1-14 | Understand exam scope, collect materials, take diagnostic |
| 2. Foundation | Days 8-20 | Days 15-35 | Build SAFe vocabulary, mindset, and principles |
| 3. Delivery system | Days 21-35 | Days 36-55 | Study teams, ARTs, PI Planning, execution, product delivery |
| 4. Governance and change | Days 36-45 | Days 56-70 | Study portfolio, leadership, stakeholders, risk, change, value |
| 5. Scenario practice | Days 46-53 | Days 71-80 | Increase question volume and explanation review |
| 6. Timed readiness | Days 54-58 | Days 81-86 | Complete timed mocks or long timed sets |
| 7. Final review | Days 59-60 | Days 87-90 | Review error log, official definitions, and exam logistics |
Weekly Structure for 60/90 Days
| Day type | Activity |
|---|---|
| 2 days per week | Official content review |
| 2 days per week | Scenario practice |
| 1 day per week | Missed-question review |
| 1 day per week | Mixed timed set |
| 1 day per week | Rest or light glossary review |
Starting early is useful only if you revisit old misses. Schedule spaced review every week so Week 1 topics do not fade by exam week.
Agile, Predictive, and Hybrid Scenario Judgment
Many SA candidates come from project management, program management, product, or delivery roles. For the SA exam, practice answering from a SAFe Lean-Agile perspective, not from generic project control habits.
| Scenario pattern | SAFe-oriented response | Common trap |
|---|---|---|
| Teams need alignment | Use ART-level cadence, PI Planning, objectives, demos, and feedback loops | Add more status reporting without improving alignment |
| Requirements change | Use backlog refinement, prioritization, feedback, and economic decision-making | Freeze scope too early |
| Stakeholders disagree | Improve transparency, shared objectives, and decision clarity | Escalate every conflict as a command decision |
| Delivery is slow | Look for flow, bottlenecks, batch size, dependencies, and DevOps improvements | Push teams harder without fixing the system |
| Risk appears during planning | Make risk visible, clarify ownership, and address it in planning | Hide risk until after commitment |
| Governance is needed | Use Lean governance, guardrails, strategy alignment, and objective measures | Treat governance as phase-gate control only |
| Benefits are unclear | Tie work to value, outcomes, customer feedback, and business objectives | Measure only activity or output volume |
Missed-Question Review Method
Do not only mark answers right or wrong. Classify every miss so you know what to fix.
| Miss type | What it means | Repair action |
|---|---|---|
| Term gap | You did not know a SAFe term | Review glossary and write your own definition |
| Role confusion | You mixed up responsibilities | Create a role-decision table |
| Event confusion | You confused PI Planning, iteration events, demos, or Inspect and Adapt | Draw the cadence and event flow |
| Principle gap | You knew the words but not the application | Write the principle and one example scenario |
| Scenario misread | You missed a clue in the wording | Underline role, problem, constraint, and desired outcome |
| Predictive bias | You answered like a traditional project controller | Reframe using Lean-Agile leadership and flow |
| Governance confusion | You missed portfolio, funding, prioritization, or guardrail logic | Review how strategy connects to execution |
| Timing error | You rushed or overanalyzed | Practice timed sets and set a per-question decision rhythm |
| Lucky correct | You guessed correctly | Review as if it were wrong |
Error Log Template
Use a simple table.
| Date | Question/topic | Miss type | Correct idea | Why I missed it | Next review date |
|---|---|---|---|---|---|
| Example | PI risk scenario | Scenario misread | Make risk visible and address ownership | Focused on the wrong role | Tomorrow |
Re-answer missed questions after 24-48 hours. If you still miss them, move the topic into your next focused review block.
What to Practice Next
Use this table after every practice session.
| If your review shows… | Practice next |
|---|---|
| Weak vocabulary | Glossary drill plus 10-15 basic concept questions |
| Weak principles | Principle scenarios and explanation review |
| Weak roles/events | Build a role-event-artifact map, then drill mixed questions |
| Weak PI Planning logic | Practice objectives, dependencies, risks, alignment, and commitment scenarios |
| Weak portfolio/governance | Review value, strategy, funding, prioritization, and guardrails |
| Weak stakeholder/risk/change scenarios | Practice situational questions with role and outcome identification |
| Weak timing | Use shorter timed blocks before another long mock |
| Many careless mistakes | Slow down, annotate the question stem, and reduce question volume temporarily |
| Same misses repeating | Stop new practice and repair the underlying topic |
Timed Mock Exam Strategy
Use timed practice only after you have enough content foundation to learn from the results.
| Preparation stage | Timed practice recommendation |
|---|---|
| Early study | Short timed sets only; focus on explanations |
| Mid-study | Mixed timed blocks by topic and scenario type |
| Final 2 weeks | At least one full-length mock if available, or long timed sets |
| Final week | One major timed attempt early in the week, then targeted repair |
| Final 24 hours | No heavy mock unless you need a confidence check and can review calmly |
When taking a mock:
- Use the time limit shown in your exam instructions or practice tool.
- Do not pause for notes.
- Mark uncertain questions.
- Review wrong answers, guessed correct answers, and slow questions.
- Convert every miss into an error-log entry.
- Revisit the same topic within 48 hours.
Do not judge readiness from one score alone. Look for consistency, timing control, and fewer repeat misses.
Final-Week Rules
| Rule | Why it matters |
|---|---|
| Stop adding broad new resources in the final 48 hours | New sources can create confusion and reduce recall |
| Review official terminology daily | SA exams often depend on precise language |
| Rework missed questions before doing new ones | Repeat mistakes are more valuable than fresh volume |
| Practice mixed scenarios | The real exam is not organized like your notes |
| Keep answers SAFe-centered | Choose Lean-Agile, value-focused, flow-based responses |
| Protect sleep before exam day | Tired candidates misread scenario questions |
| Confirm exam logistics early | Avoid preventable stress on test day |
Exam-Readiness Checks
You are closer to ready when you can say yes to most of these:
| Readiness question | Yes/No |
|---|---|
| Can I explain SAFe, business agility, and Lean-Agile leadership without reading notes? | |
| Can I connect SAFe principles to realistic delivery scenarios? | |
| Can I distinguish team, ART, portfolio, and leadership responsibilities? | |
| Can I reason through PI Planning, risks, dependencies, demos, and Inspect and Adapt? | |
| Can I answer stakeholder, risk, change, and governance questions from a SAFe perspective? | |
| Can I complete timed practice without rushing at the end? | |
| Have I reviewed all missed and guessed questions? | |
| Are repeat misses decreasing? | |
| Do I know the exam-day instructions and logistics from Scaled Agile? |
If several answers are no, delay new question volume and spend one or two sessions repairing the weakest areas.
Practical Next Step
Choose the plan that matches your exam date, take a diagnostic timed set, and build your error log today. Then study in short cycles: review one SAFe topic, answer scenario questions, analyze every miss, and repeat until your timing and explanations are stable.