Courseiva

CCNA Supporting ART Events Questions

21 of 96 questions · Page 2/2 · Supporting ART Events · Answers revealed

Practice these questionsDomain overviewAll questions
76
Multi-Selecteasy

Which TWO roles are primarily responsible for facilitating the Team Breakout sessions during PI Planning? (Choose TWO)

Select 2 answers
A.Scrum Master
B.Product Owner
C.Release Train Engineer
D.System Architect
E.Business Owner
AnswersA, B

The Scrum Master facilitates the breakout by managing timeboxes, helping the team identify risks, and ensuring the environment is conducive to planning. They act as a coach, guiding the team through the creation of the draft plan and ensuring that all team members are actively participating in the process.

Why this answer

Team Breakouts are the heart of PI Planning where teams work locally to define their stories and objectives. The Scrum Master and Product Owner work as a leadership pair for the team during these sessions. They ensure the team stays focused, resolves internal conflicts, and aligns their technical tasks with the business priorities.

Exam trap

Candidates often incorrectly include the Release Train Engineer or System Architect as the primary facilitators, ignoring the essential partnership between the SM and PO.

Practice this question →
77
MCQhard

During the System Demo, the Scrum Master for Team Golf notices that the team's features are not integrated with another team's components, causing the demo to show only isolated functionality. The Release Train Engineer asks for an explanation. What is the most appropriate action for the Scrum Master to take?

A.Explain that the team followed its own iteration plan and integration was not scheduled until the next PI.
B.Blame the other team for not delivering their components on time and request that the RTE intervene.
C.Suggest that the team skip the System Demo until all components are fully integrated to avoid showing incomplete work.
D.Acknowledge the integration gap and commit to working with the other team to resolve it before the next System Demo.
AnswerD

The System Demo is an opportunity to inspect the integrated solution. When integration is missing, the Scrum Master should facilitate collaboration to fix it. Committing to work with the other team aligns with the Scrum Master's role of removing impediments and fostering cross-team collaboration.

Why this answer

The System Demo is a critical event for inspecting the integrated solution. When integration is lacking, the Scrum Master should facilitate collaboration between teams to resolve the issue. Acknowledging the gap and committing to work with the other team demonstrates ownership and aligns with the Scrum Master's role of removing impediments and promoting cross-team coordination.

Exam trap

The trap here is treating the System Demo as a team-level demo rather than an integrated ART-level event, leading to excuses instead of corrective action.

Practice this question →
78
Multi-Selectmedium

A Scrum Master is facilitating the team's preparation for the upcoming PI Planning event. The team needs to ensure they have the right inputs and readiness to create a realistic plan. Which TWO actions should the Scrum Master take to support the team? (Choose two.)

Select 2 answers
A.Ask the Product Owner to finalize all team backlog stories with detailed acceptance criteria and estimates before PI Planning begins.
B.Ensure the team has reviewed the Program Vision and the top features in the Program Backlog before arriving at PI Planning.
C.Have the Scrum Master assign each team member their specific stories for the upcoming PI so that planning time can be used for estimation only.
D.Confirm that the team has identified its capacity and any known dependencies or risks that should be shared during the planning event.
E.Instruct the team to prepare a detailed presentation of all completed work from the previous PI to share with stakeholders at the start of PI Planning.
AnswersB, D

PI Planning requires teams to understand the Program Vision and the prioritized features in the Program Backlog so they can create meaningful draft objectives. The Scrum Master should verify that the team has access to and has reviewed these inputs beforehand. This preparation enables productive breakout sessions and helps the team align its plan with the ART's strategic direction, rather than spending valuable planning time on basic orientation.

Why this answer

Effective PI Planning preparation includes reviewing the Program Vision and Program Backlog features, and confirming the team's capacity, dependencies, and risks. These inputs enable the team to create realistic draft objectives and engage productively in breakout sessions. Pre-assigning work or requiring fully finalized stories undermines self-organization and the collaborative nature of the event.

