STSC overview

  • 200 practice questions
  • 33 flashcards
  • 7 study guide topics
  • 40 key terms

What you'll study

  • Thriving in the Digital Age with Business Agility10%
  • Becoming a SAFe Scrum Master10%
  • Establishing Team Agility20%
  • Building High-Performing Teams15%
  • Planning and Executing Work in a SAFe Enterprise20%
  • Leading in a SAFe Enterprise15%
  • Practicing SAFe10%

The SAFe 6 Scrum Master (SSM) credential is aimed at Scrum Masters, team coaches, and delivery leads who work inside a Scaled Agile Framework enterprise rather than a standalone Scrum team. It signals that you can run team-level events, coach Agile behaviours, and connect team execution to the wider planning cadence. The exam samples seven areas: the case for business agility in a digital age, the evolving Scrum Master role, establishing team agility, building high-performing teams, planning and executing work across the enterprise, leading within a SAFe organisation, and applied practice scenarios. Expect a multiple-choice exam, some items with more than one correct answer, and a strong emphasis on situational judgement - how you would act during PI Planning, Iteration execution, or a team conflict - rather than recall of definitions alone. Preparation works best in layers: read the official SAFe Scrum Master material once for vocabulary, then re-read the team and planning chapters while mapping each concept to something you have actually done. Practise explaining why a practice exists, not just naming it. The official certifying body publishes the current question count, time limit, fee, passing score, and retake rules on its own website; confirm those details there before you book, as they change. This page is independent study material and is not affiliated with or endorsed by Scaled Agile, Inc.

Common mistakes

Treating SAFe as a fixed, prescriptive process and answering that teams must adopt every artifact and ceremony exactly as written, rather than selecting the minimal set that delivers the outcome.

Candidates memorize the framework diagram (PI Planning, System Demo, Inspect & Adapt, etc.) and assume completeness equals correctness, so they pick the most ceremony-heavy option.

What to do instead

For each question, ask which practice the scenario actually requires and whether the option respects SAFe's principle of applying cadence and synchronization with the smallest viable set of practices. Prefer options that tailor rather than duplicate or bloat.

Confusing the Scrum Master's servant-leader and coaching stance with a command-and-control stance, choosing answers where the SM assigns tasks, sets estimates, or directs the team's technical decisions.

Candidates import habits from traditional project management or from team-lead roles and read 'accountable for team outcomes' as 'decides for the team'.

What to do instead

Screen every SM option for who holds the decision: if the SM makes a technical or estimation decision for the team, reject it. Correct options show the SM facilitating, teaching, removing impediments, and protecting the team's self-management.

Conflating the three Scrum roles and their accountabilities, for example saying the Product Owner runs the Daily Stand-up, the Scrum Master owns the backlog, or the team reports to the SM.

Role names sound interchangeable and candidates remember 'who attends' rather than 'who is accountable for what'.

What to do instead

Build a one-page accountability matrix: PO owns value and backlog ordering, SM owns process effectiveness and impediment removal, Developers own delivery and estimation. Answer by matching the accountability in the stem to the role that owns it.

Choosing 'the team should self-organize' as a complete answer without naming the concrete mechanism (facilitation, working agreements, retrospective action, or escalation path) that makes self-organization happen.

Self-organization is the memorable buzzword, so candidates stop reading once they see it and ignore that the option offers no actionable step.

What to do instead

Require every answer to contain a verb and an artifact: who does what, using which event or agreement. Reject options that only restate a value without a mechanism.

Treating team formation as a single event and skipping the storming and norming stages, so answers assume a new team will immediately share norms, estimate reliably, and self-manage.

Candidates focus on the Tuckman model as vocabulary rather than as a planning constraint, and underestimate how long shared working agreements take.

What to do instead

When a stem describes a new or reshuffled team, look for answers that establish working agreements, define done, and use retrospectives to surface conflict early, not answers that assume instant high performance.

Misreading PI Planning mechanics: mixing up who owns the draft plan, when business owners assign value, what a risk ROAM board is for, and what happens when dependencies cannot be resolved.

PI Planning has many interlocking steps and candidates learn the agenda order without learning the purpose of each block, so adjacent terms blur.

What to do instead

Learn PI Planning as a sequence of purposes: vision and context, team breakouts producing draft plans and objectives, management review, problem-solving for unresolved dependencies, and commitment by business owners. Map each term to its purpose, then answer by purpose.

Confusing team PI objectives with team backlog items or with the Program Board, and treating uncommitted objectives as failures rather than as planned stretch capacity.

Objectives, stories, and board items all look like 'work', and the committed/uncommitted distinction is easy to flatten into pass/fail thinking.

What to do instead

Anchor the definitions: PI objectives are business-facing summaries of planned value, some committed and some uncommitted by design; the Program Board visualizes features and cross-team dependencies. Reject options that treat uncommitted objectives as broken commitments.

Answering leadership questions with generic 'communicate more' or 'empower the team' responses instead of naming the Lean-Agile leadership behaviour and the artifact that demonstrates it.

Leadership items feel abstract, so candidates default to soft-skill platitudes that sound safe but do not match the specific behaviour SAFe describes.

What to do instead

Prepare concrete leader behaviours: leading by example, adopting a growth mindset, teaching the why, creating the environment, and aligning strategy with execution. Choose the option that names a behaviour plus a visible action such as participating in PI Planning or reviewing metrics with teams.

Treating SAFe metrics as individual performance measures, for example using velocity or predictability to rank people or teams, or reading a single metric as a verdict.

Candidates carry over traditional performance-management instincts and forget that SAFe metrics are intended for improvement, not judgement.

What to do instead

Prefer answers that use flow and outcome measures (flow time, flow load, predictability, competency) to inform Inspect & Adapt and retrospective action, and reject any option that uses metrics to compare or reward individuals.

Skipping the continuous-improvement loop: answering that a problem should be escalated or accepted without a retrospective, Inspect & Adapt, or problem-solving workshop to address the root cause.

Candidates treat events as separate boxes and do not connect a surfaced problem to the improvement mechanism that SAFe provides.

What to do instead

For any stem describing a recurring problem, look for the answer that routes it into the appropriate improvement loop (team retrospective for team process, Inspect & Adapt for ART-level systemic issues) and includes a measurable follow-up action.

Exam requirements can change. Confirm current details with the exam provider.

