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

Answer : C

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.

:

CALMR - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline

Answer : A

During PI Planning, teams are expected to create draft PI Objectives that summarize the business value they intend to deliver. However, a common anti-pattern occurs when teams spend too much time analyzing each Story instead of focusing on higher-level outcomes.

The goal of draft objectives is to express intent, alignment, and expected value---not to finalize every technical detail or task. Over-analyzing individual stories during PI Planning slows progress, distracts from collaboration with other teams, and limits the time available for identifying dependencies and risks.

From SAFe guidance:

''Teams should avoid excessive analysis of stories during PI Planning. The focus should be on creating draft objectives that align with business value and ART goals.''

Thus, the correct answer is A. Too much time is spent analyzing each Story, as it prevents the team from maintaining the right level of planning abstraction.

Answer : D

Timeboxing discussions is a key Agile development practice that supports efficiency, focus, and predictability in team events and collaboration. A timebox sets a maximum duration for an activity, ensuring that meetings or working sessions remain purposeful and do not overrun.

Agile and SAFe both emphasize timeboxing for events such as Iteration Planning, Daily Team Syncs, Iteration Reviews, and Retrospectives. This discipline encourages concise communication, prioritization of topics, and respect for everyone's time.

From SAFe guidance:

''Agile Teams use timeboxing to help ensure meetings are effective and efficient, maintain focus on outcomes, and support a predictable rhythm for collaboration.''

Other options such as sequencing processes or exploring diagnostics do not represent standard Agile team development practices. Facilitating meetings is a Scrum Master responsibility, not a development practice.

Thus, the correct answer is D. Timeboxing discussions.

Answer : C

The Coach Sync (sometimes referred to as the Scrum of Scrums or SM/TC Sync) is a coordination event within SAFe where Scrum Masters and Team Coaches from the Agile Release Train (ART) meet to discuss progress, dependencies, and impediments that affect multiple teams.

This event provides a forum for escalating and addressing ART-level impediments that cannot be resolved within a single team. The RTE (Release Train Engineer) typically facilitates this meeting to ensure transparency and problem-solving across teams.

From SAFe guidance:

''The Coach Sync allows Scrum Masters and Team Coaches to discuss cross-team progress and impediments, escalating those that require ART-level visibility or resolution.''

Therefore, the correct answer is C. Coach Sync. This event enables effective synchronization among teams and promotes continuous improvement across the ART.

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 : D

According to SAFe, the Iteration Retrospective is a key event that enables relentless improvement, one of the pillars of the SAFe House of Lean. The purpose is to reflect on the previous iteration and identify what went well, what didn't, and what can be improved.

An essential outcome of this meeting is a set of actionable improvement items that can be added to the team backlog. These items are often captured as improvement Stories, ensuring that process enhancements are visible, prioritized, and implemented in the next iteration.

From SAFe guidance:

''The retrospective concludes with actionable improvement items added to the backlog. These items should be implemented in subsequent iterations to improve performance.''

Therefore, the correct answer is D. Ensure the event ends with actionable improvement items for the backlog, as it ensures continuous learning and measurable improvement.

Answer : C

One anti-pattern that emerges when teams do not spend enough time refining the backlog is that they enter new Iterations without enough Stories prepared.This can result in several negative consequences, such as:123

The team may struggle to plan and commit to the Iteration Goals, as they lack clarity, feasibility, and testability of the Stories.

The team may face delays, rework, and waste, as they encounter unanticipated dependencies, risks, or technical issues during the Iteration.

The team may deliver low-quality or incomplete Stories, as they rush to meet the Iteration deadlines or compromise on the Definition of Done.

The team may lose focus, alignment, and motivation, as they work on ambiguous or unrealistic Stories that do not deliver value to the customers or the organization.

To avoid this anti-pattern, the team should dedicate sufficient time and effort to refine the backlog on a regular basis, preferably every Iteration123Backlog 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 Backlog4One 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 Iteration2By doing so, the team can improve the quality, efficiency, and effectiveness of their work, as well as deliver value to the customers and the organization