Exam trap

The trap here is assuming that PI Planning preparation means completing all backlog refinement and assigning work in advance, rather than ensuring the team has the strategic context and capacity data needed to plan collaboratively.

Practice this question →
79
MCQmedium

During the PI Planning event, the ART is conducting the draft plan review. A team presents a plan that includes a feature with a dependency on another team, but the dependency is not reflected on the program board. As the Scrum Master for that team, what should you do?

A.Wait until after PI Planning to update the program board with the dependency to avoid disrupting the session.
B.Facilitate a discussion with the team and the dependent team to make the dependency visible on the program board and adjust the plan if needed.
C.Escalate the missing dependency to the Release Train Engineer immediately and ask them to resolve it.
D.Instruct the team to remove the feature from the plan to avoid cross-team complications.
AnswerB

The draft plan review is designed to surface dependencies and risks. The Scrum Master should facilitate a conversation between the teams to make the dependency visible and adjust plans collaboratively. This ensures that the dependency is managed and that both teams agree on the approach, which is essential for successful PI execution and aligns with the purpose of the event.

Why this answer

During the draft plan review, dependencies should be made visible on the program board and discussed collaboratively. The Scrum Master facilitates a conversation between the teams to adjust the plan and ensure alignment. This proactive approach prevents integration issues later and leverages the event's purpose of surfacing and resolving cross-team dependencies.

Exam trap

The trap here is delaying the dependency update or escalating immediately instead of using the draft plan review to facilitate cross-team collaboration.

Practice this question →
80
MCQmedium

During the System Demo for a two-week iteration, the Product Owner for Team Delta notices that the new feature is not actually integrated with another team's component, but the demo still shows it working. The Scrum Master investigates and finds the presenter used a local stub instead of the real integration. What should the Scrum Master do first?

A.Accept the demo as valid because the team's own iteration goals were met and the feature works in their environment.
B.Ask the presenter to stop the demo and explain that the System Demo must reflect the integrated solution from all teams in the ART.
C.Log a defect against the other team for failing to provide an integrated build to Team Delta before the demo.
D.Cancel the remainder of the System Demo and reschedule it for the next iteration once integration is complete.
AnswerB

The System Demo is the ART-level event where the integrated solution from all teams is demonstrated in the staging environment. A local stub misrepresents the true state of the system and undermines the inspect-and-adapt purpose. The Scrum Master should protect the integrity of the event by clarifying the expectation that only integrated work is demonstrated, then facilitate follow-up to address the integration gap.

Why this answer

The System Demo exists to show the integrated solution produced by all teams in the ART, so using a local stub misrepresents progress and removes the opportunity for genuine inspection. The Scrum Master's first responsibility is to protect the event's purpose by clarifying that only integrated work is demonstrated, then help the team address the underlying integration gap.

Exam trap

The trap here is treating the System Demo as a team-level iteration review where a locally working feature is sufficient, when it is actually an ART-level event that requires integrated work.

Practice this question →
81
MCQeasy

A Scrum Master is preparing a team for its first ART sync after PI Planning. The team has several stories that depend on another team's API changes and one architectural concern that may affect the whole train. What should the Scrum Master ensure the team brings to the ART sync?

A.A complete backlog review with estimates for all upcoming stories so other teams can plan their own capacity around the team's workload.
B.A demonstration of the team's completed stories so other teams can confirm the interfaces they depend on are stable.
C.A status report listing every story the team has started and the percentage of completion for each.
D.The dependency on the other team's API work, the architectural concern, and any blockers or risks that require ART-level coordination.
AnswerD

The ART sync exists to coordinate dependencies, integration points, risks, and impediments that cross team boundaries. Bringing the API dependency, the architectural concern, and related blockers puts the right information in front of the train so commitments can be adjusted and risks addressed early. This is exactly the content that makes the event productive for the whole ART.

Why this answer