STSC practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Thriving in the Digital Age with Business Agility

    In the Scrum@Scale framework, which component is responsible for coordinating multiple Scrum Teams to eliminate cross-team dependencies and align on a shared product backlog?

    1. The Meta-Scrum
    2. The Product Owner Cycle
    3. The Executive Action Team (EAT)
    4. The Scrum of Scrums (SoS) Correct answer.

    Explanation

    The Scrum of Scrums is the scaling mechanism that lets representatives from several teams synchronize work, surface and remove impediments that cross team boundaries, and coordinate delivery. It sits inside the delivery cycle and complements, rather than replaces, the Product Owner cycle's backlog alignment.

  2. Question 2Thriving in the Digital Age with Business Agility

    A product team wants to test a new pricing model quickly. Which approach best reflects a business agility mindset in the digital age?

    1. Run a small, time-boxed experiment with a subset of customers and measure outcomes Correct answer.
    2. Delegate the decision to a central architecture review board
    3. Wait for the annual budget cycle to approve the pricing change
    4. Complete a full requirements specification before any customer contact

    Explanation

    Business agility favors fast, low-cost experiments that generate real customer data so decisions are evidence-based. Small, time-boxed tests limit risk while producing learning that informs the next step.

  3. Question 3Thriving in the Digital Age with Business Agility

    Which statement best describes the purpose of a Minimum Viable Product (MVP) in an agile digital product effort?

    1. To deliver the smallest increment that lets the team validate a hypothesis with real users Correct answer.
    2. To ship a feature-complete release with the lowest possible development cost
    3. To reduce scope permanently by removing all non-core features
    4. To document the full product vision before development begins

    Explanation

    An MVP is a learning instrument: it is the smallest thing the team can build to test a key assumption with actual users. Its value lies in validated learning, not in being a cheap or incomplete final product.

  4. Question 4Thriving in the Digital Age with Business Agility

    In the Stacey matrix, which condition calls for an empirical, inspect-and-adapt approach rather than a predictive plan?

    1. Stable requirements with a proven technology
    2. Low uncertainty in requirements and technology
    3. High uncertainty in both requirements and technology Correct answer.
    4. A well-understood process with predictable variation

    Explanation

    The Stacey matrix places complex and chaotic work, where requirements and technology are both uncertain, in the region that requires empirical control. Predictive planning works when both dimensions are well understood and stable.

  5. Question 5Thriving in the Digital Age with Business Agility

    Which practice most directly supports continuous delivery in a DevOps-enabled agile organization?

    1. Separating development and operations into distinct silos
    2. Maintaining an automated deployment pipeline with automated tests Correct answer.
    3. Batching releases into quarterly release trains
    4. Requiring manual sign-off for every production deployment

    Explanation

    Continuous delivery depends on an automated pipeline that builds, tests, and deploys reliably, giving fast feedback and repeatable releases. Automation removes the bottlenecks that manual gates and large batches introduce.

  6. Question 6Thriving in the Digital Age with Business Agility

    Which metric best reflects the outcome focus of business agility rather than output volume?

    1. Customer retention rate after a new feature launch Correct answer.
    2. Count of meetings held per week
    3. Lines of code committed per developer
    4. Number of story points completed per sprint

    Explanation

    Business agility measures whether customers and the organization achieve better outcomes, such as retention or satisfaction. Output metrics like story points or lines of code describe activity, not value delivered.

  7. Question 7Thriving in the Digital Age with Business Agility

    An organization adopting business agility wants to move decision authority closer to the work. Which structural change best supports this?

    1. Adding an additional approval layer above each team
    2. Empowering cross-functional teams with clear guardrails and delegated decision rights Correct answer.
    3. Requiring every team decision to be ratified by a steering committee
    4. Centralizing all product decisions in a program management office

    Explanation

    Business agility relies on decentralized decision-making within explicit boundaries so teams can respond quickly to customers. Clear guardrails preserve alignment while delegating authority to those closest to the information.

  8. Question 8Thriving in the Digital Age with Business Agility

    In Design Thinking applied to agile delivery, what is the primary role of rapid prototyping?

    1. To freeze requirements for the development phase
    2. To make assumptions tangible so they can be tested with users early Correct answer.
    3. To replace user research with internal opinions
    4. To finalize the production architecture before coding

    Explanation

    Prototypes externalize hypotheses so teams can gather user feedback before investing in full builds. This shortens the learning loop and reduces the risk of building the wrong thing.

  9. Question 9Thriving in the Digital Age with Business Agility

    A team's flow shows a growing queue of finished work waiting for testing. Which Kanban practice most directly addresses this?

    1. Removing the testing stage to shorten the board
    2. Increasing batch size to reduce the number of releases
    3. Adding more work items to keep developers busy
    4. Setting explicit work-in-progress limits and making policies visible Correct answer.

    Explanation

    Work-in-progress limits constrain the amount of concurrent work so bottlenecks surface and flow improves, and explicit policies make the process transparent. The queue signals that the system is constrained at testing, which WIP limits help expose and manage.

  10. Question 10Thriving in the Digital Age with Business Agility

    Which statement correctly distinguishes a Lean Startup build-measure-learn loop from traditional stage-gate development?

    1. It requires a complete business case before any experiment starts
    2. It advances only when predefined deliverables are signed off
    3. It treats validated learning from real customers as the primary unit of progress Correct answer.
    4. It measures progress by the percentage of planned features delivered

    Explanation

    The build-measure-learn loop uses experiments to convert assumptions into validated learning, and progress is judged by what has been learned about customers. Stage-gate development instead advances through predetermined deliverables and approvals.

  11. Question 11Thriving in the Digital Age with Business Agility

    In a large agile organization, what is the main purpose of a quarterly planning cadence such as PI planning?

    1. To lock the scope so no changes occur during the quarter
    2. To align multiple teams on shared objectives and surface cross-team dependencies Correct answer.
    3. To assign individual tasks to each developer for the quarter
    4. To replace the team's daily coordination and sprint planning

    Explanation

    Quarterly or program-increment planning aligns teams around shared objectives and exposes dependencies that need coordination. It complements, rather than replaces, team-level planning events.

  12. Question 12Thriving in the Digital Age with Business Agility

    Which is the strongest example of a leading indicator of business agility health?

    1. Total number of completed projects
    2. Cycle time from idea to customer feedback Correct answer.
    3. Last quarter's revenue total
    4. Annual employee headcount

    Explanation

    Leading indicators predict future outcomes and are actionable in the short term; cycle time reveals how quickly the organization learns and adapts. Lagging outcomes like revenue or headcount describe past results without guiding near-term decisions.

  13. Question 13Thriving in the Digital Age with Business Agility

    A team wants to reduce the risk of a large integration. Which practice aligns with continuous integration in a DevOps culture?

    1. Running integration tests only before the final release
    2. Merging small changes to a shared trunk frequently with automated build verification Correct answer.
    3. Keeping long-lived feature branches until release
    4. Assigning one integration specialist to merge all code at the end

    Explanation

    Continuous integration means integrating small changes frequently into a shared mainline, with automated builds and tests catching problems early. This keeps integration cost low and feedback fast.

  14. Question 14Thriving in the Digital Age with Business Agility

    Which describes the relationship between an Agile Release Train and its teams in a scaled agile setting?

    1. The train is a temporary committee that meets only at release time
    2. Teams report to the train only for budget approval
    3. The train delivers a continuous flow of value through teams that plan and integrate together Correct answer.
    4. Each team operates with no shared objectives or synchronization

    Explanation

    An Agile Release Train is a long-lived team of teams that plans together and integrates its work into a continuous flow of value. Shared objectives and synchronization distinguish it from independent teams or a temporary committee.

  15. Question 15Thriving in the Digital Age with Business Agility

    A product owner wants to prioritize a backlog using cost of delay. Which approach best applies this concept?

    1. Rank items by the economic value lost per unit of time they are delayed Correct answer.
    2. Prioritize items with the most detailed documentation
    3. Order items by the size of the estimate regardless of value
    4. Sequence work by the order in which requests arrived

    Explanation

    Cost of delay expresses how much value is forgone for each unit of time an item waits, enabling prioritization by economic impact. Combining it with duration yields weighted shortest job first sequencing.

  16. Question 16Thriving in the Digital Age with Business Agility

    Which practice best embodies the agile principle of welcoming changing requirements late in development?

    1. Freezing the scope at project initiation to protect the plan
    2. Maintaining a refined, ordered backlog that can absorb new insights each iteration Correct answer.
    3. Requiring change requests to pass a change control board
    4. Estimating all requirements in detail before the first sprint

    Explanation

    An ordered, continuously refined backlog lets teams incorporate new learning and reprioritize without derailing delivery. This harnesses change for competitive advantage, consistent with the agile principle.

  17. Question 17Thriving in the Digital Age with Business Agility

    An enterprise wants to fund agile teams in a way that supports continuous flow. Which funding model is most consistent with business agility?

    1. Funding allocated strictly by department headcount
    2. One-time capital funding with no review until project closure
    3. Incremental, value-based funding of persistent teams reviewed against outcomes Correct answer.
    4. Annual project funding tied to fixed scope and deliverables

    Explanation

    Lean, value-based funding of persistent teams lets investment follow demonstrated outcomes and supports continuous flow. Fixed-scope annual project funding reinforces batch thinking and inhibits reprioritization.

  18. Question 18Thriving in the Digital Age with Business Agility

    A leader in a digital transformation wants to foster intrinsic motivation. Which action is most aligned with that goal?

    1. Giving teams autonomy over how they work while connecting them to a clear purpose Correct answer.
    2. Increasing extrinsic bonuses tied to individual output metrics
    3. Standardizing every team practice to remove variation
    4. Adding closer supervision to ensure adherence to process

    Explanation

    Intrinsic motivation grows when people have autonomy, mastery, and purpose; leaders support it by granting autonomy around a compelling purpose. Extrinsic output bonuses and tighter supervision tend to undermine it.

  19. Question 19Thriving in the Digital Age with Business Agility

    Which situation best demonstrates the agile value of responding to change over following a plan?

    1. A team escalates any deviation from the baseline plan for approval
    2. A team ignores user feedback to protect the committed roadmap
    3. A team delivers the original scope on time despite new market evidence
    4. A team replans mid-increment after customer feedback reveals a more valuable opportunity Correct answer.

    Explanation

    Responding to change means adjusting direction when new information shows a better path, even mid-increment. The other options privilege plan adherence over evidence and therefore invert the value.

  20. Question 20Thriving in the Digital Age with Business Agility

    An organization measures agility only by velocity and sprint burndown. Which critique is most valid from a business agility perspective?

    1. They are leading indicators that predict revenue too precisely
    2. They are lagging indicators that cannot be collected frequently
    3. These are team-level output measures that do not reveal customer or business outcomes Correct answer.
    4. They overstate the importance of customer satisfaction

    Explanation

    Velocity and burndown describe internal team output and say little about whether customers or the business are better off. Business agility requires outcome-oriented measures that connect work to value.

  21. Question 21Becoming a SAFe Scrum Master

    In SAFe, which three roles together make up the Scrum Master's immediate team-level context in a Scrum Team?

    1. Release Train Engineer, Product Manager, and System Architect
    2. Business Owner, Epic Owner, and Solution Manager
    3. Product Owner, Scrum Master, and Developers Correct answer.
    4. Agile Coach, Portfolio Manager, and Value Stream Engineer

    Explanation

    A SAFe Scrum Team is composed of a Product Owner, a Scrum Master, and Developers, mirroring the Scrum Guide's three accountabilities. The other role sets belong to higher SAFe levels such as the ART or portfolio.

  22. Question 22Becoming a SAFe Scrum Master

    A SAFe Scrum Master is facilitating the team's iteration retrospective. Which outcome best demonstrates that the event served its purpose?

    1. The Scrum Master documented every complaint raised during the session
    2. The team confirmed that all planned stories were completed
    3. The team produced a prioritized list of one or two improvement actions with owners Correct answer.
    4. The Product Owner presented the next iteration's backlog

    Explanation

    The retrospective exists to inspect how the team works and to identify a small number of concrete improvements the team will act on. A short, owned action list is the standard evidence of a productive retrospective.

  23. Question 23Becoming a SAFe Scrum Master

    What is the primary purpose of the Iteration Review in a SAFe Scrum Team?

    1. To decide which team members will work on which stories
    2. To estimate the effort for the next iteration's backlog items
    3. To coach individual team members on their development goals
    4. To demonstrate the working, integrated increment and gather feedback from stakeholders Correct answer.

    Explanation

    The Iteration Review is a working session where the team demonstrates the integrated increment and stakeholders give feedback that informs the backlog. Estimation and task assignment happen in planning, and coaching is a separate Scrum Master activity.

  24. Question 24Becoming a SAFe Scrum Master

    During PI Planning, a SAFe Scrum Master's team has a dependency on another team's work that is not yet reflected on the program board. What is the most appropriate action?

    1. Log the dependency in the team's retrospective after the PI ends
    2. Wait until the system demo to raise the dependency with the Release Train Engineer
    3. Ask the Product Owner to reprioritize the backlog so the dependency disappears
    4. Record the dependency on the program board and coordinate with the other team during the event Correct answer.

    Explanation

    PI Planning is where cross-team dependencies are made visible on the program board so they can be managed during the PI. Raising them at the event, with the other team, is the intended flow.

  25. Question 25Becoming a SAFe Scrum Master

    Which statement accurately describes the relationship between iterations and the PI in SAFe?

    1. A PI is a fixed timebox containing several iterations plus an Innovation and Planning iteration Correct answer.
    2. A PI and an iteration are the same length and interchangeable
    3. An iteration contains several PIs, each ending with a system demo
    4. Iterations are optional, while the PI is the only required cadence

    Explanation

    A Program Increment is a longer fixed timebox made up of a series of iterations followed by an Innovation and Planning iteration. Iterations are the team's shorter cadence nested inside the PI.

  26. Question 26Becoming a SAFe Scrum Master

    A team consistently carries unfinished stories into the next iteration. As their Scrum Master, which action best reflects servant leadership?

    1. Help the team inspect its capacity and story sizing during the retrospective and let the team choose a fix Correct answer.
    2. Escalate the team's poor performance to the Release Train Engineer for correction
    3. Reassign the unfinished stories to the fastest developers on the team
    4. Direct the team to reduce story point estimates by twenty percent starting next iteration

    Explanation

    Servant leadership means helping the team diagnose its own problems and decide on improvements rather than imposing solutions. Facilitating inspection of capacity and sizing respects the team's ownership of its process.

  27. Question 27Becoming a SAFe Scrum Master

    What is the main purpose of the Innovation and Planning (IP) iteration at the end of a PI?

    1. To replace the iteration review with a formal management report
    2. To provide slack for innovation, planning, and PI system activities such as the Inspect and Adapt Correct answer.
    3. To run daily stand-ups without any other team ceremonies
    4. To deliver the remaining committed features that the team did not finish

    Explanation

    The IP iteration is intentionally unplanned capacity used for innovation, continuing education, PI planning preparation, and the Inspect and Adapt workshop. It is not a buffer for unfinished committed work.

  28. Question 28Becoming a SAFe Scrum Master

    During a daily stand-up, a developer reports being blocked by an environment issue that another team owns. What should the Scrum Master do?

    1. Take over the developer's task to keep the iteration on track
    2. Add the impediment to the retrospective list and wait for the PI to end
    3. Ask the developer to work around the issue without involving the other team
    4. Help the team resolve or escalate the impediment promptly and track it to closure Correct answer.

    Explanation

    Removing impediments is a core Scrum Master responsibility; the block should be acted on quickly, including escalation when another team is involved. Deferring it or taking over the work does not serve the team.

  29. Question 29Becoming a SAFe Scrum Master

    Which metric best helps a SAFe Scrum Master and team forecast whether they will meet their iteration goal?

    1. The team's velocity trend combined with remaining work in the iteration Correct answer.
    2. The total count of backlog items in the program backlog
    3. The number of commits pushed to the main branch each day
    4. The number of hours each developer is online

    Explanation

    Velocity trend plus remaining work gives a reasonable forecast of whether committed scope will be met. Activity metrics such as commits or online hours do not measure progress toward the goal.

  30. Question 30Becoming a SAFe Scrum Master

    What distinguishes a team PI objective from a committed PI objective in SAFe?

    1. Committed objectives are the team's high-confidence business goals, while uncommitted objectives are stretch goals Correct answer.
    2. Committed objectives are written after the PI, while uncommitted objectives are written before
    3. Committed objectives are owned by the RTE, while uncommitted objectives belong to the team
    4. Committed objectives are optional, while uncommitted objectives are mandatory

    Explanation

    Teams define committed objectives they are confident they can meet and may add uncommitted stretch objectives that provide flexibility. Both are planned during PI Planning and owned by the team.

  31. Question 31Becoming a SAFe Scrum Master

    A Scrum Master notices the team's Product Owner is consistently absent from backlog refinement, causing stories to arrive unready. Which response best fits the role?

    1. Cancel refinement until the Product Owner's schedule improves
    2. Write the acceptance criteria personally so refinement can proceed
    3. Report the Product Owner to the RTE as a performance problem
    4. Coach the team and Product Owner on the value of refinement and agree on a workable cadence Correct answer.

    Explanation

    The Scrum Master coaches the team and its stakeholders on effective collaboration, including backlog refinement. Facilitating an agreement on cadence addresses the root cause without taking over the Product Owner's accountability.

  32. Question 32Becoming a SAFe Scrum Master

    Which behavior is most consistent with the Scrum Master serving the larger organization in SAFe?

    1. Deciding the team's technical architecture during design discussions
    2. Acting as the team's sole interface to the Product Manager
    3. Approving all changes to the team's process before they are tried
    4. Helping non-agile stakeholders understand which of their requests fit the team's iteration cadence Correct answer.

    Explanation

    Serving the organization includes helping stakeholders understand and work with Scrum and the team's cadence. The Scrum Master does not gate process changes, monopolize stakeholder contact, or own technical decisions.

  33. Question 33Becoming a SAFe Scrum Master

    During the Inspect and Adapt workshop, a team's root-cause analysis shows that most missed PI objectives stem from late integration across teams. Which action is most appropriate?

    1. Remove the missed objectives from the record so the PI looks successful
    2. Propose a concrete improvement to integration cadence and track it as an ART improvement item Correct answer.
    3. Ask individual developers to work longer hours to catch up
    4. Lower the team's committed objectives for the next PI without addressing integration

    Explanation

    The Inspect and Adapt ends with a problem-solving workshop that produces improvement items for the ART backlog. Addressing the systemic integration issue and tracking it is the intended outcome.

  34. Question 34Becoming a SAFe Scrum Master

    A team new to SAFe asks their Scrum Master how the system demo differs from the iteration review. Which answer is most accurate?

    1. The system demo is team-level, while the iteration review involves the whole ART
    2. The iteration review happens once per PI, while the system demo happens every iteration
    3. They are identical events with different names in SAFe
    4. The iteration review is team-level, while the system demo shows the integrated solution from all teams on the ART Correct answer.

    Explanation

    Each team holds its own iteration review, and the ART holds a system demo that inspects the integrated increment from all teams. The system demo provides the broader, cross-team view.

  35. Question 35Becoming a SAFe Scrum Master

    A Scrum Master wants to foster a growth mindset on the team. Which action best supports that goal?

    1. Assign only tasks each person already excels at to avoid mistakes
    2. Encourage the team to treat failures in experiments as learning data during retrospectives Correct answer.
    3. Discourage the team from trying new practices until the PI ends
    4. Publicly compare developers' output so the weakest improve

    Explanation

    A growth mindset treats setbacks as learning opportunities, which the retrospective and safe experimentation support. Public comparison, avoiding challenge, and blocking experimentation all work against it.

  36. Question 36Becoming a SAFe Scrum Master

    Which situation best illustrates a Scrum Master applying systems thinking rather than blaming individuals?

    1. Adding more approval gates to catch errors before release
    2. Tracing recurring defects to the team's handoff and review process and proposing a process change Correct answer.
    3. Identifying the developer who introduced the most defects and requiring extra review of their work
    4. Asking the quietest team member to speak more in stand-ups

    Explanation

    Systems thinking looks at how the structure of work, such as handoffs and review steps, produces outcomes, and improves the system rather than singling out people. Blaming individuals or adding gates treats symptoms.

  37. Question 37Becoming a SAFe Scrum Master

    What is the primary focus of the Scrum Master during iteration execution in SAFe?

    1. Helping the team stay aligned to its iteration goals and removing impediments as they arise Correct answer.
    2. Reassigning tasks daily to balance utilization across developers
    3. Approving each story before it can be marked complete
    4. Writing the team's PI objectives on its behalf

    Explanation

    During execution the Scrum Master supports the team's focus on iteration goals and clears impediments. Task assignment, objective writing, and story approval remain with the team and Product Owner.

  38. Question 38Becoming a SAFe Scrum Master

    A team's flow is disrupted by large stories that span multiple iterations. Which Scrum Master action best addresses the root cause?

    1. Ask the Product Owner to accept partial completion of large stories
    2. Increase the iteration length to match the largest stories
    3. Add a second weekly stand-up to increase status reporting
    4. Coach the team on splitting stories during refinement so each fits within an iteration Correct answer.

    Explanation

    Stories that cannot finish within an iteration indicate sizing and refinement problems; coaching the team to slice stories smaller improves flow. Adding ceremonies, accepting partial work, or stretching the timebox treats symptoms.

  39. Question 39Becoming a SAFe Scrum Master

    Which pair of SAFe events gives the team its regular opportunities to inspect product progress and process health, respectively?

    1. The daily stand-up inspects product progress, and PI Planning inspects process health
    2. The system demo inspects process health, and the retrospective inspects product progress
    3. The iteration review inspects product progress, and the retrospective inspects process health Correct answer.
    4. Backlog refinement inspects product progress, and the iteration review inspects process health

    Explanation

    The iteration review inspects the increment and gathers feedback, while the retrospective inspects how the team works. Keeping these two purposes distinct is a core SAFe Scrum Master concept.

  40. Question 40Becoming a SAFe Scrum Master

    A Scrum Master is helping the team improve predictability. Which approach most aligns with SAFe guidance?

    1. Track individual utilization to keep every person fully loaded
    2. Commit to the maximum possible scope each iteration to raise velocity
    3. Hide risks from stakeholders until they are fully resolved
    4. Use PI objectives, iteration goals, and a visible team board to make progress and risks transparent Correct answer.

    Explanation

    Predictability improves when goals, progress, and risks are transparent so the team and ART can act on them. Maximizing utilization or scope and concealing risks reduce transparency and predictability.

  41. Question 41Establishing Team Agility

    In the STSC framework, a Scrum Team wants to become more self-managing. Which action best reflects the shift toward team agility?

    1. The Product Owner approves every technical decision before it is made
    2. The team decides together how to organize its own work within the sprint Correct answer.
    3. A separate manager reviews and reassigns work items each morning
    4. The Scrum Master assigns each task daily so work stays balanced

    Explanation

    Team agility grows when the people doing the work hold authority over how the work is done. Self-managing teams plan and coordinate their own tasks inside agreed boundaries such as the sprint goal and Definition of Done. External task assignment keeps decision rights outside the team and slows adaptation.

  42. Question 42Establishing Team Agility

    Which statement best describes the purpose of a team working agreement in establishing team agility?

    1. It records shared norms the team uses to coordinate and hold itself accountable Correct answer.
    2. It fixes each member's role permanently for the project
    3. It replaces the Definition of Done for the product increment
    4. It documents the manager's performance expectations for each member

    Explanation

    A working agreement captures the norms a team chooses for how it collaborates, communicates, and resolves conflict. Because the team authors it, it supports self-management and can be revised as the team learns. It is distinct from the Definition of Done and from role assignments.

  43. Question 43Establishing Team Agility

    A Scrum Master notices that all impediment decisions wait for the Scrum Master's approval. Which intervention most directly builds team agility?

    1. Keep approving impediment decisions but respond to requests faster
    2. Ask the team to route all impediments through a weekly steering committee
    3. Create a backlog of impediments and track resolution speed
    4. Coach the team to resolve impediments within agreed boundaries and escalate only when limits are exceeded Correct answer.

    Explanation

    Agility increases when the team has authority to act and clear escalation boundaries rather than a permanent approval gate. Coaching the team to decide within defined limits transfers decision rights while keeping safeguards. Faster approvals leave the bottleneck in place.

  44. Question 44Establishing Team Agility

    Which measure best indicates that a team is genuinely cross-functional rather than merely multi-person?

    1. The team uses a shared digital board for its tasks
    2. The team has members with different job titles on the org chart
    3. The team can deliver a done increment without handoffs to people outside the team Correct answer.
    4. The team holds a daily standup of fifteen minutes

    Explanation

    Cross-functionality means the team collectively holds the skills needed to deliver a done increment without depending on outside handoffs. Titles and ceremonies alone do not demonstrate that capability. The ability to finish work end to end is the practical test.

  45. Question 45Establishing Team Agility

    A team new to agile keeps asking the Scrum Master to decide how to split backlog items. What is the most appropriate coaching response?

    1. Assign splitting to the most senior developer each sprint
    2. Add splitting decisions to the next steering committee agenda
    3. Facilitate the team in choosing a splitting technique and reflect on the outcome Correct answer.
    4. Split the items yourself to keep the sprint moving

    Explanation

    Coaching builds capability by helping the team learn a technique and evaluate its results, so the skill stays with the team. Doing the work for them solves the immediate problem while reinforcing dependence. Permanent assignment to one person concentrates knowledge and reduces shared ownership.

  46. Question 46Establishing Team Agility

    According to the agile principle of self-organizing teams, what is the primary source of the best architectures, requirements, and designs?

    1. Approval by the program management office
    2. Self-organizing teams Correct answer.
    3. Analysis by external subject-matter experts
    4. The enterprise architecture board

    Explanation

    The agile principles state that the best architectures, requirements, and designs emerge from self-organizing teams. This reflects the value of decisions made by those closest to the work. External bodies can set constraints but are not the stated source of emergent design.

  47. Question 47Establishing Team Agility

    A team's retrospective produces the same three action items every sprint with no follow-through. Which change most improves team agility?

    1. Have the Scrum Master own all improvement actions
    2. Shorten the retrospective to thirty minutes
    3. Replace the retrospective with a monthly team survey
    4. Limit improvements to one or two owned actions with visible progress checks Correct answer.

    Explanation

    Improvement requires focus, clear ownership, and visible follow-through so the team can see results and adjust. A small number of owned actions is more likely to be completed than a long list. Moving ownership to the Scrum Master would weaken the team's accountability for its own growth.

  48. Question 48Establishing Team Agility

    Which situation most clearly signals that a team lacks psychological safety?

    1. Members challenge each other's technical assumptions during refinement
    2. Members rotate facilitation of the daily standup
    3. Members disagree openly and then agree on a path forward
    4. Members stay silent about risks in reviews because they fear blame Correct answer.

    Explanation

    Psychological safety is the shared belief that speaking up is safe. Silence about risks due to fear of blame is a direct indicator that the belief is missing. Healthy disagreement and rotating facilitation show safety rather than its absence.

  49. Question 49Establishing Team Agility

    A distributed team struggles because decisions made in side conversations are not shared. Which practice best supports team agility?

    1. Require all decisions to be approved by the product owner
    2. Ban informal side conversations during working hours
    3. Move all decisions to a weekly status meeting
    4. Record decisions and their rationale in a shared, accessible place Correct answer.

    Explanation

    Making decisions and their rationale visible lets every member act on the same information without waiting for a meeting or a person. Transparency supports faster, decentralized decision-making. Banning conversations or centralizing approval reduces the team's ability to act.

  50. Question 50Establishing Team Agility

    Which team-level metric best reflects improved agility rather than merely more output?

    1. Number of story points completed per developer
    2. Total lines of code committed each week
    3. Count of meetings held per sprint
    4. Cycle time from work start to a done increment Correct answer.

    Explanation

    Cycle time measures how quickly work flows from start to a genuinely done state, which reflects responsiveness to change. Output-per-person and code volume reward activity rather than adaptability. Meeting counts say nothing about the team's ability to deliver value.

  51. Question 51Establishing Team Agility

    A Scrum Master wants the team to take ownership of its sprint goal. Which facilitation approach best supports this?

    1. Set the sprint goal yourself before planning so the team has direction
    2. Derive the sprint goal from last sprint's velocity target
    3. Let the team draft the sprint goal and test it against stakeholder needs Correct answer.
    4. Ask the product owner to assign individual goals to each member

    Explanation

    When the team drafts its own sprint goal and checks it against stakeholder needs, it owns both the commitment and the reasoning behind it. This builds shared purpose and self-management. Goals imposed by others or reduced to a velocity number do not create ownership.

  52. Question 52Establishing Team Agility

    Which behavior by a Scrum Master is most consistent with servant leadership?

    1. Directing task assignments to maximize utilization
    2. Removing organizational impediments the team cannot address itself Correct answer.
    3. Approving the team's technical design choices
    4. Reporting individual performance to line managers

    Explanation

    Servant leadership focuses on enabling the team by clearing obstacles that lie beyond its authority. This expands what the team can accomplish on its own. Directing tasks, approving designs, and reporting on individuals all shift control away from the team.

  53. Question 53Establishing Team Agility

    A team consistently overcommits and then misses its sprint goal. Which structural change best builds sustainable agility?

    1. Increase the number of items to motivate faster work
    2. Commit to fewer items and use the freed capacity to improve quality practices Correct answer.
    3. Remove the sprint goal so misses are no longer visible
    4. Add overtime hours to close the gap each sprint

    Explanation

    Sustainable pace comes from matching commitment to real capacity and using slack to strengthen practices. This improves predictability and quality over time. Overtime and inflated commitments trade short-term output for burnout and rising defects.

  54. Question 54Establishing Team Agility

    Which practice most directly helps a team make its work visible enough to self-manage?

    1. Track progress only in the monthly status report
    2. Keep a private spreadsheet of tasks owned by the Scrum Master
    3. Maintain a board showing work items and their flow states for all to see Correct answer.
    4. Rely on verbal updates in the daily standup

    Explanation

    A visible board showing items and their flow states gives the team a shared, current picture it can act on directly. Visibility is a precondition for self-management because the team must see the work to coordinate it. Private tracking or periodic reports delay and restrict that view.

  55. Question 55Establishing Team Agility

    A team member repeatedly bypasses the team and takes concerns straight to senior management. What is the most useful first step for the Scrum Master?

    1. Remove the member from the team
    2. Ignore it because escalation is always acceptable
    3. Escalate the member's behavior to human resources
    4. Discuss the impact on the team and agree on a shared escalation path Correct answer.

    Explanation

    The Scrum Master should surface the effect on team trust and agree with the team on how concerns are raised and escalated. A shared path preserves both transparency and the team's ownership of its issues. Punitive or dismissive responses address the symptom rather than the coordination gap.

  56. Question 56Establishing Team Agility

    Which factor most limits a team's ability to become self-managing when a functional manager still approves leave and tooling requests?

    1. The team has not adopted story point estimation
    2. Decision rights over team resources remain outside the team Correct answer.
    3. The team uses two different chat tools
    4. The team lacks a dedicated meeting room

    Explanation

    Self-management depends on the team holding meaningful decision rights, including over how it organizes resources and work. When approvals for leave and tooling sit with an external manager, the team cannot act on its own plans. Tooling or estimation choices are secondary to where authority resides.

  57. Question 57Establishing Team Agility

    A team says it is self-managing but still waits for the product owner to break every large item into sprint-sized work. Which interpretation is most accurate?

    1. The team is fully self-managing because the product owner sets priorities
    2. The product owner should also assign tasks to each developer
    3. The team has authority over how but not yet over decomposing work, so self-management is partial Correct answer.
    4. The team should stop refining items entirely

    Explanation

    Self-management covers how the team turns selected backlog items into done work, including decomposition. If the product owner must split every item, decision rights over 'how' are still partly external. The situation is partial self-management rather than full self-management or a reason to abandon refinement.

  58. Question 58Establishing Team Agility

    Which approach best builds a team's capacity to make good decisions without escalation over time?

    1. Require escalation for every decision until the team has five years of experience
    2. Define decision boundaries and let the team practice deciding within them Correct answer.
    3. Rotate decision authority among managers outside the team
    4. Have the Scrum Master make decisions and explain them afterward

    Explanation

    Clear boundaries plus repeated practice let a team build judgment while keeping risk contained. Authority expands as competence and trust grow. Long escalation periods, decisions made for the team, or authority held by outside managers prevent that learning.

  59. Question 59Establishing Team Agility

    Which statement about the Definition of Done best supports team agility?

    1. It is a shared team commitment that makes 'done' transparent and can be strengthened over time Correct answer.
    2. It is set by the quality assurance department and never changes
    3. It lists every task each developer must perform
    4. It replaces the need for a sprint goal

    Explanation

    A shared Definition of Done creates a common standard for what completed means, enabling transparency and consistent quality. Teams may raise the bar as their capability grows. It is not a task checklist and does not substitute for the sprint goal.

  60. Question 60Establishing Team Agility

    A team's members each report progress to their functional manager rather than to each other. Which change most strengthens team agility?

    1. Increase the frequency of individual status reports
    2. Shift reporting to team-level progress against the sprint goal Correct answer.
    3. Keep individual reporting but shorten the templates
    4. Add a manager to the daily standup to collect updates

    Explanation

    Team agility depends on members coordinating around shared goals rather than reporting upward in parallel. Team-level progress against the sprint goal creates mutual accountability. More frequent or streamlined individual reporting preserves the silos.

  61. Question 61Establishing Team Agility

    Which combination best characterizes a high-performing agile team?

    1. Shared goals, trust, and the ability to adapt its own process Correct answer.
    2. High utilization of every member at all times
    3. Strict role boundaries enforced by management
    4. Strong individual specialization with minimal interaction

    Explanation

    High-performing agile teams align on shared goals, trust one another, and continuously adapt how they work. These traits let the team respond to change without waiting for direction. Rigid roles and constant full utilization leave no room for learning or adjustment.

  62. Question 62Establishing Team Agility

    A team wants to reduce its dependence on the Scrum Master for facilitation. Which step best develops that capability?

    1. Have team members rotate facilitation of ceremonies with coaching support Correct answer.
    2. Hire a second Scrum Master to share the load
    3. Keep the Scrum Master as permanent facilitator to ensure consistency
    4. Cancel ceremonies that the team can run without help

    Explanation

    Rotating facilitation with coaching distributes the skill across the team and reduces single-person dependence. Consistency improves through practice and reflection rather than through permanent ownership. Cancelling ceremonies or adding another Scrum Master does not build team capability.

  63. Question 63Establishing Team Agility

    Which observation most strongly suggests a team has moved from storming toward performing?

    1. Members resolve conflicts directly and adjust their process without escalation Correct answer.
    2. Members rely on the Scrum Master to settle every dispute
    3. Members avoid disagreement to keep the peace
    4. Members socialize frequently but avoid committing to work

    Explanation

    In the performing stage, the team handles conflict internally and adapts its process with little outside intervention. Direct resolution and self-adjustment are the clearest signs. Avoidance, escalation, and socializing without commitment reflect earlier stages.

  64. Question 64Establishing Team Agility

    A team's improvement backlog contains only items owned by the Scrum Master. What does this most likely indicate about the team's agility?

    1. The team is delegating improvement work and may not yet own its own growth Correct answer.
    2. The team is performing at its highest level
    3. The team has too few improvement opportunities
    4. The team has fully internalized continuous improvement

    Explanation

    When all improvements are owned by the Scrum Master, the team is not yet treating its own growth as its responsibility. Ownership of improvement is a hallmark of a self-managing team. The pattern points to dependence rather than to maturity or a shortage of opportunities.

  65. Question 65Establishing Team Agility

    Which action best supports a team in making trade-offs between new feature work and reducing technical debt?

    1. Mandate that all technical debt be fixed before any new features
    2. Let the team make the trade-off visible and decide with the product owner using clear criteria Correct answer.
    3. Leave the trade-off to the architect alone
    4. Ignore technical debt until a release is blocked

    Explanation

    Making the trade-off visible and deciding it with the product owner using explicit criteria keeps the team empowered while respecting product priorities. Blanket rules, unilateral decisions, or neglect all remove the team's judgment from a decision it must live with.

  66. Question 66Establishing Team Agility

    A Scrum Master wants the team to own its improvement work rather than wait for assigned tasks. Which action best develops that ownership in the first few sprints?

    1. Track improvement items in a separate tool owned by the Scrum Master
    2. Have the team select and commit to its own improvement experiments each retrospective Correct answer.
    3. Assign each improvement item to a named individual with a deadline
    4. Ask the manager to set improvement goals for the team

    Explanation

    Ownership grows when the team chooses its own improvement goals and commits to them publicly. Selecting experiments at the retrospective keeps decision authority with the people doing the work, which is the core of team agility. Assigning goals from outside shifts accountability back to the assigner.

  67. Question 67Establishing Team Agility

    Which team behavior most directly indicates that a team is self-organizing rather than merely self-managing its assigned work?

    1. The team holds its daily meeting at the same time each day
    2. The team reports its velocity to stakeholders every sprint
    3. The team adjusts its own process and working agreements when it sees a problem Correct answer.
    4. The team completes every item the product owner hands it each sprint

    Explanation

    Self-organization means the team designs and changes how it works, not just how it executes assigned tasks. Adjusting its own process and agreements shows authority over its operating model. Completing handed-down items or holding regular ceremonies shows discipline but not self-design.

  68. Question 68Establishing Team Agility

    A team has strong technical skills but avoids conflict, so disagreements are never surfaced and decisions are made by whoever speaks first. Which intervention most directly builds the team's agility?

    1. Split the team so that fewer disagreements arise
    2. Add a technical lead who makes the final call on disputed items
    3. Move decision-making to the product owner to reduce friction
    4. Establish working agreements for how the team will disagree and decide Correct answer.

    Explanation

    Agility depends on the team's ability to surface and resolve differences productively. Explicit agreements about disagreement and decision-making give the team a repeatable way to reach shared conclusions. Removing conflict by centralizing decisions trades short-term calm for long-term dependence.

  69. Question 69Establishing Team Agility

    Which structural condition is most essential for a team to be able to self-manage its daily work?

    1. The team has the authority to decide how to do the work it has committed to Correct answer.
    2. The team has a fixed budget for the full year
    3. The team has a dedicated project manager who coordinates dependencies
    4. The team's members all report to the same functional manager

    Explanation

    Self-management requires real authority over how work is performed, not just responsibility for outcomes. Without that authority, the team must escalate routine decisions and cannot adapt. Coordination roles, reporting lines, and budgets may help but do not substitute for decision authority.

  70. Question 70Establishing Team Agility

    A team's velocity is stable, but cycle time for small items keeps rising and the team cannot explain why. Which first step best strengthens the team's ability to self-manage?

    1. Ask the Scrum Master to investigate and report the cause
    2. Have the team visualize its workflow and measure where items wait Correct answer.
    3. Add a status report to management on cycle time
    4. Increase the sprint length to absorb the delay

    Explanation

    Self-managing teams need to see their own system of work before they can improve it. Visualizing the workflow and measuring waiting time lets the team find and act on its own bottlenecks. Delegating the investigation or adding reporting keeps the analysis outside the team.

  71. Question 71Establishing Team Agility

    Which practice best helps a team build shared understanding of a complex user story before it commits to it?

    1. Have the product owner write a more detailed specification alone
    2. Defer all discussion of the story until the sprint planning meeting
    3. Run a short collaborative refinement session where the team discusses examples and edge cases Correct answer.
    4. Estimate the story in a meeting attended only by senior developers

    Explanation

    Shared understanding forms through conversation about concrete examples and edge cases. Collaborative refinement spreads knowledge across the team and surfaces assumptions before commitment. Solo specification or partial attendance leaves understanding concentrated in a few people.

  72. Question 72Establishing Team Agility

    A team consistently finishes its sprint work early and then pulls in unplanned items, which causes quality problems. Which change best supports sustainable agility?

    1. Have the team agree on how much slack to reserve and what criteria new work must meet Correct answer.
    2. Extend the sprint so the team has more room for unplanned items
    3. Ask the product owner to add more stories at planning to fill the capacity
    4. Ban all new work from entering a sprint once it has started

    Explanation

    Sustainable agility comes from deliberate agreements about capacity and the conditions for accepting new work. Agreeing on slack and entry criteria lets the team absorb change without eroding quality. A blanket ban removes flexibility, which is equally damaging.

  73. Question 73Establishing Team Agility

    Which action by a Scrum Master most directly builds the team's long-term capacity to facilitate its own events?

    1. Document a standard agenda and require facilitators to follow it exactly
    2. Continue facilitating all ceremonies to keep them consistent and efficient
    3. Invite an external agile coach to run the retrospectives each sprint
    4. Rotate facilitation of ceremonies among team members with coaching and feedback Correct answer.

    Explanation

    Capability grows through practice with support, so rotating facilitation with coaching transfers the skill to the team. Keeping facilitation centralized, even efficiently, preserves dependence on one person. Rigid agendas or external coaches teach the team to follow rather than to lead.

  74. Question 74Establishing Team Agility

    Which statement best describes the relationship between team agility and a shared Definition of Done?

    1. A shared Definition of Done removes the need for a retrospective because quality is assured
    2. A shared Definition of Done lets the team judge completion consistently and improve its own quality bar Correct answer.
    3. A shared Definition of Done should be kept flexible so each member can apply personal standards
    4. A shared Definition of Done is a quality gate imposed by the quality assurance function

    Explanation

    A shared Definition of Done gives the team a common, team-owned standard for what complete means. That shared reference lets the team assess its own work and raise the bar deliberately over time. It is a team agreement, not an externally imposed gate or a substitute for reflection.

  75. Question 75Establishing Team Agility

    A team's retrospective actions are consistently owned by the Scrum Master, and team members describe improvement as "the Scrum Master's project." Which interpretation is most accurate?

    1. The team needs a larger improvement backlog to stay engaged
    2. The team has not yet internalized ownership of its own improvement Correct answer.
    3. The team is performing well because improvement is being managed centrally
    4. The Scrum Master is correctly shielding the team from extra work

    Explanation

    When all improvement work sits with the Scrum Master, the team is a spectator in its own growth. Team agility requires the team to own its improvement experiments and their outcomes. Central management of improvement signals dependence, not high performance.

  76. Question 76Establishing Team Agility

    Which observation most strongly suggests a team has matured from storming into performing?

    1. The team relies on the Scrum Master to resolve every dispute
    2. Members avoid disagreement to keep the atmosphere calm
    3. Members challenge each other's ideas directly and still leave meetings aligned Correct answer.
    4. Members socialize often but rarely discuss how they work together

    Explanation

    Performing teams can disagree openly and still reach alignment because trust and shared norms are in place. Constructive challenge without lasting friction is a strong marker of that maturity. Avoiding conflict or relying on a facilitator for every dispute signals earlier stages.

  77. Question 77Establishing Team Agility

    A team wants to reduce its dependence on the Scrum Master for removing impediments. Which step best develops that capability?

    1. Coach the team to identify, escalate, and track its own impediments with clear ownership Correct answer.
    2. Remove the impediment discussion from the daily meeting to save time
    3. Have the Scrum Master keep a private list and resolve impediments quietly
    4. Escalate all impediments to management so the team can stay focused

    Explanation

    Impediment removal becomes a team capability when the team can name blockers, decide who acts, and track resolution itself. Coaching that behavior transfers the skill rather than the task. Quiet resolution by the Scrum Master, upward escalation, or dropping the discussion all keep the team dependent.

  78. Question 78Establishing Team Agility

    Which factor most directly limits a team's ability to become self-managing when a functional manager still approves leave and timesheets?

    1. The team meets in person only once a week
    2. The team lacks a documented set of coding standards
    3. The team has no dedicated product owner
    4. Decision rights over the team's own working arrangements remain outside the team Correct answer.

    Explanation

    Self-management depends on the team holding decision rights over how it organizes its work, including time and availability. When approvals stay with a functional manager, the team cannot plan or adapt its own capacity. Coding standards, meeting cadence, and role gaps matter but do not remove authority in the same way.

  79. Question 79Establishing Team Agility

    Which practice most directly helps a team make trade-offs between new feature work and reducing technical debt?

    1. Make technical debt visible in the same backlog and prioritize it alongside features Correct answer.
    2. Track technical debt in a document only the architects can access
    3. Defer technical debt until a dedicated hardening sprint at year end
    4. Assign all technical debt work to a separate team

    Explanation

    Trade-offs require both kinds of work to be visible in the same place and weighed together. Putting technical debt in the product backlog lets the team and product owner decide priority transparently. Separating ownership or hiding the information prevents informed trade-offs.

  80. Question 80Establishing Team Agility

    A newly formed team is enthusiastic but has no agreed norms for how it communicates and reviews work. Which action best accelerates its path to reliable delivery?

    1. Facilitate the team in creating explicit working agreements it can revise Correct answer.
    2. Wait until the first missed commitment before discussing norms
    3. Have the manager publish a set of rules the team must follow
    4. Let norms emerge naturally without discussion to preserve spontaneity

    Explanation

    Explicit, team-created working agreements give a new team a shared reference for expectations and a way to adjust them. Because the team authors and revises them, the agreements support self-management rather than compliance. Waiting for failure or imposing rules from outside slows the team's development.

  81. Question 81Building High-Performing Teams

    A Scrum Master notices that the team's Daily Scrum has become a status report to the manager who attends. Which action best preserves the event's purpose while respecting Scrum?

    1. Convert the Daily Scrum into a formal review where the manager assigns tasks for the day
    2. Cancel the Daily Scrum and replace it with a weekly written status report to the manager
    3. Instruct each developer to give a longer, more detailed status update so the manager stays informed
    4. Ask the manager to stop attending so the Developers can inspect their progress toward the Sprint Goal Correct answer.

    Explanation

    The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal and adapt their plan; it is not a reporting ceremony to stakeholders. Coaching the manager about the event's purpose and protecting the Developers' self-management restores its intended function. Removing inspection entirely or turning it into task assignment by a manager undermines self-management rather than fixing it.

  82. Question 82Building High-Performing Teams

    Which statement best describes the primary purpose of a Sprint Retrospective?

    1. To review the product backlog and reorder items for the next Sprint
    2. To demonstrate the completed Increment to stakeholders for feedback
    3. To negotiate the Sprint Goal with the Product Owner before planning
    4. To plan which improvements the team will make to its quality and effectiveness Correct answer.

    Explanation

    The Retrospective is where the team inspects how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, then identifies the most helpful improvements. Those improvements are typically turned into concrete actions for the next Sprint. Demonstrating work and ordering the backlog belong to other events.

  83. Question 83Building High-Performing Teams

    A newly formed team of five has strong individual experts but members rarely ask each other for help. Which team-development focus is most appropriate first?

    1. Adding two more experts to reduce the workload on each individual
    2. Pushing the team straight to a high-performance state by raising delivery targets
    3. Removing all retrospectives until the team has stabilized
    4. Establishing psychological safety so members can admit uncertainty and request help Correct answer.

    Explanation

    Teams whose members cannot admit uncertainty or ask for help remain a collection of individuals rather than a collaborative unit. Psychological safety is the foundation that lets norms of mutual assistance and constructive conflict develop. Raising targets, adding headcount, or removing reflection does not address the interpersonal barrier.

  84. Question 84Building High-Performing Teams

    What does a clear Definition of Done primarily enable for a Scrum team?

    1. A guarantee that every Sprint will meet its forecast of backlog items
    2. A replacement for the Sprint Goal during Sprint Planning
    3. A fixed list of tasks that the Scrum Master assigns each day
    4. A shared understanding of when work is complete and potentially releasable Correct answer.

    Explanation

    The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It creates shared transparency so everyone agrees on what complete means. It does not guarantee scope, replace the Sprint Goal, or serve as a task-assignment tool.

  85. Question 85Building High-Performing Teams

    During a Retrospective, one developer repeatedly dominates the conversation while quieter members stay silent. Which facilitation move best improves the team's effectiveness?

    1. Use a structured format such as silent writing or round-robin so all voices are heard before open discussion Correct answer.
    2. Let the dominant member continue since they usually have the most valuable insights
    3. Ask the Scrum Master to decide which improvements the team should adopt
    4. End the Retrospective early to avoid interpersonal tension

    Explanation

    Structured formats like silent brainstorming, dot voting, or round-robin give every participant an equal entry point before open debate. This surfaces more perspectives and reduces the dominance of a single voice. Allowing one person to dominate or having the Scrum Master decide undermines collective ownership of improvements.

  86. Question 86Building High-Performing Teams

    A team consistently commits to more work than it finishes each Sprint. Which action most directly supports building a sustainable, high-performing team?

    1. Reduce the Definition of Done so more items count as complete
    2. Stop measuring progress so the team feels less pressure
    3. Use Sprint data to right-size the forecast and address the causes of overcommitment in the Retrospective Correct answer.
    4. Add overtime so the team can meet the commitments it already made

    Explanation

    Repeated overcommitment signals a forecasting and capacity problem that should be examined with real Sprint data. Adjusting the forecast and addressing root causes in the Retrospective builds a realistic, sustainable pace. Overtime, lowering quality standards, or abandoning transparency treats symptoms rather than causes.

  87. Question 87Building High-Performing Teams

    Which behavior best exemplifies servant leadership from a Scrum Master toward the team?

    1. Removing organizational impediments the team has raised and coaching the team to solve its own problems Correct answer.
    2. Approving or rejecting the team's technical design decisions
    3. Reporting individual velocity rankings to senior management
    4. Assigning each developer their daily tasks to ensure the Sprint stays on track

    Explanation

    Servant leadership means serving the team's needs by clearing impediments and coaching toward self-management rather than directing work. The Scrum Master helps the team become capable of solving problems itself. Assigning tasks, ranking individuals, or gatekeeping technical decisions are command-and-control behaviors.

  88. Question 88Building High-Performing Teams

    A cross-functional team includes a designer, two developers, and a tester who each report to different functional managers. Which structural change most supports high performance?

    1. Rotate members between teams every week to spread expertise
    2. Give the team a shared goal and let members coordinate directly across functions Correct answer.
    3. Assign each specialist to work only within their own function's queue
    4. Require all cross-functional communication to flow through the functional managers

    Explanation

    High-performing teams need a shared purpose and direct lines of communication among members, which reduces handoffs and delays. Cross-functional coordination through managers adds latency and dilutes ownership. Isolating specialists or constant rotation prevents the team from forming stable working relationships.

  89. Question 89Building High-Performing Teams

    Which metric is most useful for a team reflecting on its own improvement over several Sprints?

    1. Number of hours each person spends in meetings
    2. Individual lines of code written per developer
    3. The manager's subjective ranking of each team member
    4. Trends in cycle time and throughput for the team as a whole Correct answer.

    Explanation

    Team-level flow metrics such as cycle time and throughput reveal whether the team's process is improving and where bottlenecks lie. Individual output metrics invite gaming and damage collaboration. Meeting hours and subjective rankings do not measure the team's delivery effectiveness.

  90. Question 90Building High-Performing Teams

    A high-performing team is asked to take on a second product area while keeping its current commitments. What is the most effective response from the team's leadership?

    1. Split the team in half immediately so each area has dedicated people
    2. Assess capacity with the team and explicitly trade off existing work before adding scope Correct answer.
    3. Accept the new area and rely on the team to absorb it through extra effort
    4. Add the new area to the backlog without changing priorities or capacity

    Explanation

    Sustainable high performance depends on explicit trade-offs between demand and capacity. Leadership should involve the team in assessing load and deciding what to stop or defer before adding scope. Absorbing work through extra effort, silently expanding the backlog, or reflexive splitting degrades focus and quality.

  91. Question 91Building High-Performing Teams

    Which practice most directly builds shared ownership of the Sprint Goal across the team?

    1. Having the Developers collaboratively craft the Sprint Goal during Sprint Planning Correct answer.
    2. Setting a Sprint Goal that restates the list of selected backlog items
    3. Having the Product Owner set the Sprint Goal alone and announce it afterward
    4. Deriving the Sprint Goal from the manager's quarterly targets without team input

    Explanation

    When the Developers collaborate on the Sprint Goal, they commit to a shared objective rather than a list of tasks. This collective crafting builds ownership and coherence around why the Sprint matters. Unilateral goal-setting or a goal that merely restates items weakens commitment and focus.

  92. Question 92Building High-Performing Teams

    A Scrum Master wants to help a team improve its ability to self-manage. Which coaching approach is most appropriate?

    1. Ask open questions that help the team reflect on its own process and decide its next experiment Correct answer.
    2. Step in and make decisions whenever the team hesitates
    3. Provide detailed instructions for every ceremony so the team follows best practice exactly
    4. Withhold information about impediments to avoid worrying the team

    Explanation

    Coaching for self-management uses powerful questions and reflection so the team develops its own judgment and experiments. Prescribing every step or deciding for the team creates dependency. Transparency about impediments is essential for the team to address them.

  93. Question 93Building High-Performing Teams

    What is the main risk of a team treating velocity as a performance target set by management?

    1. Sprint Reviews will be cancelled to save time for estimation
    2. Velocity will automatically decrease because teams resist measurement
    3. The Definition of Done will become stricter without any team discussion
    4. Teams may inflate estimates and split work to hit the number, distorting transparency Correct answer.

    Explanation

    When velocity becomes a management target, it stops being a planning aid and invites gaming through inflated estimates or artificially small items. This corrupts the transparency the metric was meant to provide. Velocity is a team-internal forecasting tool, not a productivity score.

  94. Question 94Building High-Performing Teams

    Which situation best indicates that a team has developed effective conflict-resolution norms?

    1. Members settle disputes by majority vote without discussion
    2. Members raise disagreements early and resolve them directly with each other Correct answer.
    3. Members escalate every disagreement to the Scrum Master for a ruling
    4. Members avoid disagreement to keep meetings pleasant

    Explanation

    Healthy teams treat task conflict as a normal part of improving work and resolve it directly among the people involved. Early, direct resolution preserves trust and speed. Escalating everything, avoiding conflict, or voting without discussion leaves issues unresolved or suppresses information.

  95. Question 95Building High-Performing Teams

    A distributed team struggles because members in different time zones miss informal context. Which action best supports team performance?

    1. Establish explicit communication agreements and record key decisions where all members can access them Correct answer.
    2. Reduce written documentation to encourage more synchronous talk
    3. Rely on informal hallway conversations and hope context spreads
    4. Require everyone to attend all meetings live regardless of time zone

    Explanation

    Distributed teams need deliberate communication norms and durable records of decisions to replace the informal context that co-located teams get for free. Explicit agreements make collaboration predictable across time zones. Mandatory live attendance, reliance on hallway chat, or reducing documentation all increase information gaps.

  96. Question 96Building High-Performing Teams

    Which of the following best distinguishes a team from a mere group of individuals working on related tasks?

    1. A team uses a shared calendar and chat channel
    2. A team shares a common goal and holds itself mutually accountable for outcomes Correct answer.
    3. A team has more members than a group does
    4. A team reports to a single manager

    Explanation

    The defining feature of a team is a shared purpose combined with mutual accountability for results. Size, reporting lines, and shared tools are incidental characteristics that do not create interdependence. Without a common goal and mutual accountability, individuals remain a working group.

  97. Question 97Building High-Performing Teams

    A team's Sprint Review has turned into a one-way slide presentation with no stakeholder discussion. What change best restores the event's value?

    1. Move the Review to a written report distributed after the Sprint
    2. Limit stakeholder questions to a fixed five minutes at the end
    3. Invite stakeholders to inspect the Increment and discuss what to do next collaboratively Correct answer.
    4. Extend the slide deck with more metrics so stakeholders understand the work

    Explanation

    The Sprint Review is a working session where the team and stakeholders inspect the Increment and adapt the Product Backlog together. Discussion and feedback are the point, not presentation polish. More slides, written reports, or tightly capped questions all reduce the collaboration the event requires.

  98. Question 98Building High-Performing Teams

    Which action by a Product Owner most supports a team's ability to focus during a Sprint?

    1. Continuously adding urgent items to the current Sprint to keep stakeholders happy
    2. Changing the Sprint Goal whenever a stakeholder requests a new feature
    3. Assigning daily tasks to developers to keep priorities clear
    4. Protecting the Sprint Goal by deferring new requests to the next Sprint unless the goal is at risk Correct answer.

    Explanation

    Focus is protected when the Product Owner shields the Sprint Goal from churn and channels new requests into the next Sprint or a renegotiation only when the goal is threatened. Constant additions or goal changes destroy the team's ability to finish coherent work. Assigning daily tasks is not the Product Owner's role.

  99. Question 99Building High-Performing Teams

    Which practice most reliably helps a team improve its Definition of Done over time?

    1. Reviewing the Definition of Done in the Retrospective and tightening it as capability grows Correct answer.
    2. Removing quality criteria whenever a Sprint is running late
    3. Letting each developer apply their own personal definition of done
    4. Freezing the Definition of Done permanently at project start

    Explanation

    The Definition of Done should evolve as the team's capability and the product's quality expectations grow. The Retrospective is the natural place to inspect and strengthen it. Freezing it, letting individuals apply private standards, or dropping criteria under pressure erodes transparency and quality.

  100. Question 100Building High-Performing Teams

    A team member consistently misses commitments and the rest of the team covers the work silently. What is the most constructive leadership response?

    1. Address the pattern directly with the individual and the team, clarifying expectations and support Correct answer.
    2. Publicly shame the member in the next Retrospective as an example
    3. Reassign the member's work permanently without any conversation
    4. Ignore it because the work is still getting done

    Explanation

    Mutual accountability requires honest, respectful conversations about expectations and the support needed to meet them. Addressing the pattern directly preserves trust and gives the individual a chance to improve. Public shaming, avoidance, or silent reassignment damages trust and leaves the root cause unaddressed.

  101. Question 101Building High-Performing Teams

    Which statement about the Scrum Master's role on a high-performing team is most accurate?

    1. The Scrum Master owns the product backlog and prioritizes features
    2. The Scrum Master helps the team and organization adopt Scrum practices and removes impediments Correct answer.
    3. The Scrum Master approves or rejects the team's estimates
    4. The Scrum Master directs the Developers' technical work

    Explanation

    The Scrum Master serves the team and the wider organization by teaching Scrum, facilitating events, and removing impediments. Backlog ownership belongs to the Product Owner, and technical decisions belong to the Developers. The Scrum Master does not gatekeep estimates or direct technical work.

  102. Question 102Building High-Performing Teams

    What is the most likely effect of a team skipping Retrospectives for several Sprints to focus on delivery?

    1. Delivery speed increases permanently because no time is spent in meetings
    2. The team loses its main structured opportunity to improve and problems compound Correct answer.
    3. The Definition of Done automatically becomes clearer
    4. Stakeholder feedback improves because the team has more time

    Explanation

    The Retrospective is the team's dedicated mechanism for inspecting its way of working and choosing improvements. Skipping it removes that feedback loop, so recurring problems go unaddressed and accumulate. Short-term time savings do not translate into lasting speed or improved quality.

  103. Question 103Building High-Performing Teams

    A team is highly skilled but avoids committing to any improvement actions after Retrospectives. Which intervention best addresses this pattern?

    1. Stop holding Retrospectives until the team feels ready to act
    2. Assign the Scrum Master to implement all improvement actions
    3. Add more improvement ideas to the Retrospective output each time
    4. Limit the team to one or two concrete improvement actions per Sprint with clear owners Correct answer.

    Explanation

    Teams that generate ideas but never act usually lack focus and ownership. Choosing a small number of concrete actions with named owners makes follow-through realistic and visible. Piling on more ideas, outsourcing the work to the Scrum Master, or pausing Retrospectives all reinforce inaction.

  104. Question 104Building High-Performing Teams

    Which behavior most clearly signals that a team has achieved a high degree of self-management?

    1. The team waits for the Scrum Master to resolve every blocker
    2. The team adjusts its own plan during the Sprint when it discovers new information Correct answer.
    3. The team asks the manager to prioritize its daily tasks
    4. The team follows a fixed task list regardless of new findings

    Explanation

    Self-managing teams decide how to do their work and adapt their plan as they learn, without waiting for direction. Waiting for others to clear blockers, having tasks prioritized externally, or rigidly following a stale plan all indicate dependence. Adaptation within the Sprint is a hallmark of mature self-management.

  105. Question 105Building High-Performing Teams

    A team's Retrospective keeps producing the same complaint about unclear requirements, but nothing changes. What should the Scrum Master do first?

    1. Record the complaint again in the next Retrospective and move on
    2. Escalate to senior management to force the Product Owner to comply
    3. Conclude that the team is not ready for Retrospectives
    4. Help the team trace the issue to its source and agree on a specific, owned action with the Product Owner Correct answer.

    Explanation

    Recurring complaints usually mean the issue has not been translated into a specific, owned action involving the right people. Facilitating a conversation that identifies the source and agrees on a concrete action with the Product Owner addresses the loop. Re-recording, escalating prematurely, or abandoning the Retrospective avoids the underlying cause.

  106. Question 106Building High-Performing Teams

    A Scrum Team is forming and members are still polite, cautious, and unsure how much to challenge each other. Using Tuckman's model of group development, which stage is the team most likely in?

    1. Storming
    2. Norming
    3. Performing
    4. Forming Correct answer.

    Explanation

    In Tuckman's model, the forming stage is characterized by orientation, dependence on a leader, and low willingness to disagree openly. Storming follows as conflict surfaces, norming as agreements solidify, and performing as the team operates with high autonomy.

  107. Question 107Building High-Performing Teams

    A Scrum Master notices that two developers disagree strongly about a technical approach during refinement. Which action best reflects the Scrum Master serving the team's development toward self-management?

    1. Facilitate the discussion so the team reaches its own decision and records it Correct answer.
    2. Ask the two developers to raise the issue only outside team meetings
    3. Decide the technical approach to end the disagreement quickly
    4. Escalate the disagreement to the engineering manager for a ruling

    Explanation

    Self-managing teams choose how to do their work, so the Scrum Master's job is to help the team resolve the conflict itself and make the outcome visible. Deciding for them or escalating removes ownership and teaches the team to depend on authority.

  108. Question 108Building High-Performing Teams

    A team has strong individual specialists, but work stalls whenever one person is unavailable because only they understand a component. Which action most directly addresses this bottleneck?

    1. Ask the specialist to write more detailed handover documents
    2. Pair team members across components so knowledge is shared Correct answer.
    3. Increase the number of items taken into the Sprint
    4. Add a buffer to the Sprint to absorb the delays

    Explanation

    The bottleneck is single-person knowledge, so the team needs deliberate cross-learning such as pairing and swarming on work outside each person's specialty. Documentation helps but does not build the shared capability the team needs to keep flow when someone is absent.

  109. Question 109Building High-Performing Teams

    During a Retrospective, the team agrees on three improvement actions. Two Sprints later, none have been started. Which approach best supports the team in turning improvement intentions into change?

    1. Ask the Scrum Master to personally complete the improvement actions
    2. Wait until the next Retrospective and re-agree the same three actions
    3. Limit the team to one or two improvement actions per Sprint and track them like other Sprint work Correct answer.
    4. Replace the Retrospective with a management review of team performance

    Explanation

    Improvement actions compete with delivery unless they are small in number and made visible inside the team's own Sprint work. Limiting the set and tracking it creates follow-through without shifting ownership away from the team.

  110. Question 110Building High-Performing Teams

    A Scrum Master observes that meetings are calm, nobody challenges estimates, and the team agrees quickly with whatever the Product Owner suggests. Which interpretation is most accurate?

    1. The team has reached high performance because it avoids wasted debate
    2. The team demonstrates strong psychological safety because members speak freely
    3. The team shows signs of groupthink, where harmony is being preserved at the cost of critical evaluation Correct answer.
    4. The team is in the storming stage and needs more time to settle

    Explanation

    Silence and quick agreement can indicate groupthink, where the desire for cohesion suppresses dissent and critical scrutiny. High-performing teams show psychological safety through candid challenge, not through the absence of disagreement.

  111. Question 111Planning and Executing Work in a SAFe Enterprise

    In SAFe, which cadence is used by an Agile Release Train (ART) to plan and execute work across teams?

    1. A Program Increment (PI), typically 8–12 weeks long Correct answer.
    2. A quarterly board review of financial results
    3. A sprint, typically two weeks long
    4. A daily stand-up meeting held each morning

    Explanation

    The Program Increment is the ART-level timebox during which multiple teams plan and deliver together, usually spanning four to six iterations plus an Innovation and Planning iteration. Sprints are the team-level cadence nested inside the PI.

  112. Question 112Planning and Executing Work in a SAFe Enterprise

    What is the primary purpose of PI Planning in a SAFe enterprise?

    1. To assign individual performance ratings to each team member
    2. To conduct detailed code reviews across all repositories
    3. To finalize the annual budget for the entire portfolio
    4. To align all teams on a shared mission and produce committed PI objectives Correct answer.

    Explanation

    PI Planning is a face-to-face (or virtual) event where the ART builds a shared understanding of the business context, drafts team and program PI objectives, and identifies risks and dependencies. It is a coordination and alignment event, not a performance-management or budgeting exercise.

  113. Question 113Planning and Executing Work in a SAFe Enterprise

    During PI Planning, what is the role of the Release Train Engineer (RTE)?

    1. Owning the technical architecture across all teams
    2. Defining the product vision and prioritizing the program backlog
    3. Approving each team's individual work assignments
    4. Facilitating the event, managing the agenda, and helping resolve impediments Correct answer.

    Explanation

    The RTE is the ART's chief Scrum Master and servant leader, responsible for facilitating PI Planning, keeping the agenda on track, and helping teams escalate and resolve impediments. Vision and backlog prioritization belong to Product Management, and architecture is owned collaboratively by System Architects.

  114. Question 114Planning and Executing Work in a SAFe Enterprise

    A team finishes PI Planning and has drafted its PI objectives. What should happen to those objectives before they are considered final for the PI?

    1. They should be replaced entirely by the ART's program objectives
    2. They should be locked and never revisited until the next PI
    3. They should be kept confidential from other teams on the train
    4. They should be presented at the management review and assigned business value by business owners Correct answer.

    Explanation

    Team PI objectives are presented during the management review, where business owners assign business value to reflect their relative importance. This feedback loop aligns the teams' plans with business priorities and makes commitments visible across the train.

  115. Question 115Planning and Executing Work in a SAFe Enterprise

    What is the purpose of the Innovation and Planning (IP) iteration within a PI?

    1. To replace PI Planning for the following increment
    2. To conduct only mandatory compliance audits
    3. To deliver the highest-priority customer features under normal iteration pressure
    4. To provide a buffer for estimating and innovation while teams finish remaining work and prepare for the next PI Correct answer.

    Explanation

    The IP iteration sits at the end of each PI and serves as an estimating and innovation buffer, allowing teams to complete unfinished work, run hackathons or explorations, and prepare for the next PI Planning. It is not a normal feature-delivery iteration.

  116. Question 116Planning and Executing Work in a SAFe Enterprise

    In SAFe, what is a program board used for during PI Planning?

    1. Visualizing cross-team dependencies and milestones across iterations Correct answer.
    2. Tracking individual employee vacation schedules
    3. Documenting the code coverage metrics of each team
    4. Recording the financial cost of each user story

    Explanation

    The program board is a visual planning tool that shows features, cross-team dependencies, and significant milestones across the iterations of the PI. It helps teams see where coordination is needed and supports dependency management throughout execution.

  117. Question 117Planning and Executing Work in a SAFe Enterprise

    A team identifies a dependency on another team's work during PI Planning. What is the recommended SAFe practice for handling it?

    1. Visualize the dependency on the program board and agree on a resolution with the other team Correct answer.
    2. Escalate it directly to the CEO for a decision
    3. Ignore it until it becomes a blocker during execution
    4. Convert it into a separate team's PI objective without discussion

    Explanation

    SAFe encourages making dependencies visible, typically on the program board, and having the affected teams agree on how and when the dependency will be resolved. This transparency allows the RTE and teams to manage it proactively rather than reactively.

  118. Question 118Planning and Executing Work in a SAFe Enterprise

    What does a team's PI objective typically include in SAFe?

    1. A business-facing statement of intended outcomes with an assigned business value Correct answer.
    2. A copy of the team's source code repository structure
    3. A list of every individual task with hour estimates
    4. A detailed salary plan for the coming increment

    Explanation

    PI objectives are concise, business-relevant statements describing what the team intends to achieve in the PI, later scored with a business value assigned by business owners. They summarize outcomes rather than enumerating tasks.

  119. Question 119Planning and Executing Work in a SAFe Enterprise

    At the end of a PI, what does the Inspect and Adapt (I&A) event accomplish?

    1. It reviews the PI's results, runs a problem-solving workshop, and identifies improvement actions Correct answer.
    2. It assigns blame to teams that missed their objectives
    3. It replaces the need for iteration retrospectives in the next PI
    4. It re-plans the entire portfolio budget for the next fiscal year

    Explanation

    The Inspect and Adapt event evaluates the current state of the solution, reviews the PI System Demo, and uses a structured problem-solving workshop to identify root causes and improvement actions. The goal is continuous improvement of the ART, not blame.

  120. Question 120Planning and Executing Work in a SAFe Enterprise

    Which metric does SAFe use to measure the percentage of planned PI objectives that were actually achieved?

    1. Cycle time of the deployment pipeline
    2. Defect escape rate
    3. Program Predictability Measure Correct answer.
    4. Velocity per developer

    Explanation

    The Program Predictability Measure compares the business value actually achieved against the business value planned for the PI. It gives the ART a single indicator of how reliably it delivers on its commitments.

  121. Question 121Planning and Executing Work in a SAFe Enterprise

    In SAFe, what is the role of the System Demo?

    1. It replaces the team-level iteration demo entirely
    2. It is a private review attended only by the RTE
    3. It is a financial audit of the ART's spending
    4. It provides an integrated view of the new functionality delivered by all teams in the ART Correct answer.

    Explanation

    The System Demo shows the integrated solution built by all teams on the ART, giving stakeholders a view of the current system state at the end of each iteration or at PI boundaries. It demonstrates cross-team integration rather than isolated team output.

  122. Question 122Planning and Executing Work in a SAFe Enterprise

    A team consistently carries unfinished stories into the next iteration. Which SAFe practice best addresses this during execution?

    1. Ask the RTE to reassign the team's work permanently
    2. Stop holding iteration retrospectives to save time
    3. Use the team's iteration retrospective to inspect the cause and adjust the team's WIP limits or story sizing Correct answer.
    4. Add more stories to the next iteration to compensate

    Explanation

    Iteration retrospectives are the team's mechanism for inspecting how work flowed and identifying adjustments such as limiting work in progress or improving story sizing. Continuous improvement at the team level is a core SAFe execution practice.

  123. Question 123Planning and Executing Work in a SAFe Enterprise

    What is the purpose of the ART Sync event in SAFe?

    1. To coordinate across teams by combining the Scrum of Scrums and PO Sync into one cadence Correct answer.
    2. To finalize the portfolio's strategic themes
    3. To conduct annual performance reviews for the ART
    4. To replace PI Planning for the current increment

    Explanation

    The ART Sync brings together the Scrum of Scrums and the Product Owner Sync so that delivery and content coordination happen in a single, aligned cadence. It helps teams surface dependencies, risks, and progress across the train.

  124. Question 124Planning and Executing Work in a SAFe Enterprise

    Which statement best describes how SAFe treats PI objectives that are not fully met?

    1. They are automatically rolled into the next PI without review
    2. They are hidden from business owners to avoid scrutiny
    3. They are reviewed transparently and the learning informs the next PI's planning Correct answer.
    4. They are deleted so the predictability measure stays high

    Explanation

    SAFe values transparency, so unmet objectives are discussed openly during Inspect and Adapt and the resulting learning feeds the next PI. Concealing or deleting them would undermine the predictability measure and continuous improvement.

  125. Question 125Planning and Executing Work in a SAFe Enterprise

    In SAFe, what is a capacity allocation guideline used for during PI Planning?

    1. It fixes the exact number of story points a team must deliver
    2. It reserves a portion of team capacity for non-feature work such as maintenance and innovation Correct answer.
    3. It determines each team member's annual salary band
    4. It sets the number of teams allowed on the ART

    Explanation

    Capacity allocation guidelines help teams plan how much of their capacity goes to new features versus other work such as defects, technical debt, and innovation. This prevents over-committing to features and preserves room for necessary non-feature work.

  126. Question 126Planning and Executing Work in a SAFe Enterprise

    What is the role of business owners during a PI?

    1. They own the technical design of the system architecture
    2. They assign business value to PI objectives and actively participate in key ART events Correct answer.
    3. They manage the day-to-day tasks of each developer
    4. They write all user stories for the teams

    Explanation

    Business owners are key ART stakeholders who assign business value to PI objectives and stay engaged through events such as PI Planning and the System Demo. They represent the business perspective rather than day-to-day engineering work.

  127. Question 127Planning and Executing Work in a SAFe Enterprise

    A team's PI objective was to reduce checkout latency by 30%, but it achieved only 15% by the end of the PI. How should this be handled in the Inspect and Adapt event?

    1. Remove the objective from the record before the predictability measure is calculated
    2. Report the objective as fully achieved to protect the team's reputation
    3. Blame the individual developer responsible for the latency work
    4. Report the actual result transparently, then use problem-solving to understand the gap and define improvement actions Correct answer.

    Explanation

    I&A relies on honest reporting of actual outcomes followed by structured root-cause problem solving to generate improvement actions. Misreporting or deleting the objective would corrupt the predictability measure and block learning.

  128. Question 128Planning and Executing Work in a SAFe Enterprise

    What is the recommended way to manage cross-team dependencies after PI Planning has ended?

    1. Assign all dependencies to a single team to eliminate coordination
    2. Rely on informal hallway conversations only
    3. Wait until the next PI Planning to address any dependency
    4. Track them continuously through ART Sync and the program board, adjusting as work progresses Correct answer.

    Explanation

    Dependencies are dynamic, so SAFe expects them to be tracked during execution, often via the program board and discussed at ART Sync. Continuous visibility lets the ART resolve issues before they become blockers.

  129. Question 129Planning and Executing Work in a SAFe Enterprise

    In SAFe, what does the term 'collective ownership' of PI objectives imply for the ART?

    1. Each team is solely accountable for its own objectives and ignores the others
    2. The whole train shares accountability for achieving the program objectives, not just individual teams Correct answer.
    3. Only the RTE is accountable for the PI objectives
    4. Business owners are accountable for delivering the features themselves

    Explanation

    Program objectives represent the ART's collective commitments, so the train as a whole shares accountability for achieving them. Teams still own their team objectives, but the program level requires cross-team responsibility.

  130. Question 130Planning and Executing Work in a SAFe Enterprise

    Which event provides the primary opportunity for stakeholders to give feedback on the integrated solution during a PI?

    1. The team retrospective
    2. The System Demo Correct answer.
    3. The iteration planning meeting
    4. The daily stand-up

    Explanation

    The System Demo presents the integrated solution to stakeholders, who then provide feedback that can shape subsequent work. Stand-ups, iteration planning, and retrospectives are team-internal events without that stakeholder feedback focus.

  131. Question 131Planning and Executing Work in a SAFe Enterprise

    A release train wants to improve its ability to forecast delivery. Which practice most directly supports more reliable PI forecasting?

    1. Breaking features into stories sized consistently and tracking velocity across iterations Correct answer.
    2. Eliminating the IP iteration to add more delivery time
    3. Removing the program board to reduce planning overhead
    4. Increasing the number of objectives set without measuring outcomes

    Explanation

    Consistent story sizing and velocity tracking give the ART empirical data to forecast how much work fits in a PI. Removing buffers or planning tools reduces visibility and tends to make forecasts less reliable, not more.

  132. Question 132Planning and Executing Work in a SAFe Enterprise

    What is the SAFe term for the cadence-synchronizing event where Product Owners align on backlog priorities across the ART?

    1. Daily stand-up
    2. Inspect and Adapt
    3. System Demo
    4. PO Sync Correct answer.

    Explanation

    PO Sync is the event where Product Owners and Product Management align on priorities, scope, and progress across teams. It is often combined with the Scrum of Scrums into the ART Sync.

  133. Question 133Planning and Executing Work in a SAFe Enterprise

    How does SAFe recommend handling unplanned work that emerges mid-iteration?

    1. Make it visible, assess its impact on the iteration goal, and decide with the team whether to accept or defer it Correct answer.
    2. Silently add it to the team's backlog without tracking
    3. Always reject it without discussion until the next PI
    4. Always accept it immediately and abandon the iteration goal

    Explanation

    SAFe expects teams to make unplanned work transparent and evaluate it against the iteration goal before deciding to accept or defer it. Blind acceptance or rejection ignores the trade-offs involved, and silent tracking hides the impact on capacity.

  134. Question 134Planning and Executing Work in a SAFe Enterprise

    In SAFe, what is the purpose of the management review during PI Planning?

    1. Architects approve every line of code to be written
    2. The RTE finalizes the annual budget for the ART
    3. Teams present individual performance metrics to HR
    4. Business owners and management review the draft plans and adjust scope or priorities before commitment Correct answer.

    Explanation

    The management review gives business owners and leadership a chance to see the draft plans, resolve conflicts, and adjust priorities before the teams finalize their PI objectives. It is a planning alignment step, not a performance or budgeting review.

  135. Question 135Planning and Executing Work in a SAFe Enterprise

    A newly formed ART is preparing for its first PI Planning. Which preparation step best increases the likelihood of a successful event?

    1. Setting objectives for the teams without their input
    2. Communicating the business context and drafting a prioritized program backlog in advance Correct answer.
    3. Skipping the draft plan so teams can improvise on the day
    4. Inviting only the RTE and Product Management to attend

    Explanation

    Effective PI Planning depends on advance preparation such as sharing the business context and having a prioritized program backlog ready for teams to plan against. Broad attendance and team-driven drafting are also essential to producing a realistic, committed plan.

  136. Question 136Planning and Executing Work in a SAFe Enterprise

    During PI Planning, what is the primary purpose of the draft plan review that each team presents to the rest of the ART?

    1. To rank each team's stories by business value so the Release Train Engineer can allocate capacity
    2. To obtain formal budget approval from the Lean Portfolio Management group for the next increment
    3. To expose cross-team dependencies and risks so they can be visualized and addressed before the plan is finalized Correct answer.
    4. To let business owners assign each team a confidence vote score before the management review

    Explanation

    The draft plan review exists so teams surface dependencies, assumptions, and risks that only become visible when plans are shared across the ART. Business owners then use that information to set the program board and confidence vote. The review is about integration and alignment, not funding or story-level prioritization.

  137. Question 137Planning and Executing Work in a SAFe Enterprise

    A team has finished its iteration goals and has spare capacity late in the iteration. Which action best aligns with SAFe's guidance for the team?

    1. Wait until the next iteration so velocity remains predictable for the ART
    2. Start work on a lower-priority item that requires skills the team wants to develop
    3. Ask the Release Train Engineer to reassign the team's remaining capacity to another team
    4. Pull the next highest-priority backlog item that fits within remaining capacity and the team's definition of done Correct answer.

    Explanation

    SAFe keeps work pulled from a prioritized backlog, so spare capacity is filled by pulling the next item that fits, not by idling or cherry-picking. This preserves flow and keeps the team aligned with the ART's priorities. Development interests and cross-team reassignment do not override backlog order.

  138. Question 138Planning and Executing Work in a SAFe Enterprise

    What distinguishes a team's PI objectives from its iteration goals in SAFe?

    1. PI objectives summarize the business and technical outcomes a team intends to achieve across the whole PI, while iteration goals describe outcomes for a single iteration Correct answer.
    2. PI objectives are written only by business owners, while iteration goals are written by the Product Owner alone
    3. PI objectives are recorded only in the team backlog, while iteration goals appear on the program board
    4. PI objectives are mandatory commitments with fixed dates, while iteration goals are optional stretch items

    Explanation

    PI objectives describe the outcomes a team aims to deliver over an entire Program Increment and are reviewed with business owners, who assign business value. Iteration goals are shorter-horizon commitments for a single iteration. Keeping these horizons distinct is central to planning and executing work in an ART.

  139. Question 139Planning and Executing Work in a SAFe Enterprise

    Which statement accurately describes the role of the Continuous Delivery Pipeline in executing work during a PI?

    1. It is a reporting dashboard that shows planned versus actual PI objectives
    2. It provides the automated path from code commit through build, test, and deployment that lets the ART release value on demand Correct answer.
    3. It is a governance board that approves which features may enter the program backlog
    4. It replaces the need for iteration boundaries by allowing teams to plan continuously

    Explanation

    The Continuous Delivery Pipeline is the technical and automated flow that moves changes from commit to release, enabling on-demand delivery and fast feedback. It supports, but does not replace, the cadence of iterations and PIs. Governance and reporting are handled by other mechanisms.

  140. Question 140Planning and Executing Work in a SAFe Enterprise

    Midway through an iteration, a team discovers that a story it committed to is far larger than estimated. What is the most SAFe-aligned response?

    1. Extend the iteration by a few days so the original story can be completed as written
    2. Silently carry the story forward and adjust the iteration goal at the end of the iteration
    3. Split the story, keep the highest-value slice in the iteration, and return the remainder to the backlog for reprioritization Correct answer.
    4. Ask another team to take over the story so the team's commitment is preserved

    Explanation

    SAFe favors splitting large stories and delivering the most valuable slice within the iteration, returning the rest to the backlog for the Product Owner to reprioritize. This preserves flow and keeps commitments realistic. Changing iteration length or hiding slippage undermines cadence and transparency.

  141. Question 141Planning and Executing Work in a SAFe Enterprise

    A team's planned work depends on an API another team will deliver in the same iteration. Which practice best supports executing this work successfully?

    1. Define the interface contract early and agree on a delivery date so both teams can integrate within the iteration Correct answer.
    2. Defer the dependent work to the next PI so the teams do not need to coordinate
    3. Escalate to the Release Train Engineer to force one team to deliver first
    4. Remove the dependency from the plan and let each team work independently

    Explanation

    When dependent work falls in the same iteration, agreeing on the interface contract and timing early lets both teams integrate and test within the timebox. SAFe treats dependencies as something to visualize, communicate, and resolve continuously rather than avoid. Deferral or top-down forcing usually creates delay and rework.

  142. Question 142Planning and Executing Work in a SAFe Enterprise

    How does SAFe recommend that a team handle a newly discovered enabler that is required before a planned feature can be delivered?

    1. Convert the feature into an uncommitted objective and drop the enabler
    2. Deliver the feature first and retrofit the enabler after the PI closes
    3. Make the enabler explicit in the team backlog and sequence it ahead of the dependent feature, adjusting PI objectives if needed Correct answer.
    4. Record the enabler only in architectural documentation so the plan stays unchanged

    Explanation

    Enablers are backlog items in their own right and should be made visible and sequenced to support the features that depend on them. If the discovery changes what the team can achieve, PI objectives are updated transparently with business owners. Retrofitting or hiding enablers creates technical debt and misleads the ART.

  143. Question 143Planning and Executing Work in a SAFe Enterprise

    What is the main purpose of the Iteration Review in the execution of work within a PI?

    1. To assign business value to the team's PI objectives
    2. To conduct root-cause analysis of the PI's systemic problems
    3. To demonstrate the working increment to stakeholders and gather feedback that informs the next iteration's planning Correct answer.
    4. To finalize the ART's budget for the coming increment

    Explanation

    The Iteration Review is where the team shows the working, tested increment and collects stakeholder feedback that shapes the next iteration. It is a team-level inspect-and-adapt point that keeps delivery aligned with customer needs. Business value assignment and systemic problem solving happen elsewhere.

  144. Question 144Planning and Executing Work in a SAFe Enterprise

    A Product Owner wants to improve the flow of work into the team. Which action most directly supports this goal in SAFe?

    1. Increase the number of work-in-progress items so the team stays busy
    2. Delay refinement until iteration planning so the team can decide everything at once
    3. Refine backlog items just in time so they meet the team's definition of ready before iteration planning Correct answer.
    4. Add more items to the current iteration as soon as capacity appears

    Explanation

    Just-in-time backlog refinement keeps items ready without over-investing in specification, which smooths the flow of work into planning. Excessive work in progress and last-minute refinement both create churn and reduce predictability. Flow improves when incoming work is prepared to a consistent standard.

  145. Question 145Planning and Executing Work in a SAFe Enterprise

    During the PI, the ART's planned features are at risk because one component team is consistently overloaded. Which response best reflects SAFe's approach to executing the plan?

    1. Wait until the Inspect and Adapt event to raise the issue
    2. Reduce the scope of other teams' PI objectives without informing business owners
    3. Quietly extend the overloaded team's iteration to absorb the extra work
    4. Visualize the overload, rebalance work across teams where feasible, and update the plan transparently with the RTE and Product Management Correct answer.

    Explanation

    SAFe expects the ART to make work visible, rebalance where possible, and adjust the plan openly with the RTE and Product Management so dependencies and objectives stay coherent. Silent local fixes hide risk from the people who need to make trade-offs. Surfacing problems only at the end of the PI forfeits the chance to adapt.

  146. Question 146Planning and Executing Work in a SAFe Enterprise

    Which pair of events best supports continuous improvement of how work is planned and executed across the ART?

    1. The ART Sync and the scrum of scrums, which together report status to portfolio leadership
    2. The daily stand-up and the iteration planning meeting, which together set the team's daily and iteration commitments
    3. The management review and the draft plan review, which together approve the PI plan
    4. The Inspect and Adapt event and the system demo, which together surface outcomes and systemic problems for action Correct answer.

    Explanation

    The system demo shows the integrated outcome, and the Inspect and Adapt uses that evidence to identify systemic problems and create improvement backlog items. Together they close the loop between delivering value and improving how the ART works. The other pairings serve planning or coordination rather than improvement.

  147. Question 147Planning and Executing Work in a SAFe Enterprise

    A team's PI objective reads: 'Complete the payments refactor.' Which revision best aligns with SAFe guidance for writing PI objectives?

    1. Reduce payment authorization latency by 20 percent for the top three merchants by the end of the PI Correct answer.
    2. Support the payments initiative and related technical improvements
    3. Work on the payments refactor as much as possible during the PI
    4. Refactor the payments module using the team's preferred design patterns

    Explanation

    Good PI objectives state a measurable outcome and its value so business owners can assign business value and the ART can assess achievement. Activity statements or vague intentions cannot be evaluated at the end of the PI. Outcome orientation also helps the team make trade-offs during execution.

  148. Question 148Planning and Executing Work in a SAFe Enterprise

    An ART has completed several PIs with high confidence votes at planning but frequent missed objectives. Which analysis best identifies the root cause to address?

    1. The confidence vote may reflect optimism rather than evidence, so the ART should examine whether risks and dependencies are surfaced and whether objectives are truly achievable Correct answer.
    2. The teams should stop using uncommitted objectives because they dilute accountability
    3. The business owners are assigning business value incorrectly, so their scoring method should be replaced
    4. The ART should shorten the PI so there is less time for plans to go wrong

    Explanation

    A confidence vote is only meaningful when it reflects real assessment of risks, dependencies, and capacity. Recurring misses despite high confidence point to weak risk surfacing or unrealistic objectives rather than to the business value method. SAFe treats the vote as a signal to investigate, not a guarantee.

  149. Question 149Planning and Executing Work in a SAFe Enterprise

    A feature spans three teams and requires coordinated integration before it can be demonstrated. How should the ART plan and execute this work?

    1. Assign the whole feature to one team to avoid coordination overhead
    2. Break the feature into team-sized stories, plan the integration points explicitly, and verify the integrated result in a system demo Correct answer.
    3. Plan each team's portion independently and integrate only at the end of the PI
    4. Defer the feature to a later PI until a single team can own it end to end

    Explanation

    SAFe splits features into stories that teams can deliver within an iteration, while making integration points explicit so the combined result can be verified frequently. Demonstrating the integrated feature provides fast feedback on whether the pieces actually work together. Avoiding coordination or deferring integration until the end increases risk.

  150. Question 150Planning and Executing Work in a SAFe Enterprise

    Which situation indicates that an ART should revisit its definition of done rather than simply push teams to work faster?

    1. Teams finish their stories on time but report low morale during retrospectives
    2. The RTE spends too much time facilitating the ART Sync
    3. Business owners assign lower business value than teams expected
    4. Integrated features repeatedly fail system-level testing because each team's local definition of done omits end-to-end verification Correct answer.

    Explanation

    When locally complete work fails at the system level, the definition of done is too narrow to guarantee integrable, releasable increments. SAFe expects the definition of done to include the verification needed for the ART to demonstrate working solutions. Pushing for speed would only hide the quality gap.

  151. Question 151Leading in a SAFe Enterprise

    In SAFe, which role holds ultimate accountability for the economic outcomes of a Lean Portfolio, including strategy and investment funding decisions?

    1. The Lean Portfolio Management group Correct answer.
    2. The Release Train Engineer
    3. The System Architect
    4. The Product Owner

    Explanation

    Lean Portfolio Management is the group that owns portfolio strategy, investment funding, and portfolio operations, and it is accountable for the economic results of the portfolio as a whole. Individual delivery roles such as the RTE or Product Owner operate within the value streams that LPM funds and governs.

  152. Question 152Leading in a SAFe Enterprise

    Which SAFe event is the primary mechanism where a Lean Portfolio's strategy and investment decisions are adjusted based on actual value delivery data?

    1. Portfolio Sync Correct answer.
    2. System Demo
    3. Daily Stand-up
    4. Sprint Retrospective

    Explanation

    Portfolio Sync is the cadence-based forum where LPM and value stream stakeholders review progress against the portfolio Kanban, Epic outcomes, and Lean Budgets, then adjust funding and priorities. It closes the loop between strategy and execution on a recurring rhythm.

  153. Question 153Leading in a SAFe Enterprise

    A SAFe leader wants to shift from output-based to outcome-based governance. Which practice best reflects this shift at the portfolio level?

    1. Requiring weekly status reports from every Scrum Master
    2. Approving each team's iteration plan
    3. Tracking the number of features delivered per PI
    4. Measuring progress against defined business outcomes and Epic hypotheses Correct answer.

    Explanation

    Outcome-based governance evaluates whether delivered work moved the intended business measures, often through Epic hypothesis statements and leading indicators. Counting features or approving plans is output and activity control, which SAFe explicitly moves away from.

  154. Question 154Leading in a SAFe Enterprise

    In a SAFe Enterprise, what is the primary purpose of the Lean Portfolio Management trio of responsibilities?

    1. To run the ART's daily execution and remove team impediments
    2. To align strategy with execution through strategy and investment funding, Agile portfolio operations, and Lean governance Correct answer.
    3. To own the solution architecture and nonfunctional requirements across the portfolio
    4. To manage the team backlog and define acceptance criteria for stories

    Explanation

    The LPM function is described as three collaborating responsibilities: strategy and investment funding, Agile portfolio operations, and Lean governance. Together they connect enterprise strategy to the execution happening in ARTs and value streams.

  155. Question 155Leading in a SAFe Enterprise

    A leader is told that in SAFe, decentralized decision-making is preferred. What does this principle actually require of leaders?

    1. Leaders stop making any decisions and let teams decide everything
    2. Leaders set clear strategic intent and boundaries, then push decisions to the lowest responsible level Correct answer.
    3. Leaders delegate only routine decisions while retaining all architectural choices
    4. Leaders centralize decisions to avoid inconsistency across ARTs

    Explanation

    Decentralized decision-making works only when leaders articulate intent, constraints, and guardrails so teams can decide locally with context. It is not abdication; it is deliberate alignment of strategy combined with authority closest to the information.

  156. Question 156Leading in a SAFe Enterprise

    Which statement best describes the role of the Enterprise Architect in a SAFe Enterprise?

    1. They act as the primary customer proxy for the Solution Train
    2. They own the team backlog and prioritize stories each iteration
    3. They collaborate across ARTs to evolve the portfolio-level architecture and intentional architecture Correct answer.
    4. They facilitate the PI Planning event for a single ART

    Explanation

    Enterprise Architects work above the ART level, aligning architecture across value streams and maintaining intentional architecture and architectural runway at portfolio scale. They collaborate with System Architects rather than owning team-level work.

  157. Question 157Leading in a SAFe Enterprise

    A SAFe leader notices that Business Owners are not engaged in PI Planning. What is the most likely consequence for the ART?

    1. The ART may plan work that lacks alignment with business priorities and funding intent Correct answer.
    2. The Product Owner will lose content authority over the backlog
    3. The ART will produce more innovative solutions because teams are unconstrained
    4. The System Demo will be canceled automatically

    Explanation

    Business Owners are accountable for business outcomes and participate in PI Planning to confirm the business context and approve the plan. Without them, the ART risks building work misaligned with strategic priorities and budget intent.

  158. Question 158Leading in a SAFe Enterprise

    Which metric is most consistent with SAFe's guidance for measuring portfolio performance rather than local activity?

    1. Count of meetings attended by each Business Owner
    2. Percentage of planned features delivered on the original date
    3. Number of story points completed by each team
    4. Flow of value through the portfolio Kanban and realization of Epic benefits Correct answer.

    Explanation

    SAFe emphasizes measuring flow and business outcomes, including how Epics move through the portfolio Kanban and whether they deliver the hypothesized benefits. Local output and plan-conformance metrics encourage the wrong behaviors.

  159. Question 159Leading in a SAFe Enterprise

    What distinguishes a SAFe Lean Budget Guardrail from a traditional annual project budget?

    1. Guardrails constrain spending within a value stream while allowing decentralized investment decisions Correct answer.
    2. Guardrails eliminate the need for any financial oversight
    3. Guardrails are set per team and reviewed every iteration
    4. Guardrails are only applied to Epics that fail the portfolio Kanban

    Explanation

    Lean Budget Guardrails define spending boundaries and policies for a value stream so that funding can flow without per-project approvals. They preserve financial control while enabling decentralized, faster investment decisions within those limits.

  160. Question 160Leading in a SAFe Enterprise

    Which behavior most clearly demonstrates a SAFe leader acting as a servant leader rather than a traditional manager?

    1. Conducting individual performance reviews after each PI
    2. Approving all design decisions before implementation
    3. Removing impediments and developing people so teams can self-organize Correct answer.
    4. Assigning each team member their daily tasks

    Explanation

    Servant leadership in SAFe focuses on growing people, removing impediments, and creating an environment where teams self-organize and take ownership. Directing tasks and gatekeeping decisions reflects command-and-control management.

  161. Question 161Leading in a SAFe Enterprise

    An ART consistently misses its PI objectives. As a SAFe leader, which action best reflects the principle of applying systems thinking?

    1. Add more detailed status reporting requirements to increase visibility
    2. Examine the whole value stream, including dependencies, WIP limits, and cross-team flow, to find systemic causes Correct answer.
    3. Increase the number of features planned in the next PI to motivate the teams
    4. Hold individual teams accountable and replace underperforming Scrum Masters

    Explanation

    Systems thinking asks leaders to optimize the whole value stream rather than blame parts, so they inspect dependencies, WIP, and flow across teams. Blaming individuals or adding reporting overhead treats symptoms and can worsen the system.

  162. Question 162Leading in a SAFe Enterprise

    In SAFe, what is the purpose of the Portfolio Kanban?

    1. To schedule the ART's daily stand-ups
    2. To record Business Owner approvals of team PI objectives
    3. To visualize and manage the flow of Epics from identification through implementation and completion Correct answer.
    4. To track individual team stories across a single iteration

    Explanation

    The Portfolio Kanban makes the flow of portfolio Epics visible, with states such as funnel, reviewing, analyzing, portfolio backlog, and implementing. It supports WIP limits and economic prioritization of the largest investments.

  163. Question 163Leading in a SAFe Enterprise

    A leader wants to improve alignment between strategy and execution across multiple ARTs. Which SAFe mechanism is designed specifically for coordinating multiple ARTs that build a large solution?

    1. The Solution Train with its Solution Train Engineer Correct answer.
    2. The team retrospective
    3. The Scrum of Scrums within a single team
    4. The Product Owner sync within one ART

    Explanation

    When multiple ARTs must collaborate on a single large solution, SAFe introduces the Solution Train, coordinated by the Solution Train Engineer and supported by Solution Management and Solution Architects. It provides the coordination layer above individual ARTs.

  164. Question 164Leading in a SAFe Enterprise

    Which statement best captures how SAFe treats innovation during portfolio planning?

    1. Innovation is funded only after an Epic reaches the implementing state
    2. A portion of capacity and funding is reserved for innovation and exploration through the portfolio Kanban funnel Correct answer.
    3. Innovation work is excluded from Lean Budgets
    4. Innovation is owned exclusively by the Enterprise Architect

    Explanation

    SAFe encourages allocating capacity for innovation and exploring new ideas through the funnel and reviewing states of the portfolio Kanban. This keeps a pipeline of potential investments while the bulk of funding supports current value streams.

  165. Question 165Leading in a SAFe Enterprise

    A SAFe leader is reviewing an Epic hypothesis statement. Which element is essential for enabling outcome-based governance?

    1. A fixed delivery date that cannot change
    2. A list of every team member assigned to the work
    3. A detailed Gantt schedule of every task
    4. A leading indicator and expected business benefit used to evaluate the hypothesis Correct answer.

    Explanation

    Epic hypothesis statements define the intended business outcome and a measurable leading indicator so the portfolio can evaluate whether the investment is delivering value. This supports the persistent, evidence-based decision-making that Lean governance requires.

  166. Question 166Leading in a SAFe Enterprise

    Which responsibility belongs to Agile Portfolio Operations within the LPM function?

    1. Setting individual compensation for team members
    2. Defining the enterprise's financial accounting standards
    3. Coordinating and supporting the ART execution and fostering continuous improvement across value streams Correct answer.
    4. Writing user stories for the ART backlog

    Explanation

    Agile Portfolio Operations supports execution across ARTs, coordinates value stream performance, and promotes operational excellence and continuous improvement. Financial accounting standards and compensation are outside its scope.

  167. Question 167Leading in a SAFe Enterprise

    What is the primary leadership intent behind organizing development around value streams rather than around functional silos?

    1. To make budgeting easier by aligning to departments
    2. To centralize decision-making in a single program office
    3. To reduce headcount in each department
    4. To optimize end-to-end flow of value to the customer by removing handoffs and dependencies Correct answer.

    Explanation

    Value streams organize people and work around the flow of value to the customer, reducing handoffs, queues, and cross-silo dependencies. This is a systems-level optimization rather than a departmental cost exercise.

  168. Question 168Leading in a SAFe Enterprise

    In SAFe, which group approves the ART's PI objectives at the end of PI Planning?

    1. The Enterprise Architects
    2. The Business Owners Correct answer.
    3. The Scrum Masters
    4. The System Team

    Explanation

    Business Owners review and approve the ART's PI objectives during PI Planning, confirming business value and alignment with strategy. Their approval connects the plan to the funding and outcomes they are accountable for.

  169. Question 169Leading in a SAFe Enterprise

    A portfolio leader wants faster decisions on new Epics. Which change most directly supports this while preserving governance?

    1. Removing all analysis states from the portfolio Kanban
    2. Adding a monthly executive review before any Epic enters the funnel
    3. Applying WIP limits and clear economic prioritization criteria in the Portfolio Kanban Correct answer.
    4. Requiring every Epic to be approved by all Business Owners

    Explanation

    WIP limits plus explicit economic prioritization criteria let the portfolio make faster, consistent decisions about which Epics to advance. This keeps governance lightweight while maintaining discipline over investment choices.

  170. Question 170Leading in a SAFe Enterprise

    Which statement reflects SAFe's guidance on leadership and the creation of a safe environment for learning?

    1. Leaders should hide problems from teams to maintain morale
    2. Leaders should punish failed experiments to discourage waste
    3. Leaders should treat failures in experiments as learning opportunities and encourage transparency Correct answer.
    4. Leaders should require teams to report only successful outcomes

    Explanation

    SAFe leaders foster a culture where problems surface early and experiments can fail safely, enabling fast learning and improvement. Punishing failure or hiding problems suppresses the transparency that continuous improvement depends on.

  171. Question 171Leading in a SAFe Enterprise

    How does SAFe's Lean Governance responsibility differ from traditional stage-gate governance?

    1. It removes the need for any portfolio-level decision-making
    2. It requires a formal gate review before each iteration
    3. It uses lightweight, continuous, evidence-based checks such as portfolio syncs and metrics instead of phase gates Correct answer.
    4. It replaces all financial oversight with team self-reporting

    Explanation

    Lean Governance relies on continuous, evidence-based oversight through portfolio syncs, flow metrics, and guardrails rather than infrequent phase gates. This preserves accountability while supporting faster, decentralized investment decisions.

  172. Question 172Leading in a SAFe Enterprise

    A SAFe leader observes that teams are overloaded and flow has stalled. Which action best aligns with the principle of limiting work in process?

    1. Start more work so that some of it finishes sooner
    2. Add more parallel initiatives to keep everyone busy
    3. Reduce WIP, finish current work first, and make the bottleneck visible Correct answer.
    4. Extend working hours to increase throughput

    Explanation

    Limiting WIP reduces context switching and queues, allowing work to finish and flow to improve. Starting more work or extending hours increases load on the system and typically worsens the bottleneck.

  173. Question 173Leading in a SAFe Enterprise

    Which SAFe role is primarily responsible for defining and communicating the ART's vision and roadmap to align teams with customer needs?

    1. The Scrum Master
    2. The Product Manager Correct answer.
    3. The System Team
    4. The Release Train Engineer

    Explanation

    The Product Manager owns the ART backlog and communicates the vision and roadmap so teams understand customer needs and priorities. The RTE facilitates execution, while Scrum Masters and the System Team serve other functions.

  174. Question 174Leading in a SAFe Enterprise

    A Business Owner wants to influence priorities during PI Planning without micromanaging teams. Which approach best fits SAFe?

    1. Provide the business context, set clear objectives, and negotiate with teams on the draft plan Correct answer.
    2. Override the Product Owner's backlog order during breakout sessions
    3. Dictate each team's stories and acceptance criteria
    4. Assign tasks to individual developers during planning

    Explanation

    Business Owners contribute business context and negotiate PI objectives with teams, preserving team ownership of the how. Dictating stories or tasks crosses into team-level decision-making that SAFe assigns elsewhere.

  175. Question 175Leading in a SAFe Enterprise

    An enterprise is adopting SAFe and its leaders ask how to measure whether the transformation is improving flow. Which set of measures best aligns with SAFe guidance?

    1. Flow metrics such as lead time, throughput, and flow distribution across the portfolio Correct answer.
    2. Percentage of teams using the same estimation technique
    3. Number of certified practitioners and training hours completed
    4. Count of SAFe events held each quarter

    Explanation

    SAFe recommends flow-based measures such as lead time, throughput, and flow distribution to assess how value moves through the system. Training counts and event attendance measure activity, not the flow improvement the transformation aims for.

  176. Question 176Leading in a SAFe Enterprise

    A SAFe leader is establishing the guardrails that will govern spending across a portfolio. Which statement best describes the primary purpose of Lean Budget Guardrails?

    1. To ensure that every Epic receives an equal share of the portfolio budget regardless of value
    2. To constrain spending to the minimum necessary while enabling decentralized decisions within agreed boundaries Correct answer.
    3. To require executive approval for every team-level spending decision above a small threshold
    4. To replace all participatory budgeting with a single annual allocation approved by finance

    Explanation

    Lean Budget Guardrails are the policies and constraints that allow funding decisions to be decentralized while keeping spending within the portfolio's agreed capacity. They define boundaries such as capacity allocation and spending limits rather than prescribing every expenditure, so leaders can steer without micromanaging.

  177. Question 177Leading in a SAFe Enterprise

    During a PI System Demo, a SAFe leader sees that several teams have integrated their work but the overall solution does not yet meet the intended business outcome. Which action best reflects the leader's role in fostering relentless improvement?

    1. Direct the teams to add more features in the next Iteration to close the gap quickly
    2. Facilitate a problem-solving workshop to identify root causes and adjust the plan based on findings Correct answer.
    3. Reassign the teams to different value streams to improve motivation and accountability
    4. Escalate the shortfall to the portfolio and request additional funding for more teams

    Explanation

    Relentless improvement calls for leaders to help teams inspect outcomes and address root causes rather than simply adding scope or escalating. A problem-solving workshop uses the demo evidence to adjust the plan and improve the system, which is consistent with SAFe's emphasis on learning and continuous improvement.

  178. Question 178Leading in a SAFe Enterprise

    A SAFe leader wants to ensure that the portfolio is investing in the right things and that spending is aligned with strategy. Which two elements together best represent the core of Lean Portfolio Management?

    1. Detailed project plans and annual budgeting cycles
    2. Functional silos and stage-gate approvals
    3. Strategy and investment funding, and Agile portfolio operations Correct answer.
    4. Centralized decision-making and individual performance reviews

    Explanation

    Lean Portfolio Management consists of three collaborating areas: Strategy and Investment Funding, Agile Portfolio Operations, and Lean Governance. The pairing of strategy and investment funding with Agile portfolio operations captures the core alignment of investment with strategy and the operational support for value delivery.

  179. Question 179Leading in a SAFe Enterprise

    A SAFe leader observes that two ARTs are duplicating effort on similar capabilities because they are not sharing architectural information. Which action best demonstrates the leader applying the principle of decentralizing decision-making?

    1. Establish clear architectural guardrails and empower the ARTs to make local decisions within them Correct answer.
    2. Instruct the ARTs to stop all work until a single centralized architecture team defines the solution
    3. Mandate that one ART lead make all architectural decisions for both ARTs to ensure consistency
    4. Require both ARTs to submit all architectural decisions to the enterprise architecture board for approval

    Explanation

    Decentralizing decision-making means providing clear guardrails and then trusting those closest to the work to decide within them. Architectural guardrails allow ARTs to make local choices that avoid duplication while preserving alignment, rather than centralizing every decision.

  180. Question 180Leading in a SAFe Enterprise

    A SAFe leader is assessing whether the enterprise is ready to transition from project-based funding to Lean Portfolio Management. Which condition is most critical for enabling that transition?

    1. A culture that tolerates failure and supports decentralized decision-making with clear guardrails Correct answer.
    2. A performance management system that ranks individuals against each other
    3. A detailed annual budget that specifies spending for every team and Iteration
    4. A centralized PMO that approves all team-level work assignments

    Explanation

    Lean Portfolio Management depends on a culture of learning and decentralized decision-making within guardrails, because funding is directed at value streams and adjusted based on outcomes. Without psychological safety and clear boundaries, the shift from project funding to Lean funding cannot take hold.

  181. Question 181Practicing SAFe

    In SAFe, which cadence does an Agile Release Train use to deliver value, and what is the standard duration of that cadence?

    1. A Program Increment of 8 to 12 weeks, composed of development iterations Correct answer.
    2. A Sprint of 2 weeks, aligned to the team's own planning cycle
    3. A Release Train cadence of 6 months, aligned to the annual portfolio cycle
    4. A daily sync of 15 minutes, followed by a monthly system demo

    Explanation

    An Agile Release Train delivers value in Program Increments, which are typically 8 to 12 weeks long and contain several development iterations plus a final Innovation and Planning iteration. This PI cadence provides the fixed timebox within which the train plans, executes, and demonstrates value.

  182. Question 182Practicing SAFe

    During PI Planning, what is the primary purpose of the management review and problem-solving session that occurs on the second day?

    1. To approve each team's committed objectives before they are presented
    2. To finalize the budget for the next Program Increment
    3. To assign individual work items to engineers across the train
    4. To resolve cross-team dependencies and address issues that block the train's plan Correct answer.

    Explanation

    The management review and problem-solving session lets leadership and the train address the risks, dependencies, and impediments surfaced by the draft plans. Its focus is removing obstacles and adjusting scope so the final plan is realistic, not approving or assigning work.

  183. Question 183Practicing SAFe

    A Scrum Master on an ART notices that two teams have built conflicting APIs and only discover this at the system demo. Which SAFe practice most directly prevents this outcome?

    1. Making dependencies visible during PI Planning and tracking them through the ART sync Correct answer.
    2. Replacing the system demo with written status reports
    3. Adding a second system demo each PI
    4. Moving the affected teams onto separate release trains

    Explanation

    SAFe addresses cross-team integration risk by making dependencies explicit during PI Planning and continuously tracking them in the ART sync, so conflicts surface early. The system demo then verifies integrated value rather than discovering mismatches for the first time.

  184. Question 184Practicing SAFe

    Which statement best describes the role of the Release Train Engineer in SAFe?

    1. The RTE manages the engineering practices and code quality standards
    2. The RTE approves all team-level Sprint commitments
    3. The RTE serves as the ART's chief Scrum Master and servant leader, facilitating ART events and removing impediments Correct answer.
    4. The RTE owns the product vision and prioritizes the program backlog

    Explanation

    The Release Train Engineer is the ART's servant leader and chief Scrum Master, facilitating PI Planning, the ART sync, and other train events while coaching and removing impediments. Vision and backlog prioritization belong to product management.

  185. Question 185Practicing SAFe

    A team finishes its committed stories mid-iteration and has capacity remaining. According to SAFe, what should the team do with that slack?

    1. Start work on the following iteration's stories to get ahead
    2. Idle until the next Sprint to protect the iteration boundary
    3. Pull the next highest-priority items from the program backlog to keep delivering value Correct answer.
    4. Reduce the team's velocity baseline for the next PI

    Explanation

    SAFe encourages teams with remaining capacity to pull additional high-priority items from the program backlog rather than idle, keeping flow continuous. This preserves the iteration boundary while still delivering value.

  186. Question 186Practicing SAFe

    What is the primary purpose of the Innovation and Planning iteration at the end of a Program Increment?

    1. To conduct individual performance reviews for team members
    2. To provide a buffer for estimating and planning the next PI while allowing innovation and learning Correct answer.
    3. To run the system demo and inspect the integrated solution
    4. To deliver the highest-priority features committed for the PI

    Explanation

    The Innovation and Planning iteration is a fixed buffer at the end of the PI used for PI Planning, estimation, and dedicated innovation or learning time. It absorbs variability in delivery estimates and protects the next PI's planning.

  187. Question 187Practicing SAFe

    In SAFe, which event is the primary mechanism for aligning the ART on progress and surfacing impediments between PI Plannings?

    1. The portfolio kanban review
    2. The ART sync, which combines the Scrum of Scrums and the PO sync Correct answer.
    3. The daily stand-up of each individual team
    4. The inspect and adapt workshop

    Explanation

    The ART sync brings together the Scrum of Scrums and the Product Owner sync to coordinate delivery, manage dependencies, and address impediments across the train. It is the recurring alignment event between PI Plannings.

  188. Question 188Practicing SAFe

    A Product Owner wants to change the content of an iteration that is already in progress because a stakeholder requested a new feature. What does SAFe recommend?

    1. Extend the iteration by one week to accommodate the new work
    2. Add the feature immediately to protect stakeholder satisfaction
    3. Negotiate scope with the team while preserving the iteration goal and timebox Correct answer.
    4. Cancel the iteration and replan from scratch

    Explanation

    SAFe preserves the iteration goal and timebox while allowing scope to be negotiated with the team, which reflects the agile principle of responding to change within a stable cadence. Uncontrolled mid-iteration changes erode the predictability the train depends on.

  189. Question 189Practicing SAFe

    Which artifact in SAFe holds the features and enablers that the ART will implement, and who primarily owns its content?

    1. The portfolio backlog, owned by the Enterprise Architect
    2. The team backlog, owned by the Scrum Master
    3. The program backlog, owned by the Product Manager Correct answer.
    4. The solution backlog, owned by the Release Train Engineer

    Explanation

    The program backlog contains the features and enablers for the ART, and the Product Manager is accountable for its content and prioritization. Teams then decompose those items into their own team backlogs.

  190. Question 190Practicing SAFe

    A team consistently over-commits during PI Planning, causing carryover into the Innovation and Planning iteration. Which action best reflects SAFe guidance for improving this?

    1. Have the RTE approve smaller commitments on the team's behalf
    2. Reduce the number of iterations per PI to lower pressure
    3. Use the inspect and adapt workshop to analyze the root cause and adjust planning assumptions Correct answer.
    4. Increase the team's velocity target so the team stretches further

    Explanation

    SAFe treats the inspect and adapt workshop as the structured moment to examine why commitments were missed and to adjust the team's planning assumptions. This supports continuous improvement grounded in evidence rather than imposed targets.

  191. Question 191Practicing SAFe

    What distinguishes a feature from an epic in SAFe?

    1. A feature is a service delivered by an ART within a PI, while an epic is a larger initiative spanning ARTs and PIs Correct answer.
    2. A feature is a team-level story, while an epic is a program-level enabler
    3. A feature is used only for enablers, while an epic is used only for business capabilities
    4. A feature is portfolio-level and spans multiple PIs, while an epic fits within a single iteration

    Explanation

    Features are services that deliver value to the customer and are sized to be completed by an ART within a PI, while epics are larger initiatives that often span multiple ARTs and PIs. The portfolio kanban manages epics through their lifecycle.

  192. Question 192Practicing SAFe

    During a system demo, a team shows functionality that works only in its own environment and is not integrated with other teams' work. Which SAFe principle does this most directly violate?

    1. Apply cadence and synchronize with cross-domain planning Correct answer.
    2. Assume variability and preserve options
    3. Decentralize decision-making
    4. There is no correct answer among these

    Explanation

    The system demo exists to inspect a fully integrated increment, which requires the cadence and synchronization that keep teams aligned on a shared solution. Demonstrating isolated work defeats the integrated-increment purpose of the event.

  193. Question 193Practicing SAFe

    Which statement accurately describes how SAFe treats Built-in Quality at the team level?

    1. Built-in Quality applies only to hardware components
    2. Quality checks are deferred to the system demo to avoid slowing iteration flow
    3. Teams apply practices such as continuous integration and test automation so quality is built into each increment Correct answer.
    4. Quality is verified primarily by a separate QA team at the end of the PI

    Explanation

    Built-in Quality means teams adopt practices like continuous integration, test automation, and refactoring so each increment meets quality standards as it is created. Quality is owned by the teams rather than inspected in at the end.

  194. Question 194Practicing SAFe

    A Solution Train coordinates several ARTs building a large system. Which role is accountable for defining and prioritizing the solution backlog?

    1. The Solution Product Manager, supported by the Solution Architect Correct answer.
    2. The Release Train Engineer of the largest ART
    3. The System Team lead
    4. The Solution Train Engineer

    Explanation

    In a Solution Train, the Solution Product Manager is accountable for the solution backlog's content and priority, working with the Solution Architect on technical direction. The Solution Train Engineer facilitates execution rather than owning backlog content.

  195. Question 195Practicing SAFe

    An ART's predictability measure shows a wide gap between planned and actual business value delivery across several PIs. What is the most appropriate SAFe response?

    1. Remove the IP iteration to gain more delivery time
    2. Investigate planning accuracy, dependency management, and capacity assumptions during inspect and adapt Correct answer.
    3. Increase the number of features committed to close the gap
    4. Discard the predictability measure because it is not a SAFe metric

    Explanation

    SAFe uses the predictability measure to trigger reflection on planning accuracy, unresolved dependencies, and capacity assumptions during inspect and adapt. The goal is to improve the reliability of planning and execution, not to inflate commitments.

  196. Question 196Practicing SAFe

    What is the purpose of the daily stand-up within a SAFe team?

    1. To demonstrate completed functionality to stakeholders
    2. To synchronize the team's work, surface impediments, and adjust the day's plan Correct answer.
    3. To report status to the Release Train Engineer
    4. To refine the program backlog with the Product Manager

    Explanation

    The daily stand-up is a team event for synchronizing work, exposing impediments, and adapting the plan for the day. It is not a status report to management or a demonstration of completed work.

  197. Question 197Practicing SAFe

    During PI Planning, a team identifies a dependency on a team in another ART that is not present in the same planning event. What is the best SAFe practice?

    1. Remove the dependent feature from the program backlog permanently
    2. Record the dependency so it can be coordinated with the other ART through the RTE or Solution Train Engineer Correct answer.
    3. Ignore the dependency until it becomes a blocker during execution
    4. Commit to the work anyway and assume the other team will deliver

    Explanation

    Cross-ART dependencies must be made visible and routed through the appropriate coordination channel, such as the RTE or Solution Train Engineer, so the other train can plan for them. Hiding or assuming the dependency creates delivery risk.

  198. Question 198Practicing SAFe

    Which statement best captures the relationship between team PI objectives and program PI objectives in SAFe?

    1. Team PI objectives are committed by each team and rolled up or aligned into program PI objectives that describe the train's business outcomes Correct answer.
    2. Team and program PI objectives are unrelated artifacts used by different roles
    3. Program PI objectives are written first and each team must accept them without modification
    4. Team PI objectives are optional, while program PI objectives are mandatory

    Explanation

    Teams write their own PI objectives and assign business value, and these are aligned into program PI objectives that express the train's intended business outcomes. This preserves team ownership while giving the ART a shared commitment.

  199. Question 199Practicing SAFe

    A leader wants to shift decision authority closer to where information lives. Which SAFe principle most directly supports this, and what is the corresponding guidance?

    1. Unlock intrinsic motivation, which removes the need for any decision rights
    2. Decentralize decision-making, reserving central decisions for those with economies of scale or cross-cutting impact Correct answer.
    3. Implement fast feedback, which mandates decisions at the portfolio level
    4. Apply systems thinking, which requires all decisions to be made centrally

    Explanation

    The decentralize decision-making principle pushes authority to the people closest to the information, while keeping certain decisions central where scale or cross-cutting impact justifies it. It is a deliberate balance rather than a blanket rule.

  200. Question 200Practicing SAFe

    What is the primary function of the Continuous Delivery Pipeline in SAFe?

    1. To serve as the budgeting mechanism for the portfolio
    2. To replace PI Planning with automated scheduling
    3. To provide a repository for team retrospectives
    4. To automate the flow of value from committed code to release, including continuous exploration, integration, deployment, and release on demand Correct answer.

    Explanation

    The Continuous Delivery Pipeline describes the automated and manual steps that move work from continuous exploration through integration and deployment to release on demand. It enables fast, reliable flow of value rather than replacing planning or budgeting.

