Practice Free SSM SSM (6.0) - SAFe Scrum Master Practice 6.0 Exam Questions Answers With Explanation

According to the SAFe 6 Scrum Master documentation, one of the ways teams can use Iteration planning to stay aligned on their work is by committing to a set of goals to be delivered. Iteration goals are a summary of the business and technical outcomes that the team intends to achieve in the Iteration. They are based on the stories selected from the team backlog, the team’s capacity, and the acceptance criteria. By committing to a set of goals, the team creates a shared understanding of the purpose and scope of the Iteration, as well as the expected value and quality. The team also aligns with the ART vision and objectives, and communicates their commitment to the stakeholders and customers. Iteration goals help the team to stay focused, motivated, and accountable throughout the Iteration.

A safe environment for taking risks without fear of embarrassment or criticism is one of the characteristics of a high-performing Agile Team. A high-performing Agile Team is a cross-functional group of people that have everything, and everyone, necessary to produce a working, tested increment of product1 They are empowered, collaborative, aligned, and committed to delivering value to the customers and the organization2 One of the factors that enable a high-performing Agile Team is a safe environment where team members can experiment, learn, and grow without fear of failure, blame, or judgment3 A safe environment fosters a culture of innovation, creativity, and continuous improvement, as well as a sense of psychological safety, trust, and belonging among team members4 Team C is demonstrating this characteristic by creating a new workflow to speed up the testing process, even though it did not work out as expected. The rest of the team was excited to hear what was learned from the failed experiment, rather than being disappointed or critical. This shows that the team values learning over perfection, and supports each other in taking risks and trying new things.

The problem-solving workshop is the third part of the Inspect and Adapt (I&A) event in SAFe®. Its main purpose is to use structured root cause analysis to develop solutions to recognized problems that blocked or slowed work during the Program Increment (PI).

Teams and ART stakeholders collaboratively identify systemic issues using techniques like the 5 Whys or fishbone diagrams. They then define concrete improvement actions, which are prioritized and added to the improvement backlog for implementation in the next PI.

From SAFe guidance:

“The purpose of the problem-solving workshop is to identify the root causes of systemic issues that impacted performance during the PI and create improvement actions to address them.”

Therefore, the correct answer is D. Developing solutions to recognized problems that blocked or slowed work.

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 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).

According to the SAFe 6 Scrum Master documentation, one of the ways a servant leader can support team members in decision-making is by giving each team member the opportunity to contribute. This means that the servant leader encourages and facilitates the participation of all team members in the decision-making process, ensuring that everyone’s voice is heard and valued. By giving each team member the opportunity to contribute, the servant leader fosters a culture of collaboration, empowerment, and trust, as well as increases the quality and buy-in of the decisions.

The Iteration Retrospective is a core event in SAFe® and Scrum where the team reflects on the past iteration to identify ways to improve processes, collaboration, and effectiveness. One of the most powerful ways to transform retrospective insights into action is by writing improvement Stories.

An improvement Story is treated like any other backlog item—it is estimated, prioritized, and included in the upcoming iteration backlog to ensure continuous, measurable progress toward higher performance. This approach aligns with SAFe’s focus on Relentless Improvement, a pillar of the SAFe House of Lean.

From SAFe guidance:

“Teams record improvement items as stories and include them in the next iteration backlog. This ensures that improvement work receives visibility, commitment, and action.”

Thus, the correct answer is B. By writing improvement Stories, as it ensures improvement actions are tangible, trackable, and continuously implemented.

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.

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.

Hackathons are one of the activities that can be done during the IP Iteration to foster innovation and learning. They allow the team members to work on whatever they want, with whomever they want, as long as the work reflects the mission of the company. The teams then demo their work to others at the end of the hackathon. Hackathons can help the team explore new ideas, technologies, and solutions that can benefit the business and the customers. They can also increase the team’s engagement, creativity, and collaboration. References: Innovation and Planning Iteration - Scaled Agile Framework, Exam Study Guide: SSM (6.0) - SAFe® Scrum Master

A servant leader is defined in SAFe® as someone who prioritizes the growth, well-being, and development of their team over personal or organizational agendas. Rather than exercising authority or control, servant leaders empower, support, and enable their teams to achieve autonomy and high performance.