The ART sync is a coordination event where teams align on dependencies, integration points, risks, and ART-level impediments. For this team, the cross-team API dependency and the architectural concern are precisely the items that require train-wide visibility so they can be tracked and resolved. Status percentages, backlog detail, and demonstrations belong to other events and would dilute the sync's purpose.

Exam trap

The trap here is filling the ART sync with team-level status or demonstrations, when the event is designed for cross-team dependency, risk, and impediment coordination.

Practice this question →
82
Multi-Selecthard

A Scrum Master is preparing a team for its first PI Planning on a new Agile Release Train. The team asks which activities they will participate in during the two-day event. Which TWO activities are part of the team's PI Planning responsibilities? (Choose two.)

Select 2 answers
A.Establishing the ART's budget and approving the Lean Portfolio Management funding for the next PI.
B.Creating and committing to team PI Objectives during team breakout sessions.
C.Identifying and recording cross-team dependencies and risks during breakout sessions.
D.Facilitating the management review and problem-solving session that follows the draft plan review.
E.Negotiating the ART's top-level solution intent with enterprise architects outside the planning event.
AnswersB, C

Team breakout sessions are where each team reviews its backlog, estimates capacity, identifies dependencies, and drafts its PI Objectives for the upcoming PI. These objectives express the business value the team intends to deliver and are committed during the event. This is a core team-level responsibility in PI Planning and directly shapes the ART's plan.

Why this answer

During PI Planning, each team works in breakout sessions to review its backlog, estimate capacity, draft PI Objectives, and identify dependencies and risks. These outputs feed the program board and the draft plan review. Budgeting, management review facilitation, and solution intent negotiation belong to other roles and are not team responsibilities within the event.

Exam trap

The trap here is attributing portfolio or management-level accountabilities, such as funding and solution intent, to teams during PI Planning.

Practice this question →
83
MCQhard

During the Inspect and Adapt (I&A) event, the ART's metrics show that the Program Predictability Measure for the last PI was 60%. The RTE facilitates a problem-solving workshop where teams identify 'unclear acceptance criteria' as a root cause. As the Scrum Master for one of the teams, what is your most appropriate next step to support the ART's improvement?

A.Work with the RTE and other Scrum Masters to create an improvement story for the ART's backlog that addresses acceptance criteria clarity across teams.
B.Schedule a separate meeting with your team's Product Owner to rewrite all user stories with clearer acceptance criteria for the next PI.
C.Update the team's Definition of Done to include a mandatory review of acceptance criteria by the Product Owner before sprint planning.
D.Escalate the issue to the Business Owners and request additional funding for a dedicated business analyst to write acceptance criteria.
AnswerA

The Inspect and Adapt event concludes with identifying improvement items that are added to the ART backlog. Since the root cause affects the entire ART, the Scrum Master should collaborate with the RTE and peers to create a systemic improvement story. This ensures the fix is coordinated and tracked, rather than leaving each team to solve it in isolation, which aligns with the event's purpose of driving ART-level improvements.

Why this answer

The Inspect and Adapt event culminates in the problem-solving workshop, where root causes are identified and improvement items are added to the ART backlog. When a root cause is systemic, the Scrum Master should collaborate with the RTE and other Scrum Masters to create an ART-level improvement story, ensuring a coordinated and tracked solution rather than isolated team fixes.

Exam trap

The trap here is focusing on a single team's local fix instead of recognizing that the Inspect and Adapt event drives ART-level improvements that should be captured in the ART backlog.

Practice this question →
84
MCQhard

During the Inspect and Adapt event, a team's quantitative measurement shows a sharp increase in escaped defects over the last three iterations. The Scrum Master wants the team to move from the metrics review into meaningful root-cause analysis. What is the most appropriate next step?

A.Facilitate the team through a structured problem-solving workshop to identify the root cause, then define and own corrective actions.
B.Have the team estimate the cost of each escaped defect and report the total to the Release Train Engineer for prioritization.
C.Add a defect-reduction objective to the team's next Program Increment planning so the issue is tracked at the ART level.
D.Ask the system architect to review the team's code and assign the necessary refactoring work to specific developers.
AnswerA