STSC flashcards

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.

STSC study guide

Thriving in the Digital Age with Business Agility

Domain 1 - Thriving in the Digital Age with Business Agility. Exam items probe whether you can explain why SAFe exists and how a Scrum Master connects team-level work to enterprise outcomes: the definition of business agility, the seven core competencies, SAFe's four core values, the ten Lean-Agile principles, and the Scrum Master's part in each.

Core rules

  • Business agility is the ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative, digitally enabled business solutions.
  • Seven core competencies: Team and Technical Agility, Agile Product Delivery, Enterprise Solution Delivery, Lean Portfolio Management, Organizational Agility, Continuous Learning Culture, Lean-Agile Leadership. The two at the base - Lean-Agile Leadership and Continuous Learning Culture - underpin the rest; Organizational Agility is the change work of getting there.
  • Four core values: Alignment, Built-in Quality, Transparency, Program Execution. They are values, not process steps; every event is judged against them.
  • Ten principles. Most examined: #1 early and continuous value, #6 make value flow without interruptions, #8 unlock intrinsic motivation, #9 decentralize decision-making, #10 organize around value.

Worked example

A retail ART ships every 12 weeks and loses deals to competitors releasing monthly. The Scrum Master resists add more people and diagnoses by competency: regression testing is manual, so built-in quality is weak (Team and Technical Agility) and the pipeline is release-gated (Agile Product Delivery). Reasoning: business agility is an outcome of all seven competencies, so the constraint is the delivery system, not team effort. Action: raise it at the Inspect & Adapt problem-solving workshop, take a flow item to reduce batch size, and ask the LACE for test-automation coaching.

