Scaled Agile SSM (6.0) - SAFe Scrum Master SSM Exam Questions

Answer : C

In the Scaled Agile Framework (SAFe), sustainable pace and predictable delivery are essential for high-performing Agile teams. An important signal that a team may be overcommitting to work is when team members begin pulling in work from future Iterations before completing the committed iteration backlog.

This behavior is an anti-pattern because it disrupts the cadence and predictability of the Agile Release Train (ART). It also undermines flow and focus, spreading the team's effort too thin across multiple iterations and reducing quality. Overcommitting leads to burnout, missed commitments, and lower morale, which negatively affect the team's long-term velocity and dependability.

According to SAFe:

''Teams should plan only as much work as they can complete within the iteration based on historical velocity and available capacity. Pulling work from future iterations indicates overcommitment or lack of focus on the planned goals.''

Therefore, C. Team members are pulling in work from future Iterations is the correct answer---it's a clear symptom of overcommitment and poor iteration discipline.

Answer : A

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.

Answer : D

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.

Answer : D

The Innovation and Planning (IP) Iteration is designed to give teams space for innovation, exploration, learning, and improvement, not for continuing regular feature work. When a team misuses the IP Iteration to ''catch up'' on delivery, it misses the opportunity to experiment, innovate, and explore new ways to deliver solutions more effectively.

This reduces the long-term adaptability and creativity of the team, limiting their ability to introduce process or technical improvements that could increase efficiency in future PIs. The IP Iteration is also a time for the Inspect and Adapt event and PI Planning, both of which are critical to continuous improvement.

From SAFe guidance:

''The IP Iteration provides dedicated time for innovation and planning. Using it for normal work diminishes opportunities to innovate, learn, and explore new approaches.''

Therefore, the correct answer is D. They could lose an opportunity to consider new approaches to Solution delivery.

Answer : D

Within a SAFe Agile Release Train (ART), all teams work together toward a common mission guided by a single Program Backlog. This shared backlog aligns every team's work to the same vision, ensuring coordination and synchronization.

This structure fosters transparency, dependency management, and alignment across all teams, allowing them to collaborate effectively while maintaining autonomy within their scope. The ART operates under the principle of ''aligning with a common mission and cadence.''

From SAFe guidance:

''All teams on an ART share a common vision and a single Program Backlog that defines the work necessary to realize that vision.''

Thus, the correct answer is D. A common mission using a single backlog.

Answer : C

In SAFe, the team backlog is the source of work for the Agile Team and includes all the user stories, enablers, and defects that represent potential upcoming work. It is owned and managed by the team, often guided by the Product Owner, who ensures the backlog remains prioritized and ready for iteration planning.

A crucial ongoing activity related to the backlog is refinement (or backlog refinement)---the process of reviewing, clarifying, and breaking down backlog items into smaller, well-understood Stories that are ready for implementation. During this activity, the team collaborates to ensure backlog items have sufficient detail, appropriate acceptance criteria, and relative sizing estimates.

From SAFe guidance:

''The team backlog is the source for stories, enablers, and defects planned in iterations. Teams continuously refine the backlog to ensure upcoming work is well understood and ready for planning.''

Therefore, the correct answer is C. The team backlog is where the team refines possible Stories.

Answer : B

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.