The Inspect and Adapt event includes a structured Problem-Solving Workshop where the team uses root-cause analysis, often with a fishbone or five-whys technique, to find the underlying cause of a significant problem. Facilitating this lets the team move from symptom to cause and define corrective actions it owns, which is the intended flow of the event.

Why this answer

The Inspect and Adapt event is structured to move from the quantitative measurement of a significant problem into a Problem-Solving Workshop where the team performs root-cause analysis and defines corrective actions it owns. Facilitating that workshop addresses the defect trend at its source, while estimating cost, adding a PI objective, or delegating to an architect all skip the diagnosis the event requires.

Exam trap

The trap here is treating the Inspect and Adapt as a reporting or planning exercise and skipping the structured root-cause workshop that is the heart of the event.

Practice this question →
85
MCQhard

During the Inspect and Adapt of a PI, the ART's metrics show that a specific team's velocity dropped sharply in the last two iterations because of unplanned production support. In the problem-solving workshop, the team wants to add a root cause of 'too much unplanned work' to the ART's backlog of improvement items. As that team's Scrum Master, what is the most appropriate action to ensure the workshop produces an actionable result?

A.Recommend that the team reduce its planned velocity for the next PI by the average amount of unplanned work so the metrics look more consistent.
B.Record 'too much unplanned work' as the improvement item and assign it to the Release Train Engineer, since unplanned work is a program-level concern.
C.Ask the team to defer the discussion to their own team retrospective so the ART can focus the workshop on program-level impediments only.
D.Help the team apply root-cause analysis to identify the underlying source of the unplanned work, then define a measurable improvement item with an owner and a due date.
AnswerD

The problem-solving workshop is structured around identifying root causes, not symptoms, and producing a small number of improvement items with clear owners and target dates. Facilitating the team through a root-cause technique and converting the finding into a specific, measurable backlog item keeps the workshop's output actionable and aligned with the ART's improvement backlog.

Why this answer

The Inspect and Adapt problem-solving workshop exists to move from observed symptoms to root causes and then to a small set of owned, measurable improvement items. Facilitating root-cause analysis and converting the finding into a specific improvement backlog item with an owner and due date produces an actionable result. Restating the symptom, reassigning ownership away from the team, adjusting velocity, or deferring the discussion all leave the underlying cause unaddressed.

Exam trap

The trap here is treating the stated problem, 'too much unplanned work,' as the root cause and stopping there, when the workshop requires drilling down to the underlying source before defining an improvement item.

Practice this question →
86
MCQmedium

During Team Breakout #1 in PI Planning, the team finds that their capacity is exceeded by the features assigned to them. What should the Scrum Master do first?

A.Ask the team to work overtime to ensure all features are included.
B.Move the excess features to the 'Uncommitted' list without consultation.
C.Wait for the Draft Plan Review to see if management notices the gap.
D.Facilitate a conversation between the team and the PO to prioritize the work.
AnswerD

Facilitating a prioritization discussion is the most effective way to handle capacity issues. It allows the Product Owner to decide which features are essential and which can be deferred. This ensures the team's plan is realistic while still aligned with the most important business priorities.

Why this answer

The Scrum Master's role is to ensure the team creates a realistic plan. When capacity is exceeded, the first step is to seek clarification and prioritization from the Product Owner. This prevents the team from committing to an unachievable amount of work and ensures they focus on the highest value items.

Exam trap

Candidates often suggest the Scrum Master should unilaterally reduce scope or ask the team to work overtime, ignoring the Product Owner's authority over priority.

Practice this question →
87
MCQmedium

The Product Owner returns from a PO Sync and informs the team that a new high-priority Feature must be started in the current PI. How does the Scrum Master help the team?

