SAFe Scrum Master (SSM) — Questions 76–150

This is correct because the Retrospective is a primary mechanism for the team to inspect their process and decide on improvements. By coaching the team to own the Retrospective outcomes, the Scrum Master / Team Coach shifts decision-making to the team, fostering self-management. This builds the team's capability to solve problems without relying on the Scrum Master for direction.

Addressing the behavior privately is respectful and effective. Explaining the impact on the team helps the individual understand why their participation matters for the success of the group. This collaborative approach focuses on improvement and team alignment rather than punishment, fostering a healthier and more productive team culture overall.

In SAFe, features are decomposed into user stories that can be completed within an iteration. Guiding the team to slice the feature into smaller, independently deliverable stories enables incremental value delivery and aligns with Scrum's iterative approach. This is a core Scrum Master coaching moment during Sprint Planning.

Root cause analysis is the most effective way to address chronic carry-over. By identifying the specific bottlenecks—whether they are technical, process-related, or external—the team can implement targeted improvements. This scientific, data-driven approach is key to improving team performance and achieving the consistency needed for reliable delivery in SAFe.

Silent brainstorming and round-robin techniques give every team member an equal opportunity to contribute without being interrupted or influenced by more vocal colleagues. This is especially useful when dominant personalities are present, as it surfaces diverse perspectives before open discussion. The Scrum Master can then facilitate a structured discussion and voting process. This technique directly addresses the imbalance while preserving psychological safety and ensuring the retrospective reflects the whole team's thinking, not just the senior members' views.

In SAFe, team Iterations and the ART's events share a common cadence, with iterations nested inside the Program Increment. This alignment lets team-level learning flow into ART-level synchronization through events such as the System Demo and Inspect and Adapt. The Scrum Master clarifies this nesting so the team understands its Scrum events are not separate from, but integral to, the train's rhythm.

The data clearly indicates that mid-iteration changes negatively affect the team's capacity to deliver. By highlighting this, the Scrum Master provides evidence that can be used to influence the Product Owner to maintain a stable iteration scope, which will lead to more predictable performance and better alignment.

Using historical velocity and capacity helps the team ground their commitments in data. Facilitating a discussion to adjust the plan ensures the team owns the plan and learns to forecast realistically. This addresses the root cause of overcommitment while building the team's planning skills, aligning with the Scrum Master's role as a facilitator and coach.

Attending the ART Sync and using the Program Board are the primary SAFe mechanisms for cross-team coordination. The Program Board visualizes dependencies and milestones, while the ART Sync provides a forum to address them. Coaching the team to use these tools directly addresses late dependency discovery and builds the collaboration needed across the ART.

Coaching the team to refine features just-in-time ensures they maintain focus on immediate value delivery without getting bogged down by speculative future requirements. This practice embodies Lean-Agile principles by keeping work-in-progress low and adapting effectively to changing priorities.

The Iteration Review is an inspect-and-adapt event where the team demonstrates the increment to stakeholders and captures feedback. By inviting stakeholders and coaching a demo of working software, the Scrum Master restores the event's purpose. The feedback then informs the Product Owner's backlog ordering and can feed the train-level System Demo, improving alignment across the Agile Release Train.

The Iteration Retrospective is where the team inspects its way of working and identifies improvements to apply next Iteration. Coaching the team away from status reporting and toward reflection and action restores the event's purpose. This also builds self-management, because the team, not the Scrum Master, owns the resulting improvements and their follow-through.

The Scrum Master serves the ART by removing impediments and facilitating cross-team coordination. The System Demo is an inspect-and-adapt moment; the overlap is a coordination issue best resolved by bringing the two teams together immediately after the demo, preserving the event's integrity while ensuring the conflict is addressed before the next Iteration begins.

Brainstorming potential solutions is the step that follows the identification of a root cause. Once the 'why' is understood through techniques like the 5 Whys, the team must then pivot to creative thinking to find ways to prevent the issue from recurring in future iterations and Program Increments.

This approach tackles both issues: facilitation ensures balanced participation, and using historical velocity and capacity data helps the team make realistic commitments. The Scrum Master / Team Coach should intervene when one person dominates and guide the team to base commitments on evidence rather than optimism. This builds the team's ability to self-manage planning.

