SSM Flashcards — Free SAFe Scrum Master Study Cards

Escalate the uncommitted cross-ART dependencies to the Management Review and Problem-Solving session at the end of Day 1.

The Scrum Master must guide the team to surface these cross-ART dependencies immediately during the management review and problem-solving session at the end of Day 1. This ensures leadership from both trains can negotiate solutions, adjust scope, or reallocate capacity before finalizing the plan on Day 2, keeping the program increment aligned.

Facilitate a session to map team stories and iteration goals directly to PI objectives.

Effective alignment in SAFe requires the Scrum Master to coach the team on connecting their daily work to the broader PI objectives established during PI Planning. By ensuring the team understands how their stories contribute to the ART's business value, the Scrum Master fosters transparency and shared accountability. This alignment is critical because it ensures that autonomous Scrum teams remain synchronized with the train's strategic goals and deliver consistent value.

Facilitate direct conversations and alignment sessions with the dependent team's Scrum Master and relevant stakeholders to map out interface dependencies.

The Scrum Master facilitates cross-team collaboration by engaging the System Architect and other Scrum Masters during the Agile Release Train sync events. This systemic impediment requires structural alignment and dependency mapping rather than internal pressure, ensuring the team can predictably deliver value in future iterations while fostering healthy organizational networks.

Facilitate a direct conversation with the supplier team, highlight the risk on the program board, and adjust team objectives accordingly.

The Scrum Master must facilitate transparent collaboration during PI Planning by ensuring the dependency is formally documented on the program board and discussed with the dependent team. Escalating early to management and product management helps resolve bottlenecks before final commitments are made, maintaining alignment across the Agile Release Train.

Brainstorm potential solutions to address the lack of automation.

The Problem-Solving Workshop follows a structured process: identifying the problem, performing root cause analysis, brainstorming solutions, and creating action items. Once a root cause is identified, the focus must shift to creative solution generation to ensure the problem is addressed effectively in the next Program Increment planning session.

Facilitate direct alignment sessions between the dependent teams to map out dependencies, negotiate delivery sequences, and update the program board.

Facilitating cross-team collaboration during PI Planning is essential for managing inter-team dependencies and aligning delivery. By encouraging teams to actively negotiate dependencies and map them on the program board, the Scrum Master ensures transparency and shared understanding. This collaborative approach directly supports the SAFe principle of synchronizing alignment and execution across all participating teams within the Agile Release Train.

Ensure that the discussion focuses on identifying and clearing impediments to progress.

The Scrum Master acts as a facilitator, ensuring that the Team Sync remains focused on the iteration goal and progress toward the objectives. By fostering an environment where team members feel safe to share progress and challenges, the Scrum Master promotes transparency and collective ownership of the iteration's success, which is critical for identifying and clearing impediments quickly.

Raise the issue in the Coach Sync and facilitate a discussion among the Scrum Masters to help the teams align on a shared definition of done.

Misaligned definitions of done across teams cause integration problems that surface at the System Demo. The Coach Sync is the right venue for Scrum Masters to collaborate and help their teams converge on a shared definition of done. This preserves team ownership while enabling the integration and frequent delivery that the ART requires, rather than mandating from above or avoiding the demo.

Introduce a Definition of Ready and coach the team to use it during backlog refinement to ensure stories are sufficiently elaborated before Iteration Planning.

The most effective action is to introduce a Definition of Ready and coach the team to use it during backlog refinement. This directly addresses the root cause of unrefined stories. It is a collaborative, coaching-oriented approach that empowers the team to improve their own process, aligning with the Scrum Master / Team Coach role in SAFe.

Ensuring team dependencies are identified, visualized, and tracked.

The Scrum Master ensures that their team's dependencies are clearly visualized and tracked on the Program Board. They facilitate the communication needed to resolve these dependencies, which is critical for program-level coordination. This role is important because the Program Board is the primary tool for managing cross-team synchronization; if dependencies are not tracked, the entire train's ability to meet PI objectives is severely compromised.

Coach the teams to demonstrate the integrated solution from the staging environment so stakeholders can assess real progress.

The System Demo is the ART's opportunity to inspect the integrated solution produced by all teams during the Iteration, demonstrated in a staging or production-like environment. Replacing live demonstration with slides or reports defeats its empirical purpose. The Scrum Master should coach teams back to demonstrating working, integrated functionality so stakeholders can give informed feedback.

Capture the integration gap as a Program-level impediment and immediately drive the integration so the Feature can be demonstrated at the next System Demo.

The System Demo is the ART's integrated inspect-and-adapt event, so a missing cross-team integration is a Program-level impediment rather than a local team matter. Surfacing it to the RTE and driving the integration restores transparency and lets the ART adapt. Deferring, isolating, or avoiding the demo all hide the problem and prevent the coordinated fix the dependency requires.

Facilitate further planning to address the concerns that led to the low vote.

A low confidence vote indicates that the ART does not believe the plan is achievable. This requires the ART to go back into a planning session to address the concerns. The Scrum Master supports this by helping the team identify the specific reasons for their low confidence and collaborating on plan adjustments.

Explain that the Daily Stand-up is kept in SAFe to inspect progress toward the Iteration Goal, synchronize the day's work, and surface impediments, and help the team run it effectively across time zones.

The Daily Stand-up remains a core team event in SAFe because it lets the team inspect progress toward the Iteration Goal, plan the day's work, and surface impediments. Distributed teams adapt how they run it, but removing it or making it weekly would break the daily feedback cycle and reduce the team's ability to self-organize.

Record the blocker and facilitate a brief after-event conversation with the relevant team members to route it through the appropriate ART coordination mechanism.

The Scrum Master supports the Team Sync by protecting its timebox and purpose while ensuring blockers become visible and are routed correctly. Capturing the dependency and facilitating a short follow-up after the event keeps the team synchronized, respects self-organization, and uses SAFe's ART coordination mechanisms to address cross-team impediments.

Redirect the conversation to the product outcomes and offer to schedule a separate technical discussion with the stakeholder after the review.

The Iteration Review is for inspecting the increment and collecting stakeholder feedback, not for resolving technical design debates. The Scrum Master should keep the event on track by redirecting the technical discussion to a separate forum. This preserves the event's purpose, respects the stakeholder's concern, and ensures the team still benefits from broader feedback.

Coordinate with the System Team to ensure the team's increment is integrated and ready.

The System Demo is the primary measure of ART progress, showing a fully integrated system increment. The Scrum Master's role is to ensure the team is prepared to contribute their part of the integrated demo. This involves coordinating with other teams and the System Team to ensure the 'Definition of Done' is met and the work is ready for stakeholders.

Daily Stand-up

The Daily Stand-up is the dedicated event for team synchronization. By meeting daily for a brief period, the team communicates progress, identifies dependencies, and raises blockers. This regular cadence ensures that the team remains aligned, informed, and capable of addressing issues quickly, which is fundamental to maintaining flow and meeting the iteration objectives.

Help the team define a specific improvement story for the PI Planning backlog.

The Problem-Solving Workshop is designed to produce actionable improvement items. Once a root cause is identified, the Scrum Master must guide the team to create specific, measurable backlog items that can be integrated into the next PI. This ensures that the I&A results in real change rather than just identifying complaints.

Coach the team that the Iteration is the planning horizon for team-level commitment, while the PI Objectives and team PI plan represent the broader forecast they refine with their Product Owner and during the Inspect and Adapt workshop.

Within SAFe, the Iteration remains the team's commitment horizon, while the Program Increment is a forecast captured through team PI Objectives. Keeping the detailed, committable plan at the Iteration level and refining the PI plan with the Product Owner and during the Inspect and Adapt workshop preserves Scrum's empirical control while fitting the train's cadence.

Establish facilitation techniques that encourage equal participation and create psychological safety for quieter members.

The Scrum Master must act as a facilitator who actively draws out quieter team members by employing inclusive facilitation techniques, ensuring all voices contribute to problem-solving. Fostering psychological safety and equal participation maximizes team intelligence and drives better technical outcomes.

Facilitate a deep-dive session into estimation techniques and the importance of Backlog Refinement.

The Scrum Master serves as a coach for the team, helping them understand and apply Lean-Agile values. By facilitating estimation techniques like Planning Poker and ensuring the definition of ready is met, the Scrum Master ensures the team does not overcommit based on historical velocity. This protects predictability and fosters a sustainable pace, which is essential for maintaining long-term productivity and quality.