A.Refuse the change to protect the team's original PI plan and commitment.
B.Help the PO assess the impact on current PI Objectives and communicate tradeoffs.
C.Add the feature to the current iteration and ask the team to work overtime.
D.Ask the Release Train Engineer to decide if the team should take the work.
AnswerB

Helping the PO assess the impact on PI Objectives is the correct response as it maintains the integrity of the current plan while acknowledging the change. This collaborative effort allows the team to provide data-driven feedback on what other work might need to be delayed if this new feature is accepted.

Why this answer

While SAFe encourages a stable plan during the PI, it also recognizes that business needs can change. The Scrum Master's role is to protect the team's sustainable pace while helping them adapt to these changes. This involves facilitating a process where the impact of new work is transparently evaluated against the existing commitments.

Exam trap

Candidates often mistakenly choose options suggesting the Scrum Master should reject the work or handle the negotiation alone, ignoring the PO's responsibility to manage the backlog and business priorities.

Practice this question →
88
MCQmedium

During the Scrum of Scrums, Team Beta reports they will miss a dependency needed by Team Alpha. As Scrum Master for Team Alpha, what is the most appropriate immediate action?

A.Instruct Team Alpha to stop work on the dependent Feature until Team Beta delivers.
B.Work with Team Beta's Scrum Master to renegotiate the dependency timing and update the ART's program board.
C.Log the dependency as a risk in the team's backlog and continue with the current plan unchanged.
D.Escalate to the Release Train Engineer to force Team Beta to reprioritize the dependency.
AnswerB

The Scrum of Scrums exists to surface and address cross-team dependencies. Collaborating with the other Scrum Master to adjust timing and updating the program board keeps the ART's plan current and gives Team Alpha a realistic basis for adjusting their own work.

Why this answer

The Scrum of Scrums is the forum for resolving cross-team dependencies. The Scrum Master should facilitate direct collaboration with the other team's Scrum Master to renegotiate timing and update the program board, keeping the ART's plan transparent. Escalating immediately, halting work, or merely logging the risk without replanning all fail to address the dependency effectively.

Exam trap

The trap here is jumping to escalation or stopping work instead of first using the Scrum of Scrums to collaboratively replan the dependency.

Practice this question →
89
MCQhard

Refer to the exhibit. Why would the Scrum Master coach the team to mark the 'Auth API' objective as uncommitted?

A.The objective has low business value for the stakeholders.
B.The team faces high technical uncertainty or external dependencies.
C.The team has a lack of interest in this specific technical task.
D.It is a stretch goal that the team will only start if they finish early.
AnswerB

High technical uncertainty or external dependencies are the primary reasons for using uncommitted objectives. By categorizing it this way, the team can still plan the work and gain experience without failing their commitment if the external dependencies or technical challenges prove to be insurmountable during the Program Increment execution.

Why this answer

Uncommitted objectives are not extra work; they are planned items that have significant uncertainty or dependency risks. The Scrum Master coaches the team to use this category to ensure the ART's commitment remains reliable. This practice improves predictability by distinguishing between what is highly likely and what is contingent on external factors.

Exam trap

Candidates often mistakenly believe uncommitted objectives represent low-priority work that can be discarded, failing to understand they are valid, planned objectives with higher levels of inherent risk.

Practice this question →
90
MCQhard

Two iterations into a PI, the Scrum Master notices that the team's representatives consistently arrive at the Scrum of Scrums unprepared, reporting only their own status while the ART's cross-team dependencies go unaddressed. What is the most effective action for the Scrum Master to take?

A.Attend the Scrum of Scrums personally and take over reporting so the team's dependency information is presented accurately.
B.Recommend the team stop sending representatives and instead post dependency updates in a shared channel that other teams can read asynchronously.
C.Work with the team to prepare dependency information before each Scrum of Scrums, coaching the representative on raising blockers and following up on commitments.
D.Ask the Release Train Engineer to add a mandatory dependency checklist to the Scrum of Scrums agenda and enforce attendance rules for all representatives.
AnswerC