Traps

  • Defining business agility as doing Agile ceremonies faster.
  • Mixing core values with principles inside a scenario answer.
  • Assuming a Scrum Master cannot influence competencies above the team; coaching upward and escalating impediments to the RTE and LACE is part of the role.

Becoming a SAFe Scrum Master

Domain 2 - Becoming a SAFe Scrum Master. This domain tests the role itself: what a Scrum Master/Team Coach does inside an Agile Release Train, what they must not do, and how they serve the team and the ART at the same time.

Core rules

  • SAFe 6.0 names the role Scrum Master/Team Coach: servant leader and coach for the Agile Team, change agent for the ART.
  • Team duties: coach the team in SAFe principles and practices; facilitate Iteration Planning, Daily Stand-up, Iteration Review, Iteration Retrospective and Backlog Refinement; teach self-management; remove impediments and escalate what the team cannot remove; support the Product Owner on backlog and flow; build a high-performing team.
  • ART duties: prepare and facilitate team breakouts at PI Planning, represent the team at the Scrum of Scrums, contribute to the System Demo protocol, help run Inspect & Adapt. The RTE owns ART-level facilitation; the SM owns team-level facilitation.
  • Servant-leader behaviours SAFe draws on: listening, empathy, awareness, persuasion, foresight, stewardship, commitment to growth, building community.