The I&A event begins with a system demo where metrics are reviewed. Sharing the data and facilitating discussion aligns with the problem-solving workshop's purpose: to identify root causes using data. The Scrum Master helps the team become aware and engage in analysis rather than jumping to solutions.

Structured activities such as silent brainstorming or round-robin ensure that every team member has an opportunity to contribute, reducing the pressure on quieter members and preventing dominant voices from taking over. These techniques are especially effective when a team is hesitant or new to retrospectives. They promote balanced participation and help surface diverse perspectives, which is essential for identifying meaningful improvements and building a safe, inclusive environment.

This addresses the behavior at its source while engaging the whole team in setting norms. Private coaching avoids public shaming, and co-created working agreements give everyone shared ownership of participation expectations. It fits the servant-leader and team-coach stance, building psychological safety and self-management rather than imposing a solution from above.

In Scrum, the Product Owner owns what and why, while the Developers own how. Prescribing technical designs collapses that boundary, removes the team's ownership, and reduces the team's ability to adapt when implementation realities change. The Scrum Master serves both roles by coaching the Product Owner toward outcome-focused items and the Developers toward taking responsibility for technical decisions and refinement.

Working agreements are a core self-management tool that let the team define its own norms for collaboration and flow. When the team authors and owns them, adherence comes from shared commitment rather than imposed rules. This directly addresses interrupting, skipped refinement, and stalled Stories while building the team's capability to regulate itself.

The Retrospective is for inspecting and adapting the team's process. When an action is repeatedly identified but not implemented, the Scrum Master should facilitate a root-cause discussion and help the team define a concrete, achievable plan. This addresses the underlying issue and empowers the team to follow through, aligning with the Scrum Master's role as a servant-leader and coach.

Scrum and SAFe both protect the iteration from constant change so the team can finish a coherent increment. The Product Owner may continue refining and reordering the backlog for future iterations, but changes to the current iteration should be rare and negotiated with the team. This preserves flow, limits work in progress, and keeps the team's forecast meaningful.

In Scrum, the developers own the 'how' of the work. By self-selecting stories and defining their own tasks, the team practices self-management and shared ownership of the Sprint Goal. This directly addresses the observed dependency on the Product Owner for task assignment.

Dependencies are normal in PI Planning and are visualized on the program board with red strings. The team should keep planning the work they control, record the dependency, and the Scrum Master should coordinate with the other team's Scrum Master or the RTE to align timing. This keeps the timebox productive while ensuring the dependency is visible and owned.

The PI System Demo provides a comprehensive look at the value delivered during the Program Increment. Unlike the bi-weekly System Demos, this session focuses on the overall progress toward the PI Objectives and the strategic themes of the organization, providing a clear picture of the train's impact.

Facilitating a discussion on impact is the professional way to manage stakeholders. By showing how new requests affect the current commitments, the Scrum Master helps stakeholders understand the trade-offs. This empowers the PO to make informed, data-driven decisions about whether to add new work or defer existing tasks.

Engaging the Release Train Engineer and System Architect is the correct immediate step because they provide the necessary oversight to resolve cross-team technical constraints. This collaborative approach allows for re-sequencing or technical adjustments that might save the objective without needing to immediately reduce the overall Feature scope.

A newly formed team lacks shared working agreements and trust. The Scrum Master therefore focuses on establishing norms, building psychological safety, and coaching the group toward self-organisation, which are the foundational conditions enabling effective Agile Team behaviour within SAFe.

Active listening lets the Scrum Master surface the team's own perspectives, and collaborative decision-making keeps ownership with the team rather than the leader. This directly satisfies the servant leadership behaviours sought during the SAFe transition, where the Scrum Master guides without commanding.

The program board and Scrum of Scrums exist precisely to surface cross-team dependencies that emerge or were missed during PI Planning. Registering the dependency and escalating it at the Scrum of Scrums lets the affected teams and the RTE re-sequence work before the dependency becomes a PI-level impediment, which is the Scrum Master's role in supporting ART execution.