The Scrum Master serves the team by helping it prepare for and get value from ART events, which here means coaching the representative to bring dependency status, blockers, and follow-ups rather than a status recital. This builds a durable capability, keeps ownership with the team, and directly improves the cross-team coordination the Scrum of Scrums exists to provide. It also models the preparation habit for future PIs.

Why this answer

The Scrum Master's responsibility for ART events is to help teams get value from them, so the right move is to coach the team representative to arrive with dependency status, blockers, and follow-up items. That keeps ownership with the team, improves coordination for the whole train, and builds a habit that persists beyond the current PI. Imposing controls or substituting for the representative addresses symptoms rather than capability.

Exam trap

The trap here is reaching for a process control or attending in the team's place, when the Scrum Master's leverage is coaching the team to prepare for and own its ART-level coordination.

Practice this question →
91
MCQeasy

During PI Planning, what is the required outcome if any team member votes two fingers or fewer during the confidence vote?

A.The vote is recorded, and the team proceeds with the plan as written
B.The Scrum Master must override the vote if the Product Owner is confident
C.The person with low confidence is moved to a different team for the PI
D.The individual's concerns must be heard and the plan may need to be reworked
AnswerD

When someone votes two or fewer, they must explain their reasoning. The team then discusses how to mitigate those concerns. This might involve reducing scope, adding resources, or changing the approach, ensuring the final plan is one that the entire team genuinely believes they can deliver.

Why this answer

The confidence vote is a 'Fist of Five' exercise. If anyone votes two or fewer, it indicates they do not believe the plan is achievable. The person's concerns must be heard and addressed.

This may require the team to rework their plan or adjust objectives until everyone reaches at least a three-finger level of confidence.

Exam trap

People often think the majority rules in a confidence vote. In SAFe, a single 'low' vote requires the team or train to stop and address the concern, ensuring total alignment.

Practice this question →
92
MCQmedium

In a large Agile Release Train, the System Demo is often attended by various stakeholders. Why is it important for the Scrum Master to ensure the team is prepared for this event every two weeks?

A.To allow the team to practice their public speaking and presentation skills
B.To provide objective evidence of progress and get stakeholder feedback
C.To ensure the team has a reason to complete their stories before the deadline
D.To give the Scrum Master a chance to demonstrate the team's velocity
AnswerB

Objective evidence is a core principle of SAFe. By showing working, integrated software, the team proves progress in a way that status reports cannot. Stakeholder feedback at this stage is invaluable for making small course corrections before they become expensive and time-consuming problems later.

Why this answer

The System Demo is the primary mechanism for receiving objective feedback on the integrated system. If the team is not prepared, they lose the opportunity to validate their work against stakeholder expectations. Regular demos ensure that any misalignments are caught early, reducing the risk of a significant 'miss' at the end of the PI.

Exam trap

A common trap is thinking the System Demo is optional if the team hasn't finished a 'big' feature. In SAFe, the demo must happen every iteration to show the integrated state, even if progress is small.

Practice this question →
93
MCQeasy

Who is the primary audience for the System Demo?

A.The Development Team members within the ART.
B.Business Owners and external stakeholders.
C.The Scrum Master and Release Train Engineer.
D.The System Architect and technical leads.
AnswerB

Business Owners and Stakeholders are the primary audience because they provide the business context and feedback necessary to validate the solution. Their presence ensures that the ART is building the right thing and that the investment of time and resources is producing the expected value for the organization.

Why this answer

The System Demo is the primary event for stakeholders to see the progress of the Agile Release Train. It provides objective evidence of the work completed and allows for feedback that can influence the future direction of the product. The Scrum Master ensures the team is prepared to present their work meaningfully.

Exam trap

Candidates often mistakenly include 'Development Team members' as the primary audience, overlooking the fact that the demo is specifically designed to solicit feedback from Business Owners and external stakeholders.