Worked example

Mid-iteration the Product Owner adds three unplanned features and an external team misses a dependency. The Scrum Master does not simply refuse. Sequence: (1) coach the PO on iteration goals and WIP limits; (2) surface the dependency at the Scrum of Scrums so the RTE can resolve it; (3) protect focus by making trade-offs visible and letting the PO decide what to drop; (4) raise the recurring pattern in the retrospective. Reasoning: the SM owns the system around the team, not the work items - the PO owns priority, the team owns how much it takes on.

Traps

  • Describing the SM as team lead, task assigner, or project manager.
  • Confusing SM and RTE accountabilities.
  • Removing impediments by doing the team's technical work.
  • Command-and-control behaviour dressed in Agile vocabulary.

Establishing Team Agility

Domain 3 - Establishing Team Agility. Items test whether you can set up an Agile Team that can deliver every iteration: team design, the team events, goals, built-in quality, and flow.

Core rules

  • An Agile Team is cross-functional (it holds all skills needed to deliver), self-managing, small (SAFe describes roughly 5–11 people), and includes the Scrum Master and Product Owner. Teams stay stable; constant membership churn destroys the predictability you are trying to build.
  • Five team events: Iteration Planning (what and how much), Daily Stand-up (re-plan the day), Iteration Review (demo the increment, gather feedback), Iteration Retrospective (improve the system), Backlog Refinement (slice and size upcoming stories).
  • Artefacts: Team Backlog, Iteration Goals, team PI Objectives, the team's Definition of Done, the team board.
  • Built-in quality: agility is impossible on manual regression testing; test-first practices, automation and continuous integration belong in the Definition of Done.
  • Flow over velocity: SAFe 6.0 favours Flow Velocity, Flow Time, Flow Load, Flow Distribution, Flow Efficiency and Flow Predictability - used to find constraints, never to rank teams.

