Try 45 free SAFe Scrum Master questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length SAFe Scrum Master practice exam includes 45 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 45-question full-length practice format for the SAFe Scrum Master route. Always confirm current exam count, timing, passing score, and renewal rules directly with Scaled Agile.
Set a 90-minute timer and answer all 45 questions before reading explanations. Track misses by Scrum Master facilitation, team events, ART participation, flow, impediments, or servant leadership.
Use this page as an SSM diagnostic, not as the only measure of readiness. The most useful result is the pattern behind your misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your Scrum Master / Team Coach model may be stable. Review explanations and protect timing. | |
| Many Scrum-in-SAFe misses | Revisit Scrum basics, Agile teams, DevOps, release on demand, and batch-size thinking in SAFe context. | |
| Many role-boundary misses | Drill servant leadership, coaching, facilitation, and when to escalate systemic impediments. | |
| Many team-event misses | Review iteration planning, team sync, refinement, review, and retrospective purpose. | |
| Many ART-event misses | Review PI Planning, IP Iteration, Inspect and Adapt, dependencies, and RTE collaboration. |
| Field | Record |
|---|---|
| Overall score | ___ / 45 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | Scrum in SAFe / role / team events / ART events |
| Most expensive mistake type | over-controlling team / weak impediment handling / wrong event purpose / wrong escalation level / other: ___ |
This static page is useful for one diagnostic pass. PM Mastery is better for repeated practice because it gives you varied timed attempts, focused SSM drills, explanations, and progress history instead of one page you can memorize.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-15 | 30 minutes | Keep Scrum Master / Team Coach boundaries clear. |
| Questions 16-30 | 60 minutes cumulative | Watch for team-event and flow anti-patterns. |
| Questions 31-45 | 90 minutes cumulative | Finish with enough time to review marked ART-event and dependency items. |
If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Give more weight to varied timed attempts in PM Mastery than to repeating one static page.
| Item | Detail |
|---|---|
| Issuer | Scaled Agile |
| Exam route | SAFe Scrum Master |
| Official exam name | AI-Empowered SAFe Scrum Master (SSM) |
| Full-length set on this page | 45 questions |
| Exam time | 90 minutes |
| Topic areas represented | 4 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Introducing Scrum in SAFe | 25% | 11 |
| Defining the Scrum Master / Team Coach Role | 28% | 13 |
| Supporting Team Events | 19% | 8 |
| Supporting ART Events | 28% | 13 |
Topic: Introducing Scrum in SAFe
Which team habit best supports sustainable pace and reliable delivery by helping an Agile team finish started work before taking on more?
Best answer: A
What this tests: Introducing Scrum in SAFe
Explanation: Limiting work in process is a key collaboration habit for sustainable pace and reliable delivery. It helps the team focus, finish work, expose bottlenecks, and avoid overcommitting.
In SAFe and Scrum, sustainable pace depends on managing flow, not keeping every person busy at all times. A team that limits WIP makes work visible and reduces context switching, which helps them complete backlog items more reliably within an iteration. This habit also makes impediments easier to see because blocked or aging work stands out on the team board.
The key takeaway is that reliable delivery comes from finishing valuable work predictably, not from starting more work than the team can reasonably complete.
Limiting WIP reduces overload and improves flow, making delivery more predictable and sustainable.
Topic: Defining the Scrum Master / Team Coach Role
During PI Planning, a business owner presses the Scrum Master / Team Coach for a firm commitment on a high-priority feature after the Product Owner notes a dependency on another team. The Agile team is still discussing capacity, risks, and a draft PI Objective. What is the BEST action for the Scrum Master / Team Coach?
Best answer: A
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: The Scrum Master / Team Coach facilitates clarity, transparency, and healthy decision-making. In this situation, the team needs help making capacity, risks, and dependencies visible so it can decide what is realistic, rather than having the Scrum Master make a commitment on its behalf.
A Scrum Master / Team Coach serves the team by facilitating collaboration, surfacing impediments, and supporting transparency during ART events such as PI Planning. When delivery pressure appears, the role is not to make scope or commitment decisions for the team. The better move is to help the Agile team, Product Owner, and relevant ART participants clarify capacity, dependency impact, risks, and PI Objective wording so the team can form a realistic plan and communicate confidence honestly. This protects team accountability while still supporting ART alignment.
The key boundary is that facilitation helps the team reach a decision; it does not replace the team’s ownership of the plan.
The Scrum Master / Team Coach helps the team reach clarity and transparency while leaving delivery commitments to the team and Product Owner.
Topic: Supporting ART Events
During PI execution, an Agile team discovers that its API change will slip by one Iteration. The delay affects another team’s planned feature start and a third team’s test environment booking. The Product Owner wants to handle it privately with one other PO to avoid “noise,” while the RTE has asked Scrum Masters / Team Coaches to improve ART-level dependency visibility. What is the best action for the Scrum Master / Team Coach?
Best answer: A
What this tests: Supporting ART Events
Explanation: Cross-team transparency is essential when one team’s delay changes another team’s sequence of work. The Scrum Master / Team Coach should help make the dependency visible in the appropriate ART coordination forum so affected teams can adjust plans together before the impact grows.
In SAFe, dependencies and impediments that affect multiple teams should be visible to the ART, not managed as private side conversations. The Scrum Master / Team Coach does not own the technical decision or product priority, but they do facilitate transparency, coordination, and flow. By surfacing the issue in ART Sync or another agreed ART coordination mechanism, the affected teams, Product Owners, and RTE can see the real sequencing impact and adjust commitments, environment use, or feature timing earlier. Keeping the issue local may feel efficient, but it increases the chance that Team C or other stakeholders discover the conflict too late.
Making the delay visible across affected teams supports coordinated sequencing, earlier trade-offs, and fewer late surprises.
Topic: Supporting Team Events
During several team syncs, an Agile team walks through each person’s completed tasks while the Scrum Master / Team Coach updates the board. Blocked work and stories at risk are usually discussed later in one-on-one chats, and the team rarely changes its plan during the sync. What does this practice most likely indicate?
Best answer: C
What this tests: Supporting Team Events
Explanation: The team sync is meant to help the team coordinate daily work and adapt its plan based on current progress, blockers, and risks. When it becomes individual reporting and issues move to private follow-ups, the team loses the shared inspection and adaptation purpose of the event.
The core concept is the team sync’s focus on flow, blocker management, and adapting the team’s near-term plan. In the stem, the team is reporting completed tasks to the Scrum Master / Team Coach while the board is updated for them. More importantly, blockers and at-risk work are handled outside the team conversation, so the team is not collectively deciding how to adjust its plan. A healthy sync keeps the work visible and helps the team decide what to do next to meet its iteration goals. The closest trap is assuming another event is the problem, but the described symptoms are inside the team sync itself.
A team sync should help the team inspect progress, expose blockers, and adapt the plan together, not report individual status to the Scrum Master / Team Coach.
Topic: Introducing Scrum in SAFe
A SAFe Agile team says a story is complete because coding and team-level tests passed. However, the feature still cannot be released because integration with another team’s service and security validation remain unfinished. Which term best describes this gap?
Best answer: D
What this tests: Introducing Scrum in SAFe
Explanation: The key concept is undone work: effort left over after a team claims completion but before the value is actually releasable. In SAFe, local completion is not enough if integration, validation, or other release-quality work remains.
In SAFe, Agile teams should strive to create integrated, tested, potentially releasable increments. When a team meets only a local checklist but still needs cross-team integration, security validation, or other release-readiness activities, that remaining effort is undone work. It exposes a mismatch between the team’s local definition of complete and what the ART needs for release on demand.
The key takeaway is that “done” should include the quality and integration work needed to make value releasable, not just locally finished.
Undone work is remaining activity needed before an increment is truly releasable, even if a team considers it locally complete.
Topic: Supporting ART Events
An ART is preparing for PI Planning. Several Agile teams have their own backlogs, but they are unsure how their work fits together and which cross-team dependencies matter most for the next 10 weeks. What is the primary purpose of PI Planning in this situation?
Best answer: C
What this tests: Supporting ART Events
Explanation: PI Planning is the ART event that aligns multiple Agile teams to a shared mission and set of PI Objectives. It helps teams understand priorities, expose dependencies, and create a coordinated plan for the upcoming Program Increment.
The core purpose of PI Planning is ART-level alignment. Before and during the event, teams connect their local backlog work to the broader business context, identify dependencies with other teams, and draft PI Objectives that show how their work contributes to shared outcomes. This is not about approving every task or managing only one team’s sprint details; it is about creating a common plan across teams for the next PI. The Scrum Master / Team Coach helps the team prepare by clarifying inputs, supporting dependency conversations, and enabling effective participation.
PI Planning aligns all teams on the ART around a common mission, shared objectives, dependencies, and a plan for the PI.
Topic: Defining the Scrum Master / Team Coach Role
A Scrum Master / Team Coach is helping an Agile team improve its working agreements after a tense iteration retrospective. Which behavior best represents productive disagreement rather than destructive conflict?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Productive disagreement improves decisions by making assumptions visible while keeping respect and collaboration intact. The Scrum Master / Team Coach supports this through facilitation and working agreements that help the team debate ideas without attacking people.
Productive disagreement is healthy conflict focused on better outcomes. In a SAFe Agile team, the Scrum Master / Team Coach helps the team create conditions where members can challenge assumptions, use data, listen actively, and follow an agreed decision process. Destructive conflict shifts from the work to the people, reduces trust, or blocks team flow. The key distinction is not whether disagreement exists; it is whether the disagreement improves shared understanding and decision quality while maintaining psychological safety.
Productive disagreement focuses on the work, uses evidence, and preserves collaboration through clear decision-making agreements.
Topic: Defining the Scrum Master / Team Coach Role
A leader asks the Scrum Master/Team Coach, “Can you guarantee this feature will be done by next Friday?” The team has unresolved dependencies and limited data. Which response is strongest?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: The Scrum Master/Team Coach should coach transparency and honest forecasting when certainty is not available. A useful response gives the leader the current view, assumptions, risks, and how the team will reduce uncertainty next.
The core concept is transparency in empirical work. When a leader asks for certainty the team cannot honestly provide, the Scrum Master/Team Coach should not create a false commitment. The stronger response is to make the current forecast visible, explain the assumptions and risks, and identify what the team will learn or resolve next. This helps stakeholders make decisions while protecting team integrity and realistic planning. The key takeaway is to replace false precision with transparent, inspectable information.
This response preserves transparency by providing useful information without pretending the team has certainty it does not have.
Topic: Introducing Scrum in SAFe
A Scrum Master / Team Coach is reviewing how a new Agile team is using its events. Which observation most clearly shows that an event is being used for the wrong purpose?
Best answer: C
What this tests: Introducing Scrum in SAFe
Explanation: The iteration retrospective is being used for the wrong purpose because it is focused on showing completed work to stakeholders. In Scrum and SAFe team events, that feedback and demonstration activity belongs in the iteration review, while the retrospective focuses on improving how the team works.
Team events have distinct purposes even when the same people may attend several of them. Iteration planning helps the team commit to an achievable iteration goal and work plan. The team sync inspects current progress and blockers. Backlog refinement prepares upcoming work with the Product Owner. The iteration review demonstrates completed work and gathers feedback from stakeholders. The iteration retrospective is different: it is a team improvement event where the team reflects on its process, collaboration, quality, and actions for the next iteration. Using it mainly as a stakeholder demo removes the improvement focus and duplicates the review.
A retrospective is for team improvement, while demonstrating completed work to stakeholders belongs in the iteration review.
Topic: Defining the Scrum Master / Team Coach Role
During Iteration 2, a Scrum Master / Team Coach reviews this action log after a team sync. The team says, “We are self-managing, so we do not need to discuss this outside the team.” What is the best interpretation and next action?
Improvement action log
- Goal: reduce checkout API cycle time
- Team decision: rename response fields this iteration
- Expected benefit: 1 day less mapping work
- Dependency: Mobile team consumes current API
- PI objective: 'Enable mobile checkout beta'
- PO note: beta scope assumes stable API contract
- Status: work started, no cross-team review
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Healthy team autonomy operates within shared ART alignment. The exhibit shows a local technical decision that may disrupt a dependency and a PI Objective, so the Scrum Master / Team Coach should help the team coordinate before continuing.
Self-management means the team owns how it does the work, but not in isolation from commitments, dependencies, and customer outcomes. Here, renaming API fields may be a valid improvement, but the exhibit shows the Mobile team depends on the current API and the PI Objective assumes a stable contract. The Scrum Master / Team Coach should coach the team to make the impact visible and facilitate alignment with the Product Owner and affected team. The key takeaway is that autonomy is healthy when local decisions remain connected to ART-level objectives and dependencies.
The decision affects a known dependency and PI Objective, so the team should align with affected stakeholders while retaining ownership of the solution.
Topic: Supporting Team Events
An Agile team is preparing for its Iteration Review. The Scrum Master / Team Coach reviews the draft agenda and wants to improve alignment with the event’s purpose.
Exhibit: Draft agenda
- Scrum Master reports velocity and defect trends
- Team lists stories marked Done
- Product Owner announces accepted stories
- Stakeholders attend if time allows
- Remaining time used for next-iteration task estimates
What is the best coaching suggestion?
Best answer: A
What this tests: Supporting Team Events
Explanation: The Iteration Review is not mainly a status meeting or planning session. Its purpose is to inspect the value delivered in the iteration, typically through a demo of completed work, and gather feedback from stakeholders for future backlog decisions.
In SAFe team events, the Iteration Review provides transparency about what the team actually delivered and creates a feedback loop with stakeholders and the Product Owner. The exhibit overemphasizes reporting, acceptance announcements, and task estimating while making stakeholder participation optional. A better agenda would center on demonstrating completed, working stories, discussing whether the iteration goals were met, and capturing feedback that can influence backlog refinement and upcoming priorities.
The key takeaway is that the review validates value and learning; it is not a substitute for the retrospective or iteration planning.
The Iteration Review should inspect delivered value through working results and use stakeholder feedback to inform future backlog decisions.
Topic: Supporting ART Events
During the Inspect and Adapt event, an ART identifies a recurring quality issue that crossed several team boundaries. In the problem-solving workshop, what is the best contribution from a Scrum Master / Team Coach?
Best answer: A
What this tests: Supporting ART Events
Explanation: The problem-solving workshop is part of Inspect and Adapt and focuses on collaborative, systemic improvement. A Scrum Master / Team Coach contributes by facilitating structured root-cause analysis and helping participants define clear improvement actions, not by taking over ownership or backlog authority.
In a SAFe Inspect and Adapt problem-solving workshop, the Scrum Master / Team Coach serves the group by improving the quality of collaboration and learning. For a cross-team quality issue, that means helping the ART examine facts, identify root causes, avoid blame, and create practical improvement backlog items or action items. The role is facilitative and coaching-oriented: make the work visible, keep the conversation focused, and help the right people participate.
Approval authority, backlog prioritization, and task assignment belong to other roles or to the team’s self-management. The key takeaway is that the Scrum Master / Team Coach enables effective problem solving rather than owning the solution decision.
The Scrum Master / Team Coach helps the group use structured problem-solving to identify causes and agree on actionable improvements.
Topic: Supporting ART Events
In PI Planning preparation, what best describes how the Scrum Master / Team Coach helps an Agile team get ready without taking over the team’s planning responsibilities?
Best answer: C
What this tests: Supporting ART Events
Explanation: The Scrum Master / Team Coach helps the team prepare for PI Planning by enabling good collaboration, readiness, and visibility. They do not become the owner of team planning, capacity decisions, backlog priority, or PI Objective content.
The core concept is servant leadership during PI Planning preparation. The Scrum Master / Team Coach helps the team understand the event, prepare to participate, identify needed inputs, and make dependencies or impediments visible. They may facilitate conversations, coach the team on effective preparation, and coordinate with the RTE or other teams when needed. However, the Agile team still owns its plan, the Product Owner owns backlog ordering and content decisions, and the team collaborates to draft PI Objectives during PI Planning. The key takeaway is that the Scrum Master enables team readiness rather than becoming the team’s planner.
The Scrum Master / Team Coach enables preparation by facilitating, coaching, and helping the team surface dependencies while the team owns its planning work.
Topic: Supporting Team Events
During iteration planning preparation, a Scrum Master reviews the team’s notes. The backlog is refined, but the plan assumes the team’s normal velocity. It does not mention two days of test-environment downtime, a production-support rotation, or planned vacations. What is the best interpretation of this situation?
Best answer: B
What this tests: Supporting Team Events
Explanation: The issue is not backlog refinement alone; it is missing capacity and constraint information. Iteration planning depends on realistic availability, known interruptions, and limiting conditions so the team can select achievable work.
In iteration planning, the Agile team should consider its actual capacity, not just historical velocity or a full backlog. Planned vacations, support duties, and unavailable environments can reduce the team’s ability to deliver during the iteration. The Scrum Master / Team Coach helps surface these factors early so the team and Product Owner can discuss trade-offs, adjust scope, and make risks visible before the plan is accepted.
A refined backlog is helpful, but it does not replace explicit capacity and constraint discussion.
Iteration planning needs explicit team availability and constraints so the team can make a realistic plan.
Topic: Supporting ART Events
Several Agile teams arrive at pre-PI coaching with unclear capacity, unrefined top features, and no known dependency notes. They say they can “figure it all out during PI Planning.” What is the best Scrum Master / Team Coach response?
Best answer: B
What this tests: Supporting ART Events
Explanation: The Scrum Master / Team Coach supports PI Planning readiness by helping the team prepare key inputs before the event. Self-organization does not mean arriving without capacity awareness, backlog understanding, or dependency visibility.
For PI Planning preparation, the Scrum Master / Team Coach helps the Agile team become ready to participate effectively in the ART event. That includes coaching the team to understand candidate work, know its capacity, identify likely dependencies, and surface questions early. PI Planning is where teams collaborate, negotiate, align, and commit to PI Objectives; it should not be used as the first moment to discover all basic planning inputs.
The key takeaway is to enable team ownership through preparation, not replace team planning with either improvisation or top-down assignment.
PI Planning is most effective when teams arrive with enough preparation to create and align plans, not discover all inputs live.
Topic: Supporting ART Events
During PI Planning, two Agile teams are preparing for the draft plan review. A Scrum Master/Team Coach checks the shared planning notes near the end of the breakout.
Exhibit: Planning notes excerpt
Team Atlas: Objective A needs API v2 from Team Nova in Iteration 2.
Team Nova: API v2 planned for Iteration 4; no dependency recorded.
Team Atlas risk: "Integration date unclear."
Team Nova risk: "No known cross-team dependencies."
Business Owner question: "Which demo shows the end-to-end flow?"
Draft plan review starts in 15 minutes.
What is the best interpretation and next action?
Best answer: C
What this tests: Supporting ART Events
Explanation: The exhibit shows a shared-information breakdown, not just an execution risk. Atlas and Nova have different assumptions about the same dependency, so event flow should be adjusted to make the dependency visible and align the teams before the draft plan review.
In PI Planning, healthy event flow depends on teams sharing assumptions, dependencies, risks, and objective impacts early enough to adjust plans. Here, Atlas is planning an Iteration 2 dependency while Nova is planning Iteration 4 and does not even see a dependency. The Scrum Master/Team Coach should facilitate a short cross-team conversation so both teams can update their plans, risks, and PI Objective notes before presenting an inconsistent draft plan.
The key takeaway is to improve shared understanding and transparency, not to force a date or hide the issue until later.
The notes show mismatched assumptions, so the Scrum Master/Team Coach should help the teams create shared information before the plan review.
Topic: Introducing Scrum in SAFe
In a SAFe Agile Team, who is primarily responsible for owning and prioritizing the Team Backlog so the team works on the most valuable stories next?
Best answer: D
What this tests: Introducing Scrum in SAFe
Explanation: The Product Owner is accountable for Team Backlog content, ordering, and value focus. The Scrum Master / Team Coach facilitates and removes impediments, while Developers decide how to build the work.
In Scrum within SAFe, role clarity helps the Agile Team make fast decisions without shifting accountability. The Product Owner owns and prioritizes the Team Backlog, clarifies story intent, and helps ensure the team works on valuable outcomes. The Scrum Master / Team Coach supports flow, facilitation, coaching, and impediment removal. Developers are accountable for creating the working increment and managing the technical approach to meet the iteration goals. The key distinction is value ordering versus facilitation versus delivery execution.
The Product Owner owns and prioritizes the Team Backlog to maximize value delivered by the Agile Team.
Topic: Defining the Scrum Master / Team Coach Role
A Scrum Master/Team Coach is comparing observations from the last three iterations to decide where coaching is most needed. Which pattern is the strongest coaching signal about the Agile team’s participation, quality, and predictability?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Coaching signals are strongest when they show a repeated pattern across how the team collaborates and delivers. Uneven participation, rising defects, and increasing carryover indicate issues in team interaction, quality practices, and predictability that a Scrum Master/Team Coach should help the team inspect and improve.
The Scrum Master/Team Coach looks for patterns, not isolated data points. A trend where only a few people participate while defects and unfinished work increase suggests the team may not be using events effectively, may have hidden knowledge silos, and may be struggling to make reliable iteration commitments. That is a direct coaching opportunity for facilitation, team working agreements, quality practices, and retrospective improvement actions. A single dependency may need escalation or ART coordination, and stakeholder feedback may improve review facilitation, but neither is as broad a signal of team coaching need as the combined participation-quality-predictability pattern.
This combines weak participation with worsening quality and predictability, making it a strong coaching signal.
Topic: Defining the Scrum Master / Team Coach Role
A new Scrum Master/Team Coach asks why SAFe emphasizes team health instead of focusing only on velocity. Which statement best explains why team health matters to predictability and sustainable delivery?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Team health matters because predictable delivery depends on more than output measures. A healthy Agile team can raise impediments, collaborate across skills, and improve its system of work without burnout.
In the Scrum Master/Team Coach role, team health is a leading condition for reliable delivery. When trust, collaboration, psychological safety, and improvement habits are strong, the team is more likely to surface blockers early, manage dependencies honestly, and adapt its plan before small issues become missed objectives. This improves predictability because the team’s forecasts are based on real capacity and visible risks. It also supports sustainability because the team is not relying on heroics, overcommitment, or hidden overtime to meet goals.
Velocity can be useful, but it is an outcome indicator. Team health helps create the conditions that make useful, repeatable outcomes possible.
Team health supports trust, transparency, and continuous improvement, which reduce surprises and help the team deliver sustainably.
Topic: Supporting ART Events
Before PI Planning, a Scrum Master/Team Coach notices that several top backlog items are too vague for estimation and the team’s draft PI Objectives do not reflect clear business outcomes. Which pre-PI Planning action best supports ART readiness?
Best answer: D
What this tests: Supporting ART Events
Explanation: The Scrum Master/Team Coach supports PI Planning readiness by helping the team and Product Owner clarify work before the event. When backlog items or objectives are unclear, the best action is to facilitate refinement and alignment, not take over content ownership.
A Scrum Master/Team Coach helps the Agile team prepare for PI Planning by enabling effective backlog refinement, surfacing unclear work, and connecting the right people for clarification. The Product Owner remains accountable for backlog content and prioritization, while the team contributes estimates, questions, and technical insight. If draft PI Objectives lack clear outcomes, the Scrum Master can coach the team and PO to improve clarity before planning begins. This reduces wasted PI Planning time and improves alignment with ART priorities.
The key takeaway is that the Scrum Master facilitates readiness and collaboration; they do not personally define backlog content or assign team objectives.
This helps clarify backlog intent and draft objectives while keeping content ownership with the Product Owner and team.
Topic: Supporting ART Events
During PI Planning, an Agile team realizes its draft plan cannot support the highest ART priorities because a major dependency and capacity trade-off are unresolved. Which PI Planning activity is specifically intended to help resolve this kind of issue so the plan can align with ART priorities?
Best answer: D
What this tests: Supporting ART Events
Explanation: Management review and problem-solving is the PI Planning activity used when team plans reveal issues that require broader decisions. It helps resolve priority, scope, dependency, and capacity conflicts so teams can revise plans toward ART alignment.
In PI Planning, teams create draft plans and surface risks, dependencies, and capacity constraints. When a team cannot align its plan with ART priorities due to unresolved trade-offs, the issue should be made visible and addressed in management review and problem-solving. This gives the right stakeholders a chance to adjust scope, priorities, resources, or sequencing before teams finalize plans and PI Objectives.
The key is not for the Scrum Master / Team Coach to force a local team commitment. The stronger response is to use the PI Planning flow to escalate and resolve the impediment collaboratively.
This activity addresses major scope, dependency, capacity, and priority issues that prevent teams from aligning their PI plans.
Topic: Introducing Scrum in SAFe
During iteration planning, an Agile team reviews its team backlog, current capacity, and the PI Objectives agreed to during PI Planning. Which statement best describes how this team-level planning connects to broader ART objectives?
Best answer: D
What this tests: Introducing Scrum in SAFe
Explanation: Team-level planning connects to ART objectives by translating PI Planning intent into executable iteration work. The team uses capacity and backlog priorities to plan near-term progress while making dependencies and risks visible across the ART.
In SAFe, PI Objectives express what teams intend to accomplish during the PI in support of the ART’s broader goals. Iteration planning does not redefine those objectives; it breaks the work into a realistic short-term plan based on capacity, priorities, and the team backlog. This helps the team make incremental progress toward its PI Objectives and gives the ART visibility into dependencies, impediments, and risks that may affect the larger plan.
The key mapping is from ART-level alignment in PI Planning to team-level execution in each iteration.
Iteration planning turns PI-level intent into near-term team commitments while keeping dependencies visible to the ART.
Topic: Supporting Team Events
During backlog refinement, a Scrum Master/Team Coach reviews the team’s candidate backlog items for the next iteration. What is the best next action to support readiness for healthy flow?
Exhibit: Refinement notes
BI-214: "Improve checkout experience"
- No acceptance criteria yet
- Touches web, mobile, payments, and vendor API
- Vendor API availability not confirmed
BI-219: Add profile field; AC clear; 2 points
BI-221: Update help text; AC clear; 1 point
Largest item finished last iteration: 5 points
Best answer: D
What this tests: Supporting Team Events
Explanation: BI-214 is not ready for smooth flow because it lacks acceptance criteria, spans several areas, and has an unresolved vendor dependency. The Scrum Master/Team Coach should help the team refine it into clearer, smaller, lower-risk backlog items before planning.
Backlog refinement supports healthy flow by making work understandable, appropriately sized, and low enough in risk for the team to pull with confidence. In the exhibit, BI-214 is too vague because it has no acceptance criteria, too large because it spans multiple systems compared with the team’s recent completed item size, and risky because a vendor API dependency is not confirmed. A good next action is to facilitate refinement: clarify outcomes and acceptance criteria, split the item, and make the dependency visible for follow-up. High value alone does not make an item ready to enter an iteration.
BI-214 is vague, large, and risky, so refinement should make it smaller, clearer, and expose the dependency before iteration planning.
Topic: Defining the Scrum Master / Team Coach Role
A Scrum Master / Team Coach is updating the team’s impediment log. Which entry best represents a systemic cross-team or organizational blocker rather than a local team impediment?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: A systemic blocker is an impediment that one team cannot reasonably resolve on its own because it affects multiple teams, a shared service, or an organizational constraint. The unavailable shared environment creates cross-team impact and should be made visible beyond the local team.
The core distinction is scope and ownership. A local team impediment is usually within the Agile team’s ability to address through collaboration, coaching, or normal team-event follow-up. A systemic blocker crosses team boundaries or depends on organizational decisions, shared infrastructure, external groups, or ART-level coordination. The Scrum Master / Team Coach helps make these blockers visible, supports resolution, and escalates through appropriate channels when the team lacks authority or capacity to fix them alone. A shared environment used by three teams is not just a single-team workflow issue; it can affect dependencies, PI Objectives, and ART predictability.
The key takeaway is to look for cross-team impact and resolution authority, not just whether the issue is inconvenient.
A shared constraint affecting multiple teams requires broader ART visibility and likely escalation beyond one Agile team.
Topic: Introducing Scrum in SAFe
During PI Planning, an ART is discussing a new customer onboarding capability. Which plan most clearly shows the work is being organized as a one-time handoff rather than ongoing value delivery?
Best answer: D
What this tests: Introducing Scrum in SAFe
Explanation: The key discriminator is whether work is passed once between specialized groups or delivered incrementally by teams that learn from feedback. A full specification handed from design to development is a handoff pattern. Incremental delivery keeps feedback loops active through working slices and reviews.
Agile development in SAFe emphasizes empirical learning and incremental value delivery. Work should be sliced so Agile teams can build, integrate, review, and adapt based on feedback. A one-time handoff appears when one group completes a large batch of work, such as a final specification, and transfers it to another group to execute. That delays learning and increases the risk that assumptions remain untested until late. Identifying dependencies or changing priorities after review can still support incremental delivery when the teams keep feedback and integration flowing.
Completing a full design package and passing it to another group separates discovery from delivery as a handoff instead of enabling incremental learning.
Topic: Supporting ART Events
Two Agile teams on the same ART are planning related features for the next few Iterations. Each team has a local plan, but neither team has made its dependency timing visible to the other. As the Scrum Master / Team Coach, which guidance best explains why cross-team transparency matters most in this situation?
Best answer: A
What this tests: Supporting ART Events
Explanation: Cross-team transparency is valuable because it reveals dependency timing, risks, and sequencing constraints across the ART. When teams can see each other’s plans early, they can adjust order, capacity, and conversations before hidden dependencies disrupt flow.
In SAFe, Agile teams remain accountable for their own plans, but ART-level collaboration helps them see how their work affects other teams. Making dependencies visible during cross-team coordination supports better sequencing because teams can compare timing, negotiate handoffs, and raise impediments before they become urgent surprises. This is especially important when features require multiple teams to deliver in a specific order.
The key is not centralized task assignment or protecting local plans. The Scrum Master / Team Coach helps create transparency and facilitates the conversations needed for teams to coordinate flow across the ART.
Cross-team visibility helps teams align order of work and address dependency risks before they become late surprises.
Topic: Supporting Team Events
During an Iteration Review, an Agile team follows a tightly rehearsed demo script approved by the Product Owner. Stakeholders give only polite comments, and a dependent team says they still cannot tell whether the new API behavior will support their upcoming work. As the Scrum Master / Team Coach, what is the best action?
Best answer: C
What this tests: Supporting Team Events
Explanation: The Iteration Review is meant to inspect the working solution and gather feedback, not simply deliver a polished presentation. When the script prevents stakeholders and dependent teams from validating real behavior, the Scrum Master should facilitate more direct interaction with the solution.
The core concept is event effectiveness: an Iteration Review should reveal learning through feedback on a working increment. A rehearsed script can be useful for flow, but it becomes an anti-pattern when it prevents discovery, hides uncertainty, or leaves dependency questions unanswered. The Scrum Master / Team Coach should improve the event by creating space for real stakeholder questions, probing scenarios, and discussion of what was learned from the demonstrated work. This respects role boundaries because the Product Owner still owns content priorities, while the Scrum Master facilitates a better inspection-and-feedback environment. Deferring the concern or making the demo more passive would not address the missed learning opportunity.
A less scripted, working-solution-based discussion helps reveal actual learning, integration issues, and actionable feedback.
Topic: Supporting ART Events
During the first team breakout in PI Planning, three Agile teams discover they are making different assumptions about a shared authentication service. Their draft PI Objectives are stalled, and no dependency has been captured on the ART planning board. What should the Scrum Master/Team Coach do next?
Best answer: D
What this tests: Supporting ART Events
Explanation: PI Planning flow breaks down when teams lack shared information needed to make realistic plans. The Scrum Master/Team Coach should help affected teams clarify assumptions, involve the right ART participants, and capture the dependency before planning continues too far.
The core issue is not that one team needs a local task adjustment; multiple teams lack the same shared information. In PI Planning, the Scrum Master/Team Coach supports event flow by helping the team surface dependencies and get timely clarification from the relevant teams, Product Owners, System Architect, or RTE as needed. A quick cross-team huddle prevents each team from building plans on conflicting assumptions and allows the dependency to be recorded on the ART planning board. The key takeaway is to restore shared understanding before teams finalize objectives or commitments.
The next step is to create shared understanding quickly and make the dependency visible so planning can continue.
Topic: Supporting Team Events
During the iteration retrospective, an Agile team raises the same build-environment problem for the third iteration in a row. A previous improvement action was recorded, but no one followed up, and the issue is now delaying stories that support a PI Objective. What is the best Scrum Master / Team Coach response?
Best answer: C
What this tests: Supporting Team Events
Explanation: A recurring issue without action indicates a breakdown in improvement follow-through, not just a technical problem. The Scrum Master / Team Coach should facilitate team ownership by making the action specific, visible, and tracked so it is inspected in the next cycle.
The iteration retrospective is where the team inspects how it worked and identifies practical improvements. When the same issue reappears, the Scrum Master should not let the team simply restate the problem again. The better response is to help the team define a small improvement item, clarify who will drive follow-up, make dependencies visible, and ensure the item is reviewed during the next iteration. Because the issue affects a PI Objective, it may also need ART visibility if the team cannot resolve the dependency alone, but the first Scrum Master move is to restore disciplined improvement follow-through. The key takeaway is to facilitate accountability and transparency, not take over the work or ignore the pattern.
The Scrum Master should help the team turn the repeated issue into a visible, accountable improvement action and inspect follow-through.
Topic: Defining the Scrum Master / Team Coach Role
During the last two iterations, an Agile team has carried over several stories because dependency questions with another team were raised late. In team syncs, two senior developers dominate the discussion, and action items often have no owner. The Product Owner asks the Scrum Master / Team Coach to “make people accountable.” What is the best action for the Scrum Master / Team Coach?
Best answer: A
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Working agreements are a practical way to support self-management and team health. In this situation, the Scrum Master / Team Coach should facilitate the team in defining explicit collaboration norms, such as balanced participation, dependency follow-up, and action-item ownership.
A Scrum Master / Team Coach supports collaboration and accountability by helping the team create and inspect its own working agreements. The issue is not only missed tasks; it is a pattern of unclear norms around participation, ownership, and dependency management. A working agreement refresh lets the team decide how it will run team syncs, record action items, surface dependencies earlier, and hold itself accountable. This preserves role boundaries because the Scrum Master facilitates the process rather than becoming the task assigner or disciplinarian.
The key takeaway is that accountability in Agile teams is strengthened through transparent agreements owned by the team, not imposed control.
Working agreements help the team define shared behaviors for collaboration, ownership, and dependency follow-through without the Scrum Master assigning work.
Topic: Defining the Scrum Master / Team Coach Role
An Agile team is carrying over work for the third Iteration. During the team sync, several developers wait for the Scrum Master / Team Coach to tell them which stories to take next. What response best reflects a servant-leader stance rather than a task-manager stance?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: The Scrum Master / Team Coach serves the team by improving collaboration, transparency, and self-management. In this scenario, the key discriminator is whether the response helps the team own its work instead of shifting task assignment to another role.
In SAFe, the Scrum Master / Team Coach is a servant leader who helps the Agile team become more effective. That includes facilitating events, coaching collaboration, surfacing impediments, and encouraging team ownership of commitments. The role does not direct individual assignments as a task manager would. When a team waits to be told what to do next, the better coaching move is to facilitate a conversation about priorities, capacity, flow, and blockers so the team can decide how to proceed. The Product Owner owns backlog priority, but not daily task assignment. The RTE supports the ART, but routine team self-management should not be escalated as reassignment work.
A servant leader enables the team to self-manage work while making impediments and priorities visible.
Topic: Defining the Scrum Master / Team Coach Role
In a SAFe Agile team, members have stopped raising impediments in team sync, seem overloaded, and avoid discussing tension during retrospectives. Which concept do these signals most directly indicate?
Best answer: A
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: These behaviors point to a team health issue because they show stress, reduced psychological safety, and avoidance of important collaboration. The Scrum Master / Team Coach should recognize these signals and help the team make the issue visible and addressable.
Team health is reflected in how safely and sustainably the team collaborates, not just in whether work is moving across the board. When team members stop raising impediments, appear overloaded, or avoid conflict in retrospectives, the Scrum Master / Team Coach should recognize a potential health issue and facilitate transparency, inspection, and improvement. The focus is not to diagnose individuals, but to help the team surface what is happening and create improvement actions. A backlog or planning issue may contribute, but the described signals are broader collaboration and sustainability concerns.
Low morale, overload, and avoidance are warning signs that the Scrum Master / Team Coach should treat as a team health concern.
Topic: Introducing Scrum in SAFe
During backlog refinement, an Agile team discovers new customer feedback that changes the expected value of two upcoming stories. A developer says, “We already planned the PI, so the backlog should stay fixed.” What should the Scrum Master / Team Coach emphasize about the backlog?
Best answer: D
What this tests: Introducing Scrum in SAFe
Explanation: The backlog represents the team’s current best understanding of planned value, not a fixed contract. As customer feedback, dependencies, and learning emerge, the Product Owner and team refine and reorder backlog items to maximize value delivery.
In Scrum and SAFe, the backlog is an evolving, ordered source of planned value. PI Planning creates alignment and objectives, but it does not freeze all future backlog decisions. When new customer feedback changes value assumptions, the team should inspect that learning and refine the backlog accordingly. The Scrum Master / Team Coach helps the team understand this adaptive purpose while supporting collaboration with the Product Owner.
The key takeaway is that backlog refinement protects value delivery by keeping planned work aligned with current learning.
The backlog is an ordered, continuously refined source of planned value that adapts as new information emerges.
Topic: Supporting Team Events
During recent team syncs, each developer gives a brief update to the Scrum Master / Team Coach, says “no blockers,” and then goes quiet. The team board shows aging stories, QA handoffs waiting, and a dependency on another team that is only discussed after the sync. What is the best next step for the Scrum Master / Team Coach?
Best answer: A
What this tests: Supporting Team Events
Explanation: A team sync should help the Agile team coordinate work, manage flow, and surface blockers. When participants only report to the Scrum Master / Team Coach and do not discuss visible risks on the board, participation is too passive to support coordination.
The core issue is not the existence of updates; it is that the event has become a status report to one person instead of a coordination event for the team. The Scrum Master / Team Coach should facilitate the team using the board or other flow visualizations, prompting discussion about aging work, handoffs, blockers, and dependencies. This helps team members talk to each other and decide what needs attention next.
Escalation may be needed later for dependencies the team cannot resolve, but the first facilitation step is to make the work and blockers visible in the team sync and help the team coordinate around them.
The event should shift from passive status reporting to team-led coordination around flow, blockers, and dependencies.
Topic: Defining the Scrum Master / Team Coach Role
A Scrum Master / Team Coach encourages an Agile team to review progress against the Iteration Goal together, swarm on blocked stories, and adjust work as a team instead of reporting only individual task status. Which concept is this primarily reinforcing?
Best answer: D
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: The core concept is collective ownership of outcomes. A Scrum Master / Team Coach reinforces it by shifting attention from individual status to the team’s shared goal, impediments, and commitment to deliver value together.
Collective ownership means the Agile team treats commitments and outcomes as shared responsibilities, not as isolated assignments owned only by individuals. In the stem, reviewing the Iteration Goal, swarming on blocked stories, and adjusting the plan together all help the team self-manage around value delivery. This supports team health because members make progress visible, help each other, and focus on meeting the shared goal rather than optimizing personal task completion. The closest trap is individual task accountability, which can be useful but does not by itself create shared ownership of the outcome.
Shared review, swarming, and team-level adjustment reinforce that the whole team owns commitments and results.
Topic: Introducing Scrum in SAFe
A Scrum Master reviews the notes from a team’s Iteration Retrospective before the next Iteration Planning event.
Exhibit: Retrospective notes
Event: Iteration Retrospective
Discussed: testing delays, long PR queues, handoff confusion
Decisions: "Collaborate better" and "Improve quality"
Owner: not assigned
Target Iteration: not recorded
Follow-up: not scheduled
What is the best next action supported by the exhibit?
Best answer: C
What this tests: Introducing Scrum in SAFe
Explanation: The exhibit shows a retrospective that identified useful issues but did not produce a specific improvement outcome. The Scrum Master should help the team turn those themes into owned, time-bound improvement actions that can be inspected in the next Iteration.
Each team event has a purpose and should produce an outcome that supports flow and learning. For an Iteration Retrospective, the expected outcome is not just conversation about problems; it is one or more practical improvement actions the team agrees to try, with ownership and follow-up. The notes show vague statements with no owner, target Iteration, or inspection point. The Scrum Master should coach the team to make the improvement concrete enough to act on and review later.
The key takeaway is that healthy events convert discussion into the event’s intended outcome.
A retrospective should produce concrete, trackable improvement actions, not only broad discussion themes.
Topic: Defining the Scrum Master / Team Coach Role
During backlog refinement, a Scrum Master / Team Coach reviews the team’s facilitation notes and wants to decide how to support the next discussion.
Exhibit: Facilitation notes
Topic: Split the API security story
Dev A: "Versioning risk needs design time."
Tester: "Let's compare recent defect data."
Dev B: "Ops always blocks us anyway."
Two people were interrupted twice.
No decision; quieter members stopped contributing.
What is the best interpretation and next action?
Best answer: C
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: Productive disagreement focuses on evidence, risks, and decision quality. The exhibit also shows destructive conflict signals: blame, interruptions, and withdrawal from quieter members. The Scrum Master should facilitate the conversation back to working agreements without suppressing the useful technical debate.
The core concept is distinguishing debate about the work from behavior that damages collaboration. Comments about versioning risk and defect data are productive because they help the team evaluate options. The statement blaming Ops, repeated interruptions, and loss of participation are signs the interaction is becoming destructive. A Scrum Master / Team Coach supports the team by making the pattern visible, using working agreements, and helping the group reframe concerns into actionable risks or dependencies.
The key takeaway is to preserve constructive disagreement while intervening on behaviors that reduce trust, safety, or participation.
The notes show useful technical disagreement mixed with blaming and interruptions, so the Scrum Master should protect collaboration while keeping the decision-focused debate.
Topic: Introducing Scrum in SAFe
A department forms a temporary group to build a reporting feature. Analysts collect requirements, developers code for several weeks, then the work is handed to a separate testing and release group before the temporary group disbands. What is this practice best illustrating?
Best answer: C
What this tests: Introducing Scrum in SAFe
Explanation: The described practice is organized around a temporary effort and sequential handoffs. In SAFe Scrum, Agile teams are intended to deliver value incrementally and learn continuously, rather than pass work through one-time specialist stages.
The core concept is the difference between phase-based handoffs and ongoing value delivery. A temporary group that gathers requirements, codes, hands work to another group for testing and release, and then disbands is not acting like a stable Agile team delivering incremental value. It resembles a project or waterfall-style handoff model, where feedback and accountability are delayed across functional boundaries.
Long-lived Agile teams reduce these delays by owning delivery, integration, quality, and learning across iterations. The key takeaway is that repeated value delivery needs stable team ownership, not a one-time transfer of partially completed work.
The work is structured as sequential phases and transfers rather than ongoing delivery by a long-lived Agile team.
Topic: Supporting ART Events
During PI Planning, Team Atlas has a draft PI Objective that requires an API endpoint from Team Beacon by Iteration 3. Beacon owns the endpoint work, but the delivery date is not yet confirmed. The RTE asks teams to make cross-team needs visible before the draft plan review. What is the best action for the Scrum Master / Team Coach?
Best answer: B
What this tests: Supporting ART Events
Explanation: A dependency exists when one team needs something from another team to complete its work. Here, Atlas depends on Beacon’s API endpoint, so the Scrum Master / Team Coach should help make that dependency visible and coordinate timing during PI Planning.
In PI Planning, dependencies should be identified, visualized, and coordinated so teams can create realistic plans and PI Objectives. Atlas does not merely have an uncertain event; it has a specific need for work owned by Beacon. The best response is to record the cross-team dependency, clarify the needed-by iteration, and facilitate discussion between the teams. If the date uncertainty creates potential impact, that may also become a risk, but the primary classification is still a dependency. The key takeaway is to first identify what the item is, then use the right ART mechanism to manage it.
Atlas needs work owned by another team, so the Scrum Master / Team Coach should make the dependency visible and facilitate alignment.
Topic: Introducing Scrum in SAFe
An Agile team released a small payment-flow change during the iteration using the ART’s release-on-demand pipeline. Within a day, production telemetry and user comments show that customers are abandoning the flow at a new confirmation step. What should the Scrum Master / Team Coach do next?
Best answer: C
What this tests: Introducing Scrum in SAFe
Explanation: Fast feedback matters because it lets the team learn whether a released change is creating the intended user value. The Scrum Master / Team Coach should help the team and Product Owner inspect the evidence quickly and decide what to adapt next.
In SAFe, DevOps and release on demand help teams get real evidence from production and users sooner. When feedback shows a possible value or usability problem, the next step is not to wait for a later ART event or escalate ownership away from the team. The Scrum Master / Team Coach facilitates transparency and learning by helping the Agile team and Product Owner review the data, understand the impact, and adapt the backlog or next work items as appropriate.
The key takeaway is that fast feedback closes the loop between delivery and value, enabling the team to adjust before more effort is spent in the wrong direction.
Fast production and user feedback should be inspected quickly so the team and PO can adapt work toward customer value.
Topic: Supporting Team Events
During the daily team sync, most Agile team members listen silently while the Scrum Master / Team Coach asks each person for a status update. Dependencies are being discovered late, and the team often leaves without clear coordination. What is the best next step to improve the event?
Best answer: B
What this tests: Supporting Team Events
Explanation: A healthy team sync is not passive attendance or a status meeting for the Scrum Master. The Scrum Master / Team Coach should facilitate team-owned coordination so members inspect progress, surface blockers, and adjust together.
The core concept is event participation that improves outcomes. In this scenario, the anti-pattern is that team members are reporting to the Scrum Master instead of coordinating with one another. The best next step is to change the facilitation stance: use the team board or iteration goal as the focus, ask members to identify work flow issues and dependencies, and help the team decide immediate follow-up actions. This keeps accountability with the Agile team while the Scrum Master / Team Coach enables better collaboration. Escalation to the ART may be useful for cross-team impediments, but it should not replace healthy team-level participation.
This turns passive status reporting into active team collaboration around progress, blockers, and dependencies.
Topic: Defining the Scrum Master / Team Coach Role
An Agile team keeps losing time each Iteration because test environment access requires a manual approval. The Scrum Master helps get individual approvals expedited, but the same delay returns in later Iterations. Which concept best describes what this pattern indicates?
Best answer: A
What this tests: Defining the Scrum Master / Team Coach Role
Explanation: A recurring impediment is a strong sign of a systemic impediment when the team only applies temporary fixes. The manual approval process remains unchanged, so the same blocker predictably returns in later Iterations.
The core concept is a systemic impediment: a blocker caused by policies, structures, environments, handoffs, or dependencies outside the team’s immediate control. In this scenario, expediting one approval removes the immediate pain, but it does not change the approval process that creates the delay. A Scrum Master / Team Coach should help make the pattern visible, involve the right stakeholders, and escalate when the impediment requires ART or organizational action. The key signal is recurrence after short-term fixes, not merely that the team has a dependency.
The repeated delay after local workarounds shows the underlying system causing the impediment has not changed.
Topic: Introducing Scrum in SAFe
An Agile team on an ART adds automated build, integration, security tests, deployment scripts, and production monitoring to its workflow. Which statement best explains how this DevOps practice supports faster and safer delivery of value?
Best answer: A
What this tests: Introducing Scrum in SAFe
Explanation: DevOps in SAFe supports faster and safer delivery by improving the Continuous Delivery Pipeline. Automation, built-in validation, deployment capability, and monitoring reduce handoffs and risk while enabling smaller releases when the business is ready.
The core concept is that DevOps connects the people, practices, and automation needed to move value from idea to production more quickly and reliably. In the stem, automated builds, tests, deployment scripts, and monitoring directly strengthen the Continuous Delivery Pipeline. This supports release on demand because changes can be validated in smaller batches and deployed with less manual effort and less late-stage risk.
The key takeaway is that DevOps does not remove business accountability for release decisions; it improves the technical and flow capability to release safely when needed.
DevOps improves flow and safety by automating and validating changes through the delivery pipeline so value can be released on demand.
Topic: Supporting ART Events
An Agile team enters the IP Iteration with two unfinished stories from the last delivery iteration. A stakeholder asks the Product Owner to use the entire IP Iteration to finish and harden them for a promised demo. The RTE has scheduled Inspect and Adapt and PI Planning readiness activities, and the team has improvement experiments planned. As the Scrum Master/Team Coach, what is the best action?
Best answer: B
What this tests: Supporting ART Events
Explanation: The IP Iteration is for innovation, learning, Inspect and Adapt, and PI Planning readiness, not a routine extension of delivery iterations. The Scrum Master/Team Coach should help the team and Product Owner make unfinished work visible, negotiate responsibly, and preserve the ART-level purpose of the IP Iteration.
In SAFe, the IP Iteration provides capacity for work that supports the ART’s health and next planning cycle: innovation, improvement, continuing learning, Inspect and Adapt, and PI Planning readiness. Some carryover or urgent completion work may need discussion, but it should be made transparent and managed deliberately rather than treated as a normal iteration commitment. The Scrum Master/Team Coach helps facilitate this conversation across the team, Product Owner, and ART stakeholders so trade-offs are visible and the team does not silently consume the IP Iteration as a delivery buffer. The key distinction is that IP work supports readiness and improvement; regular delivery iterations are where committed feature work is planned and completed.
IP Iteration should not become a normal delivery commitment; the team should make carryover visible while protecting innovation, I&A, and PI Planning readiness.
Topic: Supporting ART Events
During PI Planning, an Agile team has identified dependencies and ROAMed several risks. The Scrum Master wants to avoid treating the plan as a guaranteed forecast while still surfacing whether the team believes the PI Objectives are achievable. Which SAFe practice best supports this healthy discussion?
Best answer: A
What this tests: Supporting ART Events
Explanation: A confidence vote is used to make delivery confidence visible, not to create false certainty. In PI Planning, low confidence should prompt discussion about risks, dependencies, scope, or needed adjustments before the plan is accepted.
The core concept is the PI Planning confidence vote. After teams review objectives, dependencies, and risks, the vote helps reveal whether the plan feels realistic enough to proceed. It is a facilitation mechanism for transparency and alignment, not a guarantee that every objective will be delivered exactly as planned. A Scrum Master/Team Coach should use the result to encourage honest discussion, especially when confidence is low or uneven across teams.
The key takeaway is that healthy confidence is evidence-based and transparent; false certainty ignores unresolved delivery concerns.
The confidence vote exposes whether participants believe the PI plan is achievable and triggers discussion when confidence is low.
Use the SAFe Scrum Master Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.