Practice this question →
94
MCQeasy

A Scrum Master is facilitating the ART Sync for a newly launched Agile Release Train. The Product Manager has not attended the last three sessions, and the System Architect is also consistently absent. The teams are still sharing progress and dependencies. What is the most appropriate action for the Scrum Master?

A.Take over the Product Manager's backlog prioritization duties during the ART Sync to keep the meeting productive.
B.Raise the attendance gap with the Release Train Engineer and help the Product Manager and System Architect understand their role in the ART Sync.
C.Replace the ART Sync with a written status report distributed by email to the Product Manager and System Architect.
D.Cancel the ART Sync until the Product Manager and System Architect can attend.
AnswerB

The ART Sync depends on the Product Manager and System Architect to provide content authority and technical guidance, so their absence undermines the event's purpose. The Scrum Master serves the ART by coaching participants and escalating impediments they cannot resolve. Involving the Release Train Engineer, who owns the ART's overall execution, is the correct path to restore participation without disrupting the event.

Why this answer

The ART Sync exists to synchronize teams and surface dependencies, and it relies on the Product Manager and System Architect for content and technical decisions. When those roles are absent, the Scrum Master should coach and escalate through the Release Train Engineer rather than cancel or replace the event. This preserves the cadence while addressing the root cause of the attendance problem.

Exam trap

The trap here is assuming that a missing role justifies cancelling or replacing a cadence event instead of coaching and escalating the attendance issue.

Practice this question →
95
MCQmedium

A Scrum Master notices that the System Demo is frequently delayed because teams are struggling to integrate their code at the end of the iteration. What is the best way to support this ART event?

A.Suggest moving the System Demo to every other iteration to allow more time.
B.Ask the Product Owner to demo only the features that are fully completed.
C.Encourage the team to adopt Continuous Integration and align on integration points.
D.Request that the System Architect takes over the integration responsibilities.
AnswerC

Coaching the team on Continuous Integration ensures that code is merged and tested frequently throughout the iteration. By aligning on integration points with other teams, the ART reduces the 'integration debt' that typically causes delays, making the System Demo a smoother and more valuable event for stakeholders.

Why this answer

The System Demo relies on the ability to show integrated work from all teams on the Agile Release Train. If integration is failing, the Scrum Master must advocate for technical practices like Continuous Integration and more frequent synchronization to ensure the demo remains a viable mechanism for gathering stakeholder feedback and measuring progress.

Exam trap

Candidates often suggest manual coordination or meetings, failing to recognize that technical practices like Continuous Integration are the only scalable way to solve systemic integration delays in SAFe.

Practice this question →
96
MCQeasy

During PI Planning, the Scrum Master for Team Gamma notices that one team member is dominating the discussion and dismissing others' ideas during the team breakout. What is the most appropriate action for the Scrum Master to take?

A.Intervene to ensure all voices are heard and the team remains focused on the PI objectives.
B.Ignore the behavior because PI Planning is time-boxed and the team must complete their plan.
C.Escalate the behavior to the functional manager of the dominating team member.
D.Let the team resolve the issue on their own to encourage self-management.
AnswerA

The Scrum Master serves as a facilitator during PI Planning, ensuring effective collaboration. When one person dominates, the Scrum Master should step in to balance participation and keep the team aligned with the planning goals. This action supports the team's ability to self-organize and make collective decisions.

Why this answer

The Scrum Master should intervene to ensure all voices are heard and the team stays focused. Facilitating inclusive discussions is a key Scrum Master responsibility during PI Planning. By addressing the dominating behavior, the Scrum Master helps the team leverage diverse perspectives and create a more robust plan.

Exam trap

The trap here is assuming that self-management means the Scrum Master should never intervene in team dynamics, even when facilitation is needed to uphold collaboration.

Practice this question →
← PreviousPage 2 of 2 · 96 questions total

Ready to test yourself?

Try a timed practice session using only Supporting ART Events questions.

Start 20-question session