Try 10 focused SAFe Scrum Master questions on Supporting ART Events, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | SAFe Scrum Master |
| Topic area | Supporting ART Events |
| Blueprint weight | 28% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Supporting ART Events for SAFe Scrum Master. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 28% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Supporting ART Events
During PI Planning, a Scrum Master / Team Coach reviews this dependency note before the final plan review:
Dependency: API gateway hardening
Provider: Platform Team
Consumer: Payments Team
Needed by: Iteration 2
Current signal: Platform capacity full until Iteration 4
Impact: Payments Obj 2, Payments Obj 4, Retail Obj 3
Owner: Not assigned
What is the best next action?
Best answer: C
What this tests: Supporting ART Events
Explanation: The note shows an unresolved cross-team dependency that affects several PI objectives across the ART. The Scrum Master / Team Coach should help make the issue visible, facilitate coordination with affected teams and the RTE, and ensure ownership and risk handling are clear.
In PI Planning, dependencies that threaten multiple PI objectives should not remain a private team issue. The Scrum Master / Team Coach supports transparency and ART alignment by helping the team raise the dependency on the planning board, involve the provider and affected consumers, identify an owner, and coordinate with the RTE if the risk needs broader facilitation. The likely outcome may include replanning, sequencing changes, capacity trade-offs, or updating PI risks and objectives. The key is to enable ART-level problem solving, not to unilaterally command another team or hide the impact until later.
A dependency threatening multiple PI objectives should be surfaced for ART-level coordination, ownership, and plan adjustment.
Topic: Supporting ART Events
Two days before PI Planning, several Agile teams say they can “figure out the plan live.” The Scrum Master / Team Coach reviews the prep notes:
Pre-PI readiness notes
Top features: named, acceptance unclear
Dependencies: "TBD" for 3 shared services
Capacity: holidays not checked
Risks: none captured
Draft PI objectives: blank
PO availability: 30-minute sync today
What is the best coaching response supported by this exhibit?
Best answer: C
What this tests: Supporting ART Events
Explanation: PI Planning works best when teams arrive with enough preparation to collaborate effectively. The notes show unclear scope, unknown dependencies, unchecked capacity, and no draft objectives, so the Scrum Master / Team Coach should coach the team into a short preparation effort before the event.
The core concept is pre-PI coaching for team readiness. A Scrum Master / Team Coach does not create the plan for the team, but helps the team and Product Owner prepare enough to make PI Planning productive. In this case, the best next action is to use the available PO sync to clarify top features, identify likely dependencies, check capacity, surface risks, and draft initial PI objectives. The goal is not perfect certainty; it is enough shared understanding for meaningful planning and ART-level collaboration. Improvising everything live would consume PI Planning time with avoidable discovery work.
The exhibit shows readiness gaps that the team should reduce before PI Planning rather than discovering everything live.
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: B
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 ART Events
An ART is at the end of a PI. The RTE asks Scrum Masters/Team Coaches to help prepare an event where teams will review PI results, examine metrics and feedback, identify systemic issues, and create improvement backlog items. What best distinguishes this event from a routine status meeting?
Best answer: D
What this tests: Supporting ART Events
Explanation: Inspect and Adapt is an ART event for learning and improvement at the end of the PI. It uses results, metrics, feedback, and problem solving to identify systemic improvements, not simply to report current status.
Inspect and Adapt is different from a routine status meeting because its purpose is to improve the system of work across the ART. Teams review PI outcomes, inspect metrics and feedback, and participate in a problem-solving workshop to find root causes and define improvement backlog items. The emphasis is on transparency, learning, and actionable improvement, not on collecting progress reports or managing individual task assignments.
A status meeting may ask, “Where are we?” Inspect and Adapt asks, “What did we learn, and what should we improve next?”
Inspect and Adapt focuses on PI performance, systemic problem solving, and concrete improvement actions across the ART.
Topic: Supporting ART Events
During a PI, three Agile teams discover they are each building separate workarounds for the same unreliable integration environment. As the Scrum Master / Team Coach, what is the strongest action to support ART-level flow?
Best answer: A
What this tests: Supporting ART Events
Explanation: When multiple teams are solving the same problem independently, the issue is likely systemic rather than local. The Scrum Master / Team Coach should make it visible in the ART coordination forum and help align teams on a shared solution that improves flow across the train.
The core concept is ART-level impediment coordination. Coach Sync supports Scrum Masters / Team Coaches in surfacing cross-team blockers, duplicated effort, dependencies, and flow problems during the PI. In this scenario, separate workarounds create local optimization and waste. Bringing the issue to Coach Sync enables collaboration with other Team Coaches, the RTE, and affected teams so the ART can address the underlying environment problem once, rather than allowing each team to create a separate fix. Inspect and Adapt can be useful for deeper improvement learning, but it should not delay action on an active systemic impediment.
Coach Sync is the appropriate forum to expose cross-team impediments and coordinate systemic improvements with the ART.
Topic: Supporting ART Events
During PI Planning, an Agile team identifies that a supplier API may not be available until Iteration 4. The team’s planned feature supports a committed PI Objective, two other teams depend on the integration, and the Product Owner cannot remove the work without affecting the ART plan. What is the Scrum Master / Team Coach’s best action?
Best answer: D
What this tests: Supporting ART Events
Explanation: A risk is visible enough for ART-level discussion when it can affect PI Objectives, cross-team dependencies, or the ART’s plan. This issue is not only a team concern because multiple teams and a committed objective depend on the supplier API.
In SAFe, ART-level risk discussion is appropriate when a risk may impact the ART’s ability to meet PI Objectives or when resolution requires coordination beyond one Agile team. During PI Planning, those risks should be made visible so the ART can discuss, ROAM, assign ownership, accept, mitigate, or replan as needed. The Scrum Master / Team Coach helps the team surface the risk clearly rather than hiding it in local tracking or waiting for the problem to occur.
The key test is whether the risk affects shared commitments or cross-team coordination, not whether the team first proves the risk will happen.
The risk affects a PI Objective and multiple team dependencies, so it needs ART visibility and ownership decisions.
Topic: Supporting ART Events
During iteration planning, an Agile team identifies that a shared test environment is unavailable for the next 3 weeks. Two other teams on the ART depend on the same environment for committed PI Objectives, and the team cannot resolve access locally. What should the Scrum Master / Team Coach do next?
Best answer: D
What this tests: Supporting ART Events
Explanation: A blocker that affects multiple teams and committed PI Objectives is systemic, not just a local team issue. The Scrum Master / Team Coach should help make it visible at the ART level so the RTE and affected teams can coordinate resolution.
The core concept is matching the blocker to the correct level of action. A team-level workaround is appropriate when the team can resolve the issue within its own control. In this case, the shared environment affects several teams and threatens PI Objectives, so the Scrum Master / Team Coach should escalate or surface it through ART coordination mechanisms, such as the ART sync, Scrum of Scrums, or direct coordination with the RTE. The goal is not to hand off accountability blindly, but to create visibility and enable cross-team action. Delaying, silently re-planning, or waiting until Inspect and Adapt allows the systemic flow issue to persist too long.
The blocker affects multiple teams and PI Objectives, so it needs visibility and intervention beyond one team’s workaround.
Topic: Supporting ART Events
A Scrum Master is helping an Agile team prepare for PI Planning next week. The Product Owner has initial feature priorities, but the team has not yet reviewed likely capacity, risks, or cross-team dependencies. Several team members ask the Scrum Master to draft the team’s PI Objectives so the team can “just approve them” during planning. What is the best next step?
Best answer: A
What this tests: Supporting ART Events
Explanation: The Scrum Master helps the team get ready for PI Planning by facilitating preparation, not by taking over planning decisions. A readiness session lets the PO share priorities while the team discusses capacity, risks, dependencies, and draft objective ideas together.
In PI Planning preparation, the Scrum Master supports readiness by creating the conditions for the Agile team to plan effectively. That includes helping the PO and team review priorities, understand capacity, identify risks and dependencies, and prepare questions for ART-level alignment. The Scrum Master does not own the team’s plan or write objectives on the team’s behalf. PI Objectives should emerge from team collaboration during planning, informed by business context, team capacity, and dependencies. The RTE facilitates ART-level readiness, but the team must still prepare its own inputs and concerns. The key distinction is facilitation and coaching versus taking over ownership of the planning work.
The Scrum Master should coach and facilitate team preparation while keeping ownership of plans and objectives with the team.
Topic: Supporting ART Events
During PI Planning, an Agile team is finalizing its draft plan when it discovers that a key PI Objective depends on another team delivering an API change. The dependency is not yet visible on the ART planning board. What should the Scrum Master / Team Coach do first to support team focus while staying connected to ART-wide coordination?
Best answer: D
What this tests: Supporting ART Events
Explanation: The Scrum Master / Team Coach helps the team maintain focus, but not by isolating it from ART concerns. In PI Planning, cross-team dependencies should be made visible and coordinated so teams can create realistic plans and PI Objectives.
The core concept is balancing team facilitation with ART-wide alignment. During PI Planning, the Scrum Master / Team Coach supports the team’s planning conversation, helps clarify the dependency, and ensures it is visible to the other team and the ART. This may involve coordinating with the other team’s Scrum Master / Team Coach and involving the RTE if broader facilitation is needed.
The key is not to solve every technical issue personally or shield the team from all external coordination. The team stays focused because the dependency is captured, owned, and discussed with the right people during the event.
This keeps the team focused on its plan while making the cross-team dependency visible for ART-level coordination.
Topic: Supporting ART Events
During Inspect and Adapt, the ART reviews improvement candidates from several teams. Which candidate is best treated as a broader ART improvement in the problem-solving workshop rather than only as a local team retrospective action?
Best answer: B
What this tests: Supporting ART Events
Explanation: The problem-solving workshop focuses on systemic issues that affect the ART’s ability to deliver value. A shared test environment delaying multiple teams is broader than one team’s working agreement or backlog clarification need.
In Inspect and Adapt, improvement items should be handled at the right level. Local issues that a single Agile team can resolve usually belong in that team’s retrospective and improvement backlog. Issues that cut across teams, create dependencies, or constrain ART flow should be made visible and addressed in the ART problem-solving workshop.
A shared test environment delaying multiple teams is a systemic impediment. It may require coordination, prioritization, ownership, and action beyond one team’s control. The key distinction is whether the issue is primarily within one team’s span of control or affects the ART’s ability to integrate and deliver together.
A cross-team environment constraint affects ART flow and requires broader visibility, ownership, and problem solving.
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.