Worked example

A six-person team has 14 stories in progress and Flow Time doubling. The Scrum Master does not ask for overtime. Diagnosis: Flow Load exceeds capacity, creating long queues and slow feedback. Interventions: enforce WIP limits per board column, slice stories smaller, tighten the Definition of Done, and have the PO hold new scope until the next iteration. Measure Flow Time and Flow Load across three iterations to verify the change. Reasoning: the symptom is overload, not effort - fixing the queue fixes the delay.

Traps

  • Treating iteration goals and PI objectives as the same artefact.
  • Assuming self-managing means no accountability and no coaching.
  • Comparing velocity across teams as a performance measure.
  • Skipping Backlog Refinement, then blaming planning.

Building High-Performing Teams

Domain 4 - Building High-Performing Teams. Items test coaching judgement: how teams develop, how trust and psychological safety are built, how conflict is handled, and what actually motivates knowledge workers.

Core rules

  • Tuckman: forming → storming → norming → performing. Storming is normal, not failure; the Scrum Master moves the team through it rather than suppressing dissent.
  • Psychological safety (Edmondson) - the shared belief that you can speak up, admit error and ask questions without punishment - is the precondition for team learning. The SM models it by naming their own mistakes first.
  • Motivation: SAFe Principle 8 reflects Daniel Pink - autonomy, mastery, purpose. Carrots and sticks degrade knowledge work; the team needs autonomy over how it works.
  • Working agreements and Team Charter: explicit norms for meeting times, decision-making, and how disagreement gets resolved.
  • Conflict styles (Thomas–Kilmann): competing, collaborating, compromising, avoiding, accommodating. Collaborating is the default for design disputes; avoiding is the classic Scrum Master error when the team sits in artificial harmony.
  • Coaching stance: ask before telling; the team owns the solution.