The System Demo showcases the integrated work of all teams on the train in a staging environment that mirrors production. The team should demonstrate the integrated functionality, even if some stories are not fully complete, because the goal is to inspect the whole system and gather feedback. This aligns with the SAFe principle of frequent integration and objective evaluation.

The Scrum Master serves the team by fostering an environment where all voices are heard during planning. Inviting quieter members ensures diverse input, better estimates, and shared ownership of the plan, which is exactly the collaborative behavior PI Planning depends on.

This is correct because the Daily Stand-up is for the team to synchronize and plan the next 24 hours, not to report to the Scrum Master. By coaching the team on its purpose and facilitating peer-to-peer communication focused on the Iteration Goal, the Scrum Master addresses the root cause of the disengagement and improves the event's value.

The Iteration Retrospective is the event where the team inspects its process and interactions and identifies improvements. Holding it directly addresses the repeated impediments by giving the team a structured way to find root causes and act. The Scrum Master should protect this time rather than let delivery pressure eliminate it.

Sharing impediments is the core function of the meeting. In a SAFe ART, teams are interdependent. By surfacing these issues, the Scrum Master triggers the necessary coordination across the train. This proactive sharing is essential for keeping the ART synchronized and ensuring that work flows smoothly towards the release goal.

The team Retrospective closes each Iteration by inspecting how the team worked and identifying improvements. In SAFe, the ART additionally holds an Inspect and Adapt event after the System Demo at the end of a Program Increment to solve broader, systemic problems. These operate at different levels and do not replace each other, giving teams both local and train-wide improvement loops.

PI Planning is designed to surface cross-team dependencies, and the program board is the tool for making them visible. By facilitating a direct conversation between the teams, the Scrum Master helps them negotiate delivery timing and adjust plans before commitment. This keeps the team's plan realistic and aligns with SAFe's emphasis on collaboration across the train.

The problem-solving workshop is a structured part of the Inspect and Adapt where the ART selects a significant problem and applies root-cause analysis to find a durable corrective action. A Scrum Master supports this by helping the team contribute meaningfully, keep the analysis honest, and commit to improvements that can be carried into the next PI, which is exactly the event's adaptive purpose.

The Scrum of Scrums is a coordination meeting where dependencies are surfaced. If a team's representative is absent, the Scrum Master should capture the dependency on the program board and then directly follow up with the missing team's Scrum Master to ensure it is addressed. This maintains transparency and keeps the dependency visible for tracking and resolution.

The Daily Stand-up exists for the team to inspect progress toward the Iteration Goals and adapt its plan. When members report to the Scrum Master, ownership has shifted away from the team. Coaching them to self-facilitate and pull the next speaker restores peer-to-peer coordination and reinforces self-management, which is a core Scrum Master responsibility in SAFe. This action directly addresses the observed behavior without removing the event.

This action directly addresses the Product Owner's behavior while respecting their role. By coaching the Product Owner on how self-organizing teams pull work, the Scrum Master helps realign the team's operating model with SAFe principles. It also protects the developers from conflict and fosters a collaborative relationship. This is a servant-leader approach that resolves the root cause without undermining anyone's authority.

In SAFe, the Scrum Master / Team Coach helps the team make work visible and manage flow rather than absorbing hidden work. By surfacing the unplanned items, the team can see the real capacity consumed, decide whether to renegotiate scope with the Product Owner, and raise a systemic impediment if needed. This preserves team ownership and supports the Inspect and Adapt cycle without bypassing the team.

This action embodies the Team Coach role. By asking guiding questions and facilitating problem-solving, the Scrum Master helps the team build capability and confidence. Intervening only for external impediments respects the team's ownership of technical decisions. This approach aligns with servant leadership and self-organization, and it addresses the root cause of the team's inability to finish stories: over-reliance on the Scrum Master for technical direction.

The PI system demo is the first part of the Inspect and Adapt event, where the ART demonstrates the integrated solution from the PI. Teams participate by presenting their working, integrated increments. This gives stakeholders and the ART a factual basis for the measurement review that follows, making it a core team responsibility during the event.

