SSM SSM (6.0) - SAFe Scrum Master Practice 6.0 Questions and Answers

One example of an Agile Team development practice is to demo working functionality frequently to the product owner and other stakeholders. This practice helps the team to get fast feedback, validate their assumptions, and ensure that they are delivering value that meets the customer needs and expectations. Demoing frequently also helps the team to improve the quality of their work, as they have to ensure that the functionality is tested and meets the definition of done before showing it to others. Demoing frequently is part of the SAFe Scrum and SAFe Team Kanban practices, and is done at the end of each iteration in the Iteration Review event.

According to the SAFe® Iteration Review process (adapted from Scrum’s Sprint Review), the primary goal is to inspect the completed increment and gather feedback from stakeholders. This event focuses on demonstrating working software or system increments produced during the iteration. The team and stakeholders then discuss what was accomplished, any changes in priorities, and what might be done next to ensure continuous alignment with business needs.

The Iteration Review is not about planning or adding new acceptance criteria (which happens during refinement) nor about demonstrating work from a previous PI. Instead, it’s about validating the current increment and using feedback to adjust the upcoming work accordingly.

From SAFe guidance:

“The Iteration Review provides a mechanism for the team to demonstrate the increment to stakeholders and collect feedback. This feedback helps ensure that the team continues to deliver value aligned with customer needs.”

Therefore, the correct answer is D. To receive feedback on the increment, as this is the key objective of the Iteration Review.

One purpose of iteration goals is to align team members to a common purpose and vision. Iteration goals are a high-level summary of the business and technical goals that an Agile Team agrees to accomplish in an iteration. They help the team and the product owner to reach agreement on the business value they intend to deliver, align their work to their team PI objectives, and ground everyone on their shared purpose. Iteration goals also provide transparency and management information, as well as support the coordination and dependency management of the Agile Release Train (ART).

An essential coaching technique for Scrum Masters/Team Coaches in SAFe® is asking powerful questions. Instead of providing direct solutions, effective Scrum Masters guide the team toward self-discovery and collaborative problem-solving.

Powerful questions are open-ended, thought-provoking inquiries that stimulate deeper reflection and creative thinking. This approach aligns with the servant-leader mindset, enabling team members to take ownership of their challenges and develop collective accountability.

Examples include:

“What options have we not yet considered?”

“What’s the smallest next step we could take?”

“What’s blocking our progress, and how might we remove it together?”

From SAFe guidance:

“Scrum Masters and Team Coaches enable teams to find their own solutions by asking powerful questions rather than providing answers. This encourages collaboration and fosters a culture of continuous learning.”

Therefore, the correct answer is A. Asking powerful questions, as it directly supports self-management and team empowerment.

In SAFe® and Scrum, acceptance criteria define the conditions that must be met for a User Story to be considered complete and accepted by the Product Owner. These criteria clarify how the Story will be validated and serve as the basis for confirming that functionality meets expectations and quality standards.

Acceptance criteria support transparency, alignment, and shared understanding between the team and stakeholders. They guide development, testing, and validation efforts and are essential for achieving the Definition of Done (DoD).

From SAFe guidance:

“Acceptance criteria define the boundaries and validation conditions of a Story. They ensure the implemented functionality meets the customer’s intent and can be accepted.”

Therefore, the correct answer is A. To identify how the Story can be validated, as this captures the core purpose of acceptance criteria.

One benefit of PI Planning is that it allows for faster decision-making by bringing together all the members of the Agile Release Train (ART) and the relevant stakeholders in a face-to-face (or virtual) event. PI Planning provides an opportunity for the ART to align on a common vision and mission, review the business context and priorities, identify and resolve dependencies and risks, and commit to a realistic and achievable plan for the next Program Increment (PI). By having everyone involved in the planning process, the ART can leverage the collective knowledge and expertise of the participants, reduce ambiguity and uncertainty, and make informed and timely decisions that support the delivery of value to the customers.

One anti-pattern of the Inspect and Adapt (I&A) is to have no actionable improvement Features created as a result of the problem-solving workshop. This is considered an anti-pattern because the main goal of the I&A workshop is to identify and address the systemic issues that are limiting the effectiveness of the Agile Release Train (ART). The workshop should produce one or more improvement Features that are added to the ART backlog and prioritized for the next PI Planning event. These Features should be SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) and aligned with the ART vision and goals. Without actionable improvement Features, the ART will miss the opportunity to learn and improve from the feedback and data collected during the PI.

One of the main responsibilities of a Scrum Master/Team Coach is to facilitate team events, such as Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective. These events help the team to plan, execute, inspect, and adapt their work throughout the Iteration. By facilitating these events, the Scrum Master/Team Coach ensures that the team follows the Agile principles and practices, collaborates effectively, and delivers value to the customers and stakeholders.

In SAFe®, the Coach Sync (also known as the Scrum of Scrums or SM/TC Sync) is a coordination event for Scrum Masters and Team Coaches within an Agile Release Train (ART). The main purpose of this event is to gain visibility into team progress, discuss impediments, and ensure cross-team alignment.

Facilitated by the Release Train Engineer (RTE), the Coach Sync promotes transparency across the ART by allowing Scrum Masters to share information about iteration status, dependencies, and challenges that may affect other teams. It also serves as a forum for escalating ART-level impediments.

From SAFe guidance:

“The Coach Sync provides Scrum Masters and Team Coaches with visibility into progress and dependencies across teams and enables them to coordinate and remove impediments at the ART level.”

Thus, the correct answer is C. To gain visibility into progress, as this captures the event’s primary purpose.

Backlog Refinement is the Agile Team event where team members estimate relative story sizes. Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single iteration2 To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3 Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4 The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35 

Improving flow is a central responsibility of a Scrum Master/Team Coach (SM/TC) in SAFe®. One of the most effective ways to enhance flow is by establishing a Team Kanban board with the team.

A Kanban board visualizes the workflow, showing where work items are in the process and helping teams identify bottlenecks or work-in-progress (WIP) issues. By visualizing flow, the team can inspect, measure, and optimize how work moves from “To Do” to “Done.”

This approach aligns with SAFe’s Principle #6: Visualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengths, which promotes smoother, faster delivery and higher predictability.

From SAFe guidance:

“Teams use Kanban systems to visualize work, identify bottlenecks, and optimize flow. Scrum Masters/Team Coaches help teams establish and maintain their Kanban to improve throughput and reduce delays.”

Therefore, the correct answer is B. Work with team members to establish a team Kanban board, as it directly enables better visibility and flow management.

Among the five Scrum values — Commitment, Focus, Openness, Respect, and Courage — the value that most directly supports transparency is Openness.

In both Scrum and SAFe®, transparency is a foundational principle of empirical process control. Teams must be open about progress, impediments, challenges, and feedback to allow effective inspection and adaptation. When teams practice openness, trust grows, collaboration deepens, and issues are surfaced early rather than hidden.

The Scrum Guide (2020) states:

“The Scrum Team and its stakeholders are open about the work and the challenges. Openness encourages transparency, inspection, and adaptation.”

Similarly, SAFe encourages openness as part of the Lean-Agile mindset and team culture, ensuring alignment, honesty, and clarity across teams and ARTs.

Thus, the correct answer is B. Openness, as it directly enables transparency and honest collaboration.

The key benefit of transitioning from Waterfall to Agile delivery is the ability to deliver value to customers earlier and more frequently.

Traditional waterfall approaches deliver value only at the end of long development cycles, increasing risk and reducing adaptability. In contrast, Agile uses iterative and incremental delivery, allowing teams to release small increments of working solutions regularly. This provides faster feedback loops, improves responsiveness to change, and enhances customer satisfaction.

From SAFe guidance:

“Agile delivery enables teams to deliver value continuously and early, ensuring that customer feedback can be incorporated to improve outcomes and minimize risk.”

Therefore, the correct answer is C. Ability to deliver value to customers earlier, as this encapsulates one of the main advantages of Agile over waterfall.

The Team Sync (or Daily Stand-up) in SAFe® is a short, focused, timeboxed event that allows the team to align on progress toward iteration goals, identify impediments, and plan the next 24 hours.

The meeting promotes transparency and collaboration, ensuring that all team members are aware of progress and issues that could affect delivery. It also reinforces self-management by allowing the team to adapt plans daily based on new information.

From SAFe guidance:

“The Team Sync allows team members to align on progress toward iteration goals, discuss impediments, and adjust their plans to stay on track.”

Thus, the correct answer is A. The team aligns on the progress of Iteration Goals, as it captures the event’s primary intent.

By continuing to stay heads-down on the finalizing Feature delivery work, Team A might miss the chance to reflect on their team work more holistically and identify areas for improvement. The IP Iteration is intended to provide time for the team to participate in the Inspect and Adapt event, where they can review their PI performance, analyze the root causes of any issues, and create an improvement backlog. The IP Iteration also allows the team to engage in innovation and learning activities, such as hackathons, that can foster creativity, collaboration, and experimentation. These activities can help the team generate new ideas, solutions, and feedback that can benefit their future work. By skipping the IP Iteration, Team A might lose the opportunity to learn from their past experiences, improve their processes, and innovate their products. References: Innovation and Planning Iteration - Scaled Agile Framework, Exam Study Guide: SSM (6.0) - SAFe® Scrum Master

SAFe® defines seven core competencies that enable business agility. One of these is Agile Product Delivery, which focuses on building a customer-centric approach to defining, developing, and releasing valuable solutions.

This competency emphasizes Design Thinking, DevOps, continuous delivery, and release on demand to ensure fast, high-quality value delivery aligned with customer needs. While Built-in Quality is a foundational SAFe principle, it is not categorized as a core competency.

From SAFe guidance:

“Agile Product Delivery is a customer-centric approach to defining, building, and releasing a continuous flow of valuable products and services to customers and users.”

Therefore, the correct answer is B. Agile Product Delivery, as it is one of SAFe’s official seven core competencies.

Lean flow is one of the elements of the CALMR approach to DevOps in SAFe. It means applying lean principles and practices to optimize the flow of value from idea to production. Lean flow accelerates delivery by eliminating waste, reducing batch sizes, implementing pull systems, limiting work in process, managing queues, reducing handoffs, and applying cadence and synchronization. Lean flow enables faster feedback, shorter lead times, higher quality, and lower costs.

Norming is the stage of team development where team members stop focusing on their own goals and begin focusing on developing better ways of working together. Norming occurs after the team has gone through the Forming and Storming stages, where they have established their roles and responsibilities, and have resolved their initial conflicts and disagreements12 In the Norming stage, the team starts to build trust, respect, and cohesion among themselves. They also align on a common vision, mission, and goals, and agree on the norms and expectations for their collaboration and communication12 The team becomes more productive, efficient, and effective, as they leverage their collective strengths and skills, and support each other in overcoming challenges and delivering value12 The team also develops a sense of identity and pride, and celebrates their achievements and learnings12 

A key responsibility of the Scrum Master/Team Coach (SM/TC) in SAFe® is to support Iteration Execution. This involves ensuring that the team adheres to Agile principles, manages dependencies, removes impediments, and maintains focus on achieving iteration goals.

The Scrum Master facilitates team events, promotes collaboration, and helps the team continuously improve. They also assist in managing scope and ensuring transparency by tracking progress through iteration burndowns, Kanban boards, or burn-up charts.

From SAFe guidance:

“Scrum Masters support iteration execution, help the team meet iteration goals, and ensure all Scrum events are productive and within their timeboxes.”

Therefore, the correct answer is B. Supporting Iteration Execution, as it encapsulates a central part of the Scrum Master/Team Coach role.

One benefit of holding regular system demos is that execution can be measured across the whole ART. A system demo is a significant event that provides an integrated view of new Features for the most recent Iteration delivered by all the teams in the Agile Release Train (ART). Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI). The system demo offers the ART a fact-based measure of current, system-level progress within the PI. It’s the true measure of ART velocity and progress. Achieving this requires implementing the scalable engineering practices necessary to support Continuous Integration across the ART. By holding regular system demos, the ART can evaluate the quality, functionality, and usability of the solution, as well as identify and resolve any issues, risks, or dependencies. The system demo also provides an opportunity for feedback and learning from the customers, Business Owners, and other stakeholders, which can help the ART to align with the vision and goals, and to adapt to changing needs and expectations.

PI Planning is one of the events that aligns teams on a train. PI Planning is a cadence-based event for the entire Agile Release Train (ART) that aligns teams and stakeholders to a shared mission and vision. PI Planning provides an opportunity for the ART to review the business context and priorities, identify and resolve dependencies and risks, and commit to a realistic and achievable plan for the next Program Increment (PI). PI Planning is essential to SAFe: If you are not doing it, you are not doing SAFe1 

The intended value of the Backlog Refinement event is that the team is able to prepare requirements for Iteration Planning. Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single Iteration2 By doing so, the team can improve the quality, efficiency, and effectiveness of their work, as well as deliver value to the customers and the organization123

The Innovation and Planning (IP) Iteration in SAFe® serves a critical purpose—it provides time for innovation, learning, improvement, and preparation for the next Program Increment (PI).

When teams attempt to use the IP Iteration to continue their standard work, they lose the opportunity to rest, reflect, and prepare effectively for future planning. One of the key intended uses of the IP Iteration is to prepare for PI Planning, which includes reviewing objectives, refining backlogs, and ensuring readiness for upcoming work.

From SAFe guidance:

“The IP Iteration provides teams with the opportunity to innovate, improve, and prepare for the upcoming PI Planning event.”

Therefore, the correct answer is D. The team can prepare for PI planning, as this aligns with one of the primary goals of the IP Iteration.

In the Scaled Agile Framework (SAFe®), Scrum Masters or Team Coaches (SM/TCs) support their teams by making work visible and ensuring transparency around progress and delivery. One of the most effective tools for visualizing team delivery is the Burn-up Chart.

A Burn-up Chart shows progress toward the completion of work over time. It tracks the amount of work completed compared to the total scope, helping teams and stakeholders visualize how close they are to meeting iteration or PI objectives. This visualization enables data-driven discussions, supports predictability, and helps identify delivery risks early.

While other metrics like Cycle Time or Cumulative Flow Diagrams are valuable for measuring flow and efficiency, the Burn-up Chart specifically visualizes delivery progress.

From SAFe guidance:

“Teams use burn-up charts to visualize progress toward the goal and communicate delivery status. They enable transparency and support empirical planning and adaptation.”

Therefore, the correct answer is B. Burn-up chart—it is the primary visualization tool for tracking and communicating team delivery progress.