Worked example

Two engineers clash repeatedly at stand-up over architecture. The SM resists escalating to their manager. Instead: separate 1:1s to hear both positions, surface the disagreement at the retrospective, agree a decision rule (a time-boxed spike plus a written decision record), and add disagree in the open, commit once decided to the working agreements. Reasoning: this is storming plus an unstated decision process; the fix is a team norm, not a verdict from above.

Traps

  • Jumping from forming straight to performing in a scenario answer.
  • Labeling all conflict as dysfunction.
  • Telling the team the answer instead of coaching it to one.
  • Assuming co-location is required for a high-performing team.

Planning and Executing Work in a SAFe Enterprise

Domain 5 - Planning and Executing Work in a SAFe Enterprise. The ART planning mechanics are heavily examined: PI Planning, the Program Board, PI Objectives, ROAM, the confidence vote, ART Sync, System Demos and Inspect & Adapt.

Core rules

  • Cadence: a PI is typically 8–12 weeks - four or five two-week iterations plus an Innovation and Planning (IP) iteration that carries no committed work and hosts the final System Demo and Inspect & Adapt.
  • PI Planning (two days, all teams): business context → product vision → architecture vision → team breakouts → draft plans → management review and problem solving → final plan → PI Objectives → program board → risks → confidence vote (fist of five).
  • Program Board visualises features, milestones and cross-team dependencies; ROAM classifies risks as Resolved, Owned, Accepted or Mitigated.
  • PI Objectives express business value, with committed and uncommitted items, and are scored by the business owner at PI end.
  • During execution: ART Sync (Scrum of Scrums plus PO Sync), a System Demo each iteration, and Inspect & Adapt in three parts - the PI System Demo, quantitative and qualitative measurement, and a problem-solving workshop using root-cause analysis.

Worked example

A team's plan returns a confidence vote of two fingers. The correct handling is not to re-vote until it passes. The SM and RTE surface the top risks and dependencies, the PO negotiates scope with the Product Manager, uncommitted objectives are used for stretch, and the plan is adjusted and re-voted. Reasoning: a low vote is data about unmitigated risk and overcommitment; transparency and adjustment raise confidence, pressure does not.

Traps

  • Treating PI Planning as a status meeting or a demo.
  • Writing PI Objectives as task lists instead of value statements.
  • Reading the Program Board as a Gantt chart.
  • Forgetting that the IP iteration is planned and protected.

Leading in a SAFe Enterprise

Domain 6 - Leading in a SAFe Enterprise. This domain is about influence without authority: the Scrum Master as a Lean-Agile leader, the principles used as decision tools, and the mechanics of organisational change.

Core rules

  • Lean-Agile Leadership is a core competency: leaders model the mindset (Lean thinking plus the Agile Manifesto), teach the principles, and align and unblock the system. A Scrum Master demonstrates it by coaching upward and making problems visible instead of quietly absorbing them.
  • Principle 9, decentralize decision-making, separates strategic decisions (centralized) from economic ones (decentralized) using a decision framework, so teams move fast without guessing.
  • Principle 10, organize around value, explains ARTs and value streams: structure follows the flow of value to the customer, not the org chart.
  • Leading change: the SAFe Implementation Roadmap sequences adoption - reach the tipping point, train leaders and change agents, identify value streams and the first ART, prepare and launch, then extend to the portfolio and sustain. Kotter's eight steps and John Shook's change guidance sit underneath.
  • LACE (Lean-Agile Center of Excellence) is the small group guiding adoption and coaching; a Scrum Master feeds it real constraints from the team.

Worked example

A director asks the Scrum Master to have the team absorb an extra feature mid-PI. The SM neither complies silently nor refuses. They make the trade-off explicit against the PI Objectives, ask the director to take it to PO Sync where economic decisions belong, and log it as a risk if it proceeds. Reasoning: this applies decentralized decision-making with clear boundaries and preserves transparency - leadership is exercised through the system, not around it.

Traps

  • Equating leadership with hierarchy or job title.
  • Starting a transformation with teams while leaders opt out.
  • Treating roadmap steps as a rigid, non-negotiable sequence.
  • Hiding organisational impediments inside the team.

Practicing SAFe

Domain 7 - Practicing SAFe. The closing domain is applied: what you will actually do differently, how you keep improving, and how you keep learning after the course ends.

Core rules

  • Practice starts with observation, not redesign. Assess the current state - events, artefacts, flow metrics, team health - before changing anything.
  • Convert findings into a small, measurable improvement backlog and iterate it with PDCA (plan–do–check–adjust): pick one or two constraints, run an experiment for a few iterations, measure, keep or discard.
  • Continuous Learning Culture, one of the seven competencies, has three dimensions: a learning organisation, relentless improvement, and a culture of innovation. The Scrum Master protects time for learning and normalises cheap, fast experiments.
  • Use the system you teach: run a retrospective on your own facilitation, ask the team for feedback, and work with a coach or mentor.
  • Stay connected: the SAFe community platform (SAFe Studio), communities of practice, and annual certification renewal with continuing education keep knowledge current.

Worked example

A new Scrum Master's first 90 days: days 1–30 attend every team event and record observations only; days 31–60 introduce working agreements and a Definition of Done with the team's consent; days 61–90 pilot WIP limits and a Flow Time metric, then review the pilot in a retrospective on the change itself. Reasoning: every step is small, reversible, measured and owned by the team - the pattern exam items reward over a big-bang transformation.

Traps

  • Copying another organisation's practices verbatim.
  • Launching many changes at once with no measurement.
  • Treating certification as the destination rather than the starting point.
  • Driving improvement at the team instead of with it.

STSC cheat sheet

Quick reference

Thriving in the Digital Age with Business Agility

  • Business agility is the ability of an organization to compete and thrive by sensing and responding to market changes with speed and stability; it is a whole-enterprise property, not a team property.

  • SAFe's seven core competencies: Lean-Agile Leadership, Team and Technical Agility, Agile Product Delivery, Enterprise Solution Delivery, Lean Portfolio Management, Organizational Agility, and Continuous Learning Culture.

  • Digital disruption shifts value from physical assets to information; the response pattern is shorter feedback loops, smaller batches, and decentralized decision-making rather than larger upfront plans.

  • SAFe is built on ten Lean-Agile principles, including #1 take an economic view, #6 make value flow without interruptions, #8 unlock intrinsic motivation, and #9 decentralize decision-making.

  • The SAFe Core Values are Alignment, Transparency, Respect for People, and Relentless Improvement; Built-in Quality is a fifth principle-level value in newer versions and is often tested alongside the four.

  • A SAFe Lean-Agile Mindset combines the Lean-Agile Leaders' mindset with the House of Lean (Value, Respect for People and Culture, Flow, Innovation, Relentless Improvement).

  • Sensing and responding replaces predict-and-plan: organizations that shorten the observe-orient-decide-act (OODA) loop handle volatility better than those optimizing for plan accuracy.

  • Business agility outcomes are measured by flow (lead time, throughput), quality (defects, built-in quality), and employee engagement, not by velocity alone.

Quick reference

Becoming a SAFe Scrum Master

  • The SAFe Scrum Master (SSM) serves the team, the Product Owner, and the organization; in SAFe the role is explicitly a servant leader and a team coach, not a project manager or a line manager.

  • Core SSM responsibilities: facilitate team events, coach the team in Scrum and SAFe practices, remove impediments, support PI Planning, and help the team improve via Inspect & Adapt.

  • The SSM is a member of the Scrum Master/Team Coach group that participates in the Scrum of Scrums (SoS) during the PI, plus the ART Sync, and helps coordinate dependencies across teams.

  • Scrum Master duties in SAFe include helping the team estimate and plan at PI Planning, protecting the team from scope overload, and fostering DevOps and Built-in Quality practices.

  • A key mindset shift from traditional project management: the SSM does not assign tasks or own the schedule; the team self-manages its work within the Iteration and PI cadence.

  • The SSM coaches the Product Owner on backlog management, story splitting, and PI objectives, and coaches the team on the Definition of Done and collective ownership.

  • Servant leadership in SAFe is expressed through the Lean-Agile Leader behaviors: leading by example, coaching, unlocking intrinsic motivation, and creating psychological safety.

  • The SSM supports the team's participation in the Continuous Delivery Pipeline and helps the team achieve a system demo every iteration.

Quick reference

Establishing Team Agility

  • An Agile Team in SAFe is typically 3-11 people (5-9 common), cross-functional, and owns the full flow of value for its features from definition through delivery.

  • Iteration cadence is a fixed timebox (commonly two weeks) containing Iteration Planning, daily stand-up, Iteration Review, and Retrospective; the timebox is protected and does not stretch.

  • The Definition of Done (DoD) is a team-owned, explicit checklist of quality criteria; the team must meet the DoD every iteration, and incomplete stories return to the backlog.

  • Iteration Planning produces a committed Iteration Backlog and a set of Iteration Goals; capacity is based on the team's velocity and known availability, not on ideal hours.

  • Stories are sized to be completed within one iteration and follow the INVEST criteria; enablers are tracked separately as Exploration, Architecture, Infrastructure, or Compliance enablers.

  • Built-in Quality means quality is designed in, not tested in: practices include paired work, TDD/ATDD, continuous integration, refactoring, and automated testing.

  • Team Topologies concepts (stream-aligned, platform, complicated-subsystem, enabling teams) help the SSM design the team boundary and interaction modes.

  • Team agility depends on stable membership and a shared cadence; frequent re-forming of teams destroys the trust and tacit knowledge required for flow.

Quick reference

Building High-Performing Teams

  • Tuckman's stages - Forming, Storming, Norming, Performing, Adjourning - describe team development; the SSM's coaching style shifts from directing to delegating as the team matures.

  • Psychological safety (Edmondson) is the shared belief that speaking up is safe; it is the strongest predictor of team learning and is a prerequisite for high performance.

  • Intrinsic motivation is unlocked by autonomy, mastery, and purpose; SAFe Principle #8 states knowledge workers must be engaged and motivated to be effective.

  • High-performing teams are self-organizing and self-managing: they decide how to do the work, own their commitments, and hold each other accountable.

  • Conflict is normal and, when task-focused and managed well, improves decisions; the SSM distinguishes healthy task conflict from destructive relationship conflict.

  • Retrospectives should produce a small number of owned, measurable improvement actions; SAFe's Inspect & Adapt (I&A) event escalates team-level issues to the ART level.

  • Distributed teams need explicit working agreements: overlapping core hours, shared tooling, asynchronous documentation, and clear decision rights.

  • Team metrics for high performance include flow efficiency, predictability (planned vs. actual PI objectives), quality, and engagement - not individual utilization.

Quick reference

Planning and Executing Work in a SAFe Enterprise

  • PI Planning is a two-day, face-to-face (or highly interactive) event where all teams on an Agile Release Train (ART) align to a shared mission and produce PI Objectives and a Program Board.

  • A PI is a fixed timebox of typically 8-12 weeks (5 iterations of 2 weeks is common), including an Innovation and Planning (IP) iteration that also hosts Inspect & Adapt.

  • PI Objectives are business summaries of what the team intends to deliver; each is scored with a business value from 1-10, and the sum yields the team's planned business value for the PI.

  • The Program Board shows features, milestones, and cross-team dependencies (red strings); dependencies are identified at PI Planning and tracked through the PI.

  • The ART Sync (or Scrum of Scrums) is a weekly event where Scrum Masters/Team Coaches and the RTE coordinate progress, dependencies, and risks.

  • Features are the ART-level work item, decomposed into stories owned by teams; the ART backlog is managed by the Product Manager with the System Architect/Engineering.

  • The System Demo occurs at the end of every iteration and shows the integrated solution from all teams; the ART's stakeholders inspect the working increment.

  • Inspect & Adapt closes the PI with a problem-solving workshop on the ART's metrics (flow, quality, predictability) and produces improvement backlog items for the next PI.

Quick reference

Leading in a SAFe Enterprise

  • Lean-Agile Leaders are responsible for the organization's Lean-Agile transformation: they lead by example, adopt the SAFe principles, and teach them to others.

  • The Release Train Engineer (RTE) is the ART's servant leader and chief Scrum Master: facilitates PI Planning, ART Sync, and I&A, and manages risk and dependencies.

  • The Product Manager owns the ART backlog, defines and prioritizes features, and validates that delivered features meet the intended outcomes.

  • The System Architect/Engineering role defines the architecture and nonfunctional requirements and provides technical guidance across the ART.

  • Lean Portfolio Management (LPM) aligns strategy to execution via the Portfolio Kanban, Lean Budgets, and value stream funding; epics are approved through a lightweight business case and Lean Portfolio Management approval.

  • Decentralized decision-making (Principle #9) requires clear decision rights: leaders set intent and boundaries, and teams make the technical and delivery decisions within them.

  • Transformation success is measured by outcome and flow metrics (lead time, predictability, quality) and by the adoption of the SAFe core values, not by ceremony compliance alone.

  • Leaders create the environment for change by building a guiding coalition, communicating the why, removing organizational impediments, and protecting the change from reversion.

Quick reference

Practicing SAFe

  • The SAFe Implementation Roadmap has 12 steps, starting with reaching the tipping point and ending with optimizing flow; the first ART launch typically occurs around step 5 (Launch more ARTs and Value Streams).

  • The ART is the primary value delivery construct: a long-lived team of Agile Teams (50-125 people) that plans, commits, and executes together on a shared cadence.

  • Value streams are the sequence of steps that deliver value to a customer; Development Value Streams are the ones an ART or Solution Train builds and operates.

  • The Continuous Delivery Pipeline has four aspects: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand.

  • Built-in Quality is a SAFe core value; the SSM practices it by enforcing the DoD, promoting test automation, and ensuring code is integrated continuously.

  • SAFe configurations are Essential, Large Solution, Portfolio, and Full; choose the smallest configuration that addresses the organization's complexity.

  • The SSM supports the Innovation and Planning iteration by protecting time for innovation, PI planning preparation, and improvement work.

  • Metrics for practicing SAFe: flow velocity, flow time, flow load, flow efficiency, and flow distribution; predictability is measured as planned vs. actual business value.

STSC key terms

Business Agility

An organization's ability to compete and adapt by delivering innovative products and services quickly, using Lean-Agile practices across the whole enterprise rather than isolated teams.

Related: Lean Portfolio Management, Agile Release Train
Agile Manifesto

Four value statements and twelve principles written in 2001 that prioritize individuals, working software, customer collaboration, and responsiveness to change over documentation, contracts, and plans.

Related: Scrum, Iteration
SAFe Lean-Agile Principles

Ten foundational principles, such as taking an economic view and assuming variability, that guide decisions and behaviors for leaders and teams applying SAFe across the enterprise.

Related: Business Agility, Lean Portfolio Management
SAFe Scrum Master

The role responsible for coaching the team in Agile practices, facilitating team events, removing impediments, and fostering a culture of continuous improvement within a SAFe environment.

Related: Team Coach, Scrum Master as Servant Leader
Servant Leadership

A leadership style in which the Scrum Master puts the team's needs first, removes obstacles, and enables others to grow rather than directing their daily work.

Related: SAFe Scrum Master, Team Coach
Team Coach

The aspect of the Scrum Master role focused on teaching Agile mindset and practices, observing team dynamics, and giving feedback that improves how the team works together.

Related: Servant Leadership, Retrospective
Scrum Master as Facilitator

The practice of designing and guiding team events so that participants reach their own decisions, keeping discussions focused while remaining neutral about content.

Related: Scrum Master as Servant Leader, Iteration Planning
Scrum Master as Servant Leader

A description of the role emphasizing service to the team and the wider organization: shielding the team from distraction, coaching stakeholders, and modeling SAFe values.

Related: Servant Leadership, SAFe Scrum Master
Agile Team

A cross-functional group of typically five to eleven people that defines, builds, and tests increments of value within an iteration, owning its own plan and process.

Related: Iteration, Scrum Team
Scrum Team

A small self-managing group consisting of one Scrum Master, one Product Owner, and developers, collectively accountable for delivering a valuable, useful increment each iteration.

Related: Agile Team, Product Owner
Product Owner

The team member accountable for maximizing value by managing and prioritizing the team backlog, defining stories, and accepting completed work on behalf of stakeholders.

Related: Team Backlog, User Story
Iteration

A fixed-length timebox, usually two weeks, during which an Agile Team builds and tests a potentially releasable increment of the solution.

Related: Iteration Planning, System Demo
Team Backlog

The ordered list of user stories, enablers, and other work items the team intends to complete, maintained by the Product Owner and refined continuously.

Related: Product Owner, User Story
User Story

A short description of a small piece of desired functionality written from the user's perspective, typically stating who wants it, what they want, and why.

Related: Team Backlog, Definition of Done
Definition of Done

A shared checklist describing the quality criteria an increment must meet before the team considers a backlog item complete, reducing ambiguity about finished work.

Related: User Story, System Demo
Built-in Quality

The practice of embedding quality checks into every step of development so defects are prevented or caught immediately rather than discovered in later testing phases.

Related: Definition of Done, Continuous Integration
Iteration Planning

A team event at the start of each iteration where the team selects backlog items, agrees on how to build them, and commits to a goal for the timebox.

Related: Iteration, Iteration Goal
Iteration Goal

A short statement of the business value the team intends to deliver in the current iteration, used to focus work and guide trade-off decisions.

Related: Iteration Planning, Iteration Review
Iteration Review

A team event at the end of an iteration where the team demonstrates the working increment to stakeholders and collects feedback for future backlog items.

Related: System Demo, Iteration Goal
Retrospective

A recurring team event where members inspect how they worked, identify improvements, and agree on a small number of actions to try in the next iteration.

Related: Team Coach, Continuous Improvement
Continuous Improvement

An ongoing effort to incrementally improve products, processes, and team interactions, driven by frequent reflection and small, measurable experiments.

Related: Retrospective, Problem Solving Workshop
High-Performing Team

A team that consistently delivers value, holds itself accountable, communicates openly, and continuously raises its own performance through trust and shared goals.

Related: Psychological Safety, Tuckman Model
Psychological Safety

A climate in which people feel safe to speak up, admit mistakes, ask questions, and challenge ideas without fear of punishment or humiliation.

Related: High-Performing Team, Conflict Resolution
Tuckman Model

A description of team development stages - forming, storming, norming, performing - that helps a Scrum Master choose appropriate coaching for the team's current stage.

Related: High-Performing Team, Team Coach
Conflict Resolution

The skill of surfacing disagreements and guiding people toward a workable solution, distinguishing constructive task conflict from destructive personal conflict.

Related: Psychological Safety, Retrospective
Problem Solving Workshop

A structured, timeboxed SAFe event in which a team and stakeholders analyze a persistent problem, find root causes, and agree on corrective actions.

Related: Continuous Improvement, Impediment
Agile Release Train

A long-lived team of Agile Teams, typically 50 to 125 people, that plans, commits, and delivers value together on a shared cadence aligned to the program.

Related: Program Increment, PI Planning
Program Increment

A fixed timebox, usually eight to twelve weeks, during which an Agile Release Train delivers a set of planned features and learns through a system demo.

Related: PI Planning, System Demo
PI Planning

A two-day event where all teams on the train align on a shared mission, draft iteration plans, identify dependencies, and commit to objectives for the increment.

Related: Program Increment, PI Objectives
PI Objectives

Short summaries of the business value each team intends to deliver during a program increment, committed to at PI Planning and reviewed at the end.

Related: PI Planning, Program Increment
System Demo

An event at the end of each iteration where teams on the train integrate their work and demonstrate the full solution to stakeholders for feedback.

Related: Program Increment, Iteration Review
Inspect and Adapt

A structured event at the end of a program increment where the train reviews results, identifies root causes of problems, and agrees on improvements.

Related: Program Increment, Continuous Improvement
Dependency

A relationship in which one team's work must be completed or decided before another team can proceed, tracked visually and resolved through coordination.

Related: PI Planning, Impediment
Impediment

Any obstacle that slows or blocks a team from completing its work, which the Scrum Master helps remove or escalates to the appropriate level.

Related: Problem Solving Workshop, Dependency
Lean Portfolio Management

The SAFe function that aligns strategy and execution by applying Lean budgeting, portfolio flow, and governance so investment follows value.

Related: Business Agility, Value Stream
Value Stream

The sequence of steps an organization uses to deliver value to a customer, used to organize development around flow rather than functional silos.

Related: Lean Portfolio Management, Agile Release Train
Lean-Agile Leadership

The mindset and behaviors leaders adopt to model SAFe principles, teach and coach others, and create the environment in which teams can thrive.

Related: SAFe Lean-Agile Principles, Servant Leadership
Continuous Delivery Pipeline

The set of automated and manual practices - continuous exploration, integration, deployment, and release on demand - that move work from idea to customer.

Related: Continuous Integration, Built-in Quality
Continuous Integration

The practice of merging code changes frequently into a shared mainline and verifying each merge with automated builds and tests to surface problems early.

Related: Continuous Delivery Pipeline, Built-in Quality
DevOps

A culture and set of technical practices that unify development and operations to shorten lead time, improve reliability, and deliver value continuously.

Related: Continuous Delivery Pipeline, Continuous Integration

STSC study plan

8 weeks · About 7 hours per week

Week 1

Establishing Team Agility

  • Define Business Agility, Lean-Agile Leadership, and the seven core competencies in your own words, then map which competency each later week of this plan strengthens.

  • Describe the Scrum Master's three SAFe responsibilities (team facilitator, team coach, servant leader) and contrast them with a traditional project manager's duties in a short written comparison.

  • Diagram the SAFe core values, Lean-Agile mindset, and SAFe Principles 1-5, and explain how each principle shows up in daily team behavior.

  • List the Scrum Master's role in each team event (PI Planning, Iteration Planning, Daily Stand-up, Iteration Review, System Demo, Inspect & Adapt) with one concrete action per event.

Your checkpoint

A one-page role charter that states what you own as SAFe Scrum Master, what you do not own, and the three metrics you will use to judge team health.

Week 2

Establishing Team Agility

  • Explain how Agile Teams fit inside the Agile Release Train, including the team's dependency on the ART cadence and sync points.

  • Walk through the Iteration cadence: Iteration Planning, backlog refinement, Daily Stand-up, Iteration Review, and Iteration Retrospective, and state the Scrum Master's facilitation intent for each.

  • Distinguish team PI objectives from ART PI objectives and describe how committed versus uncommitted objectives are used.

  • Practice writing three user stories with clear acceptance criteria and split one that is too large using the vertical-slice technique.

Your checkpoint

A facilitation kit covering Iteration Planning and Iteration Retrospective: purpose, agenda with timeboxes, inputs, outputs, and the anti-patterns you will watch for.

Week 3

Establishing Team Agility & Building High-Performing Teams

  • Build a team working agreement template and explain how to co-create it with a team rather than imposing it.

  • Define the Scrum Master's coaching stance and practice three coaching questions you would use instead of giving advice during a team conflict.

  • Describe the Tuckman stages and identify two concrete Scrum Master interventions for the storming stage.

  • Explain how to use team flow metrics such as cycle time and velocity trends to start a retrospective conversation without blaming individuals.

Your checkpoint

A retrospective design for a team in conflict, including the format, the prompts, and how you will follow up on the resulting actions.

Week 4

Building High-Performing Teams & Planning and Executing Work in a SAFe Enterprise

  • Explain the purpose and structure of PI Planning, including the inputs, the two-day agenda, and the Scrum Master's logistics and facilitation duties.

  • Describe how to prepare a team for PI Planning: capacity, draft objectives, and pre-identified risks and dependencies.

  • Practice writing PI objectives that are business-value oriented and SMART, then critique three weak examples.

  • Explain how ROAM is used to address risks in PI Planning and classify five sample risks.

Your checkpoint

A complete PI Planning prep pack for a fictional six-person team: capacity calculation, draft PI objectives, a dependency list, and a risk board with ROAM classifications.

Week 5

Planning and Executing Work in a SAFe Enterprise

  • Describe how the ART executes an iteration: the Scrum of Scrums, the PO Sync, the System Demo, and the Inspect & Adapt event, and state what each is for.

  • Explain how to visualize and manage cross-team dependencies during execution, including how to escalate a blocked dependency.

  • Describe the ART Sync and how it differs from a team's Daily Stand-up in purpose and participants.

  • Explain how to track progress against PI objectives and what to do when a team will miss a committed objective.

Your checkpoint

A dependency management playbook: how you will identify, visualize, escalate, and close dependencies across a simulated PI.

Week 6

Building High-Performing Teams & Leading in a SAFe Enterprise

  • Explain how to foster high-performing teams: psychological safety, shared purpose, and the Scrum Master's role in removing impediments.

  • Describe the difference between the Scrum Master's servant-leader, facilitator, and coach stances, and pick the right stance for three scenarios.

  • Explain how to coach a Product Owner on backlog prioritization and how to coach a team on self-management.

  • Describe how to handle a team member who dominates discussions, using a specific intervention you would practice.

Your checkpoint

A coaching plan for one struggling team member or team dynamic, with the observation, the coaching approach, and how you will measure improvement.

Week 7

Leading in a SAFe Enterprise & Becoming a SAFe Scrum Master

  • Explain how the Scrum Master supports the ART's Inspect & Adapt and problem-solving workshop, including the role of the root-cause analysis.

  • Describe how to lead a team through a retrospective that produces a small number of owned improvement actions.

  • Explain the Scrum Master's role in the continuous learning culture competency, including how to build a learning backlog.

  • Describe how to use the SAFe implementation roadmap phases to explain where a team is and what comes next.

Your checkpoint

An Inspect & Adapt facilitation plan, including the problem-solving format, the improvement backlog, and the owners for each action.

Week 8

Thriving in the Digital Age with Business Agility & Practicing SAFe

  • Review all seven domains and write a one-page summary of each, then identify your three weakest areas.

  • Explain how Business Agility, the seven core competencies, and the SAFe Principles connect to the Scrum Master's daily work.

  • Complete a full timed practice exam and review every missed question to identify the underlying concept gap.

  • Build a personal 30-day plan for applying SAFe Scrum Master practices to your current team.

Your checkpoint

A scored practice exam with a written review of every missed question and a 30-day application plan.

Milestones

Week 2: Can explain the Scrum Master role, the team's place in the ART, and facilitate Iteration Planning and Retrospective from your own kit without notes.

Week 4: Can run a full PI Planning prep for a team, write SMART PI objectives, and ROAM a risk list; score at least 70% on a domain 3-5 practice set.

Week 6: Can explain dependency management, ART sync, and coaching stances, and produce a coaching plan with measurable outcomes.

Week 8: Score at least 80% on a full timed practice exam and have a written review of every missed question plus a 30-day application plan.

STSC exam day

Your checklist

Government-issued photo ID

Bring the exact name-matching photo ID your registration requires. Confirm with the provider which ID types are accepted and whether a secondary ID is needed; if you are unsure your ID matches your registered name, resolve it before test day.

Appointment confirmation and test-taker ID number

Have your confirmation email, scheduling number, and provider login credentials accessible (printed or on your phone). You may need them at check-in or if the proctor has to look up your record.

Know your test format and delivery mode

Confirm whether you are taking the exam at a test center or remotely, the appointment time and time zone, and the total seat time. Verify the current format and duration on the provider's official page rather than relying on secondhand summaries.

Review the current official content outline

Download the latest exam blueprint or content outline from the provider and check that your study materials match the current version. Outlines change; do not study to an outdated domain list.

Confirm allowed and prohibited items

Check the provider's test-center or remote-proctoring rules on notes, calculators, scratch paper, phones, watches, and water. Rules differ by delivery mode, so confirm with the provider instead of assuming.

Remote-testing environment check (if applicable)

If testing remotely, run the provider's system check in advance, confirm webcam/microphone/bandwidth, and prepare a quiet, cleared, private room. Confirm the provider's specific room and desk requirements.

Plan your route and arrival buffer

For a test center, know the address, parking or transit options, and building/room location, and arrive earlier than the provider's stated check-in time. For remote testing, log in early to complete identity checks.

Light, familiar study materials for the final day

Bring only a concise summary of high-yield facts and your own notes for a short pre-test review. Avoid learning new material in the last 24 hours; it raises anxiety more than scores.

Hydration, food, and medication plan

Eat a normal meal, bring water if allowed, and follow your usual medication routine. Confirm with the provider whether water, snacks, or medication access is permitted during the test or only on breaks.

Rest and logistics for the night before

Protect sleep, set two alarms, and lay out ID, confirmation, and clothing the night before. Fatigue is a bigger score risk than one more hour of review.

Backup plan for technical or transport failure

Save the provider's support phone number and know their reschedule or technical-issue policy in advance. Confirm with the provider how to report a technical failure during a remote test.

Plan the day

72 hours before

Stop expanding your scope. Re-read the official content outline and confirm the current exam version, duration, and delivery mode. Take one timed practice set under realistic conditions, then review only the explanations for missed items. Write a one-page sheet of facts you keep missing and study only that.

48 hours before

Confirm logistics: appointment time and time zone, test-center address or remote-testing setup, ID requirements, and allowed items. Run any required system check for remote delivery. Resolve any name or ID mismatch now, not on test day.

24 hours before

Do a short, light review of your one-page sheet and high-level frameworks, then stop. Prepare ID, confirmation, and clothing. Eat a normal meal, avoid heavy caffeine after midday, and go to bed at your usual time. Do not attempt a full-length practice exam.

Morning of

Eat a normal breakfast, hydrate moderately, and do a 10-15 minute skim of your summary sheet only. Leave with buffer for transport or log in early for remote testing. Keep your phone off and stowed unless the provider allows otherwise.

At check-in

Follow proctor instructions exactly, present your ID, and store prohibited items as directed. Read the test rules and nondisclosure agreement carefully before accepting them. If anything about the setup seems wrong, raise it before the timer starts.

During the test

Read each question fully, answer the ones you know first, and flag uncertain items to revisit. Watch the clock and allocate time so you can review flagged questions. For scenario questions, identify what is being asked and eliminate clearly wrong options before choosing.

Breaks

Take scheduled breaks if offered, stand and stretch, and return promptly. Confirm with the provider whether breaks are timed and whether the clock stops; do not assume.

Final minutes and after

Use remaining time to confirm you have answered every question and that flagged items have a final choice. Submit deliberately, note your unofficial result if shown, and keep your score report and confirmation for your records.

Rules to check

  • Bring the ID required by the provider and ensure the name matches your registration exactly. If you are unsure which documents qualify, confirm with the provider before test day.

  • Follow all proctor instructions and the published test-center or remote-testing rules. Prohibited items and permitted materials vary by delivery mode, so confirm the list with the provider rather than guessing.

  • Do not communicate with other test takers, use unauthorized materials, or attempt to record or share exam content. Nondisclosure and misconduct rules apply and can result in score cancellation.

  • Understand the scoring model before you sit: confirm whether the exam is pass/fail, how it is scaled, and whether wrong answers are penalized. Do not assume a guessing penalty; confirm with the provider.

  • Know the break policy in advance. Some exams offer scheduled breaks, some are untimed or timed differently, and some do not permit breaks; confirm the specifics with the provider.

  • If a technical failure, illness, or emergency occurs, stop and follow the provider's stated procedure and contact their support line. Do not attempt to troubleshoot in ways that violate testing rules.

  • Arrive or log in before the stated check-in time. Late arrivals may be refused entry or lose seat time depending on provider policy, so confirm the cutoff with the provider.

  • Keep your confirmation, score report, and any case number. If you need to dispute a result or reschedule, those records and a prompt request to the provider are usually required.

STSC FAQ

How many STSC practice questions are available?

The practice set has 200 STSC questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many STSC flashcards are available?

The flashcard set has 33 STSC cards. Each card shows the term and its definition.

Which topics does the STSC study material cover?

The STSC study material has 7 sections, including Thriving in the Digital Age with Business Agility, Becoming a SAFe Scrum Master, and Establishing Team Agility.

What format facts does the catalog list for the STSC exam?

The catalog lists these item types: multiple choice, single answer, and multiple response for the STSC exam.