SSM-6.0 Safe Scrum Master Practice Questions

The statement is false. In SAFe and Agile, the entire Agile Team is responsible for quality. The principle of Built-in Quality means that quality is not an afterthought or the responsibility of a single person or department. The Scrum Master's role is to coach the team on quality practices and ensure they have a strong Definition of Done, but the ownership of quality resides with the team members who build the solution.

Encouraging practices like pair programming and organizing internal knowledge sharing sessions (e.g., brown bags) is a collaborative and effective way to foster T-shaped skills. This approach allows team members to learn from each other in a supportive environment, gradually broadening their skill sets and breaking down knowledge silos without forcing them into unfamiliar work. It builds collective ownership and resilience.

The fishbone diagram, also known as an Ishikawa or cause-and-effect diagram, is a root cause analysis tool. Its purpose is to help teams systematically brainstorm and categorize the potential causes contributing to a specific problem (the 'effect'). This structured approach helps ensure that the team considers all possible factors before jumping to conclusions or solutions.

An anti-pattern for the Iteration Review is treating it as a formal status meeting for management rather than a collaborative session to gather feedback on a working increment. The focus should be on demonstrating the solution, discussing progress toward the Iteration Goals, and adapting the backlog based on feedback. When it becomes a one-way status report, its value as a feedback loop is lost.

SAFe applies Kanban systems at multiple levels (Portfolio, ART, and Team) to visualize, manage, and optimize the flow of value. These systems make bottlenecks visible, help implement pull-based flow, and use Work-in-Process (WIP) limits to improve throughput and predictability.

The 'Circles of Influence' (or 'Circle of Control') exercise is a powerful coaching tool that helps teams differentiate between areas they can directly control, areas they can influence, and areas that are simply concerns. This technique effectively shifts the focus from blaming external factors to identifying actionable steps within their immediate control or sphere of influence, which is the primary goal of a retrospective.

SAFe Principle #4 emphasizes the importance of integration. Building incrementally is not enough; the increments must be integrated to create a cohesive whole. The problem described—work being 'done' but not integrated—is a classic violation of this principle. Fast, integrated learning cycles mean that teams should be integrating their work frequently (ideally continuously) to identify and resolve issues early, rather than waiting for the System Demo.

This action demonstrates the Scrum Master's role as a coach and servant leader. Instead of escalating or creating workarounds, the first step is to engage directly with the individual to understand the root cause of the problem and offer support.

Creating a working agreement makes expectations explicit for everyone. It's a collaborative way to define how the team and Product Owner will work together, including their respective commitments to events like Backlog Refinement, which addresses the issue systemically.

This action directly addresses the root cause identified in the case study: inconsistent DoD and lack of integration standards. By creating a shared ART-level DoD, all teams align on the quality and integration expectations for their work. This is a systemic solution that promotes Built-in Quality and ensures that 'done' means integrated and tested, preventing the issues seen in the first PI. It is a proactive, collaborative approach that empowers the teams to solve the problem.

The statement is false. The Team Backlog in SAFe contains User Stories, which deliver direct business value, and Enabler Stories. Enabler Stories are used to build the architectural runway, explore requirements, or improve infrastructure, which are necessary to support future business functionality.