This approach honors the prior experience while keeping the door open to adaptation, which is central to the Retrospective. By exploring what was tried and what has changed, the team can make an informed decision rather than dismissing the idea outright. Testing a small experiment also lowers risk and generates learning, aligning with SAFe's continuous improvement mindset.

This directly addresses the lack of follow-through by helping the team focus on a few impactful changes and creating accountability. The Scrum Master / Team Coach facilitates the team in choosing actions, assigning owners, and reviewing progress in subsequent events. This builds the team's ability to self-improve and makes the retrospective productive rather than repetitive.

This is correct because the Scrum Master is responsible for creating a safe environment. Redirecting from personal blame to systemic causes aligns with the Retrospective's purpose and encourages learning. By facilitating a discussion on process improvements, the Scrum Master helps the team move forward constructively and prevents future incidents.

The Scrum Master should facilitate team agreement on estimation practices. Explaining relative sizing and its benefits—such as faster estimation and reduced false precision—helps the team make an informed choice. Guiding them to a consistent approach supports self-management and improves planning over time. This neutral facilitation respects all voices while steering toward a proven agile technique that fits the team's context and Iteration Planning needs.

Facilitating estimation and refinement helps the team uncover hidden complexities and reach a shared understanding of the work. This collaborative process leads to more accurate estimates and reduces the likelihood of overcommitment, aligning with the Scrum Master's role in promoting team-level flow and predictability.

The Iteration Review is intended to inspect the increment and adapt the backlog through stakeholder feedback. The Scrum Master serves the team by ensuring the event is effective and that feedback is actively solicited. Facilitating a structured conversation helps the team and stakeholders engage, aligning with the Scrum Master's role of coaching and removing impediments to event success.

The Program Predictability Measure is the 'heartbeat' of the ART. By reviewing this and other metrics (like quality or cycle time), the train can see if it is operating within the target range (80-100%) and identify trends that may need to be addressed in the Problem-Solving Workshop.

The ART Sync is a forum for transparency and cross-team collaboration. Reporting the impediment and seeking help aligns with SAFe's principle of transparency and the purpose of the ART Sync to address issues collectively. This allows the ART to adjust plans, reallocate work, or provide support, keeping the PI on track.

The Scrum Master supports the Iteration Review by helping the team be transparent about what is and is not integrated. Acknowledging the dependency and capturing it as an impediment keeps the event honest, preserves stakeholder trust, and routes the issue to the appropriate coordination mechanism so the team can address it in the next Iteration.

Facilitation is the core of the role. By creating a safe space for open communication, the Scrum Master ensures the team can discuss difficult topics without fear. This focus on action ensures that the meeting results in tangible improvements rather than just a venting session that leaves the team unchanged.

The high impediment resolution time is the primary indicator of why iteration goals are not being met. By shifting focus to clearing these blocks, the Scrum Master directly supports the team's productivity. This allows the team to focus on their work, resulting in better goal attainment and team morale.

Psychological safety is foundational for an effective Retrospective. By reinforcing a blame-free space, the Scrum Master helps team members speak candidly about what is not working, which is necessary to identify real improvements. This supports the team's ownership of its actions and aligns with the Scrum Master's role in facilitating team events and fostering self-management.

Coaching the Product Owner and the team is a key servant-leader behavior. By helping the PO with backlog refinement and the team with estimation, the Scrum Master improves the system in which the team works. This supports better planning and delivery without taking over decision-making. It reflects the Scrum Master's role as a teacher and mentor, and it aligns with SAFe's focus on continuous improvement and cross-functional collaboration.

Facilitating root-cause analysis allows the team to pinpoint systemic issues like technical debt and generate actionable improvement stories. This directly supports continuous learning and continuous improvement, which are core pillars of the SAFe House of Lean framework.

This approach builds the team's capability to self-manage by teaching problem-solving skills and progressively handing over responsibility. It aligns with the Scrum Master / Team Coach as a servant leader and coach, who should develop the team's autonomy rather than create dependency.

This is correct because the Scrum Master should coach the team to self-manage by helping them reconnect the Daily Stand-up to its purpose: inspecting progress toward the Iteration Goals and adapting the plan. By asking questions rather than imposing rules, the Scrum Master enables the team to own the solution, which aligns with SAFe's principle of decentralized decision-making and the Scrum Master's role as a servant-leader and coach.

Bringing the dependent teams together enables them to visualize risks and dependencies on the program board and negotiate realistic delivery commitments. This proactive facilitation directly addresses the root cause of isolated planning by reinforcing cross-team communication and synchronization.

Facilitation is the Scrum Master's primary contribution to the Iteration Review. By managing the time and keeping the focus on feedback, the Scrum Master ensures the event is valuable for both the team and the stakeholders. This helps the team learn from the demo and align their future efforts.

Holding the meeting at the end of Day 1 provides leadership with immediate visibility into draft plan bottlenecks. Management collaborates overnight to resolve scope or dependency issues so teams can finalize realistic plans on Day 2.

The Iteration Review is intended to inspect the Increment and adapt the backlog based on stakeholder feedback. When it devolves into a status presentation, the Scrum Master should coach the Product Owner and team on its true purpose and facilitate a format change. This collaborative approach respects the Product Owner's ownership while ensuring the event delivers value through demonstration and dialogue, not passive listening.

Effective Scrum Masters foster cross-team collaboration to resolve blockers early. By facilitating direct communication, the team gains the necessary information to make a realistic commitment. This proactive behavior aligns with the SAFe principle of synchronizing across domains, ensuring the team's plan is based on reality rather than guesswork.

The I&A event includes a structured problem-solving workshop where the ART analyzes metrics, identifies root causes, and generates improvement backlog items. This is the prescribed SAFe approach to address systemic issues like declining predictability. The Scrum Master facilitates this workshop to help the ART learn and adapt, ensuring that corrective actions are data-driven and owned by the teams.

Facilitation is the core skill of a Scrum Master. By guiding the team to create specific, measurable, and actionable improvement items, the Scrum Master ensures the team makes tangible progress. This proactive approach turns vague desires into concrete plans, which is essential for continuous improvement in an Agile organization.

Synchronizing all teams to the same cadence is mandatory for SAFe. This alignment enables the System Demo, simplifies dependency management, and allows the ART to maintain a predictable delivery rhythm. It ensures that every team contributes their work for integration at the same time, preventing bottlenecks and late-stage integration conflicts.

The Daily Stand-up is for the team to inspect progress toward the iteration goal and adapt the plan, not to report to the Scrum Master. The Iteration Review and Retrospective are essential Scrum events in SAFe; skipping them removes inspection and adaptation. Re-establishing their purpose and cadence is the Scrum Master's core coaching responsibility.

Facilitating events such as Iteration Planning, Daily Stand-up, Iteration Review, and Retrospective and coaching Scrum and SAFe principles are core Scrum Master responsibilities. This work builds the team's self-management and helps it operate effectively inside the Agile Release Train. It also keeps the Scrum Master in a servant-leader stance rather than a command-and-control one, which is essential when introducing Scrum.

Coaching both the Product Owner and the team on backlog refinement addresses the root cause of unclear items. Refinement ensures stories meet the team's definition of ready before planning, reducing mid-Iteration churn and improving commitment quality. This is a core Scrum Master / Team Coach responsibility: building effective collaboration between the team and the Product Owner without taking over either role.

A plan with no buffers is highly likely to fail if any risk materializes. The Scrum Master guides the team to use historical velocity and leave space for the 'unknown unknowns,' ensuring that the final commitment is something the team can actually stand behind with confidence.

The Scrum Master is responsible for keeping the Daily Stand-up focused and time-boxed. Facilitating a 'meet-after' ensures the technical debate is handled by the relevant parties without wasting the entire team's time. This preserves the meeting's utility while ensuring the technical problem is acknowledged and scheduled for resolution.

Analyzing the root cause is the foundational step for improvement. By looking at the data from the iteration, the team can determine if their estimation is off, if stories are too large, or if they have too many external dependencies. This allows for data-driven changes to their process.

Rotating facilitation builds shared ownership of team events and develops facilitation skills across the team. It reduces reliance on the coach and encourages members to take responsibility for the quality of discussions and decisions. This is a practical way to grow self-management while keeping the coach available for deeper coaching and ART-level work.