Scrum Masters and Team Coaches embody this leadership style by removing impediments, fostering collaboration, and promoting a safe environment for experimentation and learning. The servant leader’s goal is to help the team reach its full potential, not to command or direct.

From SAFe guidance:

“Servant leaders focus on the growth and well-being of people and the communities to which they belong. They put the needs of others first and help people develop and perform as highly as possible.”

Therefore, the correct answer is A. A leader that prioritizes the needs and growth of the team over their own priorities.

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.

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.

According to the SAFe® (Scaled Agile Framework) guidelines, an effective Scrum Master or Team Coach (SM/TC) exhibits several key traits that enable them to support Agile Teams effectively. One of the most emphasized characteristics is the ability to navigate conflict constructively.

A "conflict navigator" refers to someone who helps the team identify and work through disagreements in a productive way. Rather than avoiding or suppressing conflict, a skilled Scrum Master uses it as an opportunity to surface issues, enhance team learning, and drive continuous improvement. This aligns with the servant-leadership stance encouraged both in SAFe and the Scrum Guide.

While traits like being charismatic or ambitious may be personally beneficial, they are not explicitly listed in SAFe or Scrum literature as core attributes for Scrum Masters. Similarly, competitiveness could actually contradict the collaborative, team-focused nature of Agile frameworks.

From the SAFe® Scrum Master role description:

“Effective Scrum Masters are servant leaders who display characteristics such as active listening, empathy, persuasion, and conflict facilitation.”

This highlights the importance of conflict facilitation, making “Conflict navigator” the correct answer.

For full reference, see:

???? SAFe Scrum Master Role – Scaled Agile Framework

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

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.

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.

Respect is one of the five Scrum values that can help Agile Teams create transparency. Respect means that team members value each other’s opinions, skills, and contributions, and treat each other with dignity and professionalism. Respect also means that team members are honest and open with each other, and share information and feedback without hiding or withholding anything. By respecting each other, Agile Teams can foster a culture of trust and collaboration, where everyone feels comfortable to express their ideas, concerns, and issues, and work together to solve them. Transparency is essential for Agile Teams to inspect and adapt their work, and to align their actions with the vision and goals of the organization.

According to the SAFe 6 Scrum Master documentation, one of the metrics that are reported at the Inspect and Adapt event is the ART predictability measure. This metric shows how well the ART delivers on its PI objectives, which are the SMART commitments made by the teams during PI planning. The ART predictability measure is calculated by dividing the total actual business value achieved by the total planned business value, as shown in the PI system demo. The ART predictability measure helps the ART to assess its performance, identify gaps, and improve its forecasting accuracy and reliability.

One method a Scrum Master/Team Coach can use to help teams overcome a fear of conflict is to give every team member the opportunity to contribute. Fear of conflict is one of the common dysfunctions of a team, which can result in artificial harmony, lack of trust, and avoidance of issues1 To overcome this fear, the Scrum Master/Team Coach can facilitate a safe and respectful environment where team members can express their opinions, ideas, and concerns without being judged, ignored, or attacked23 Giving every team member the opportunity to contribute can help them feel valued, respected, and heard, as well as foster a culture of collaboration, feedback, and learning45 The Scrum Master/Team Coach can use various techniques to ensure equal participation, such as round-robin, fist of five, dot voting, silent brainstorming, and liberating structures45 By encouraging healthy and constructive conflict, the Scrum Master/Team Coach can help the team improve their performance, creativity, and innovation23

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.

One practice Scrum Masters/Team Coaches can use to facilitate conflict management is to enforce working agreements. Working agreements are a set of guidelines that define how a team wants to work together, communicate, and collaborate. They are created by the team members themselves and reflect their shared values, norms, and expectations. Working agreements can help prevent or reduce conflicts by establishing clear boundaries, roles, and responsibilities, as well as by promoting respect, trust, and transparency among team members. Working agreements can also help resolve conflicts by providing a common reference point and a framework for constructive feedback and dialogue. Scrum Masters/Team Coaches can support the team in creating, reviewing, and updating their working agreements, as well as in holding each other accountable for following them.