SSM Questions and Answers

According to the SAFe 6 Scrum Master documentation, one of the ways a Scrum Master/Team Coach can help improve ART performance is to facilitate cross-team collaboration. Cross-team collaboration is the ability of Agile teams to work together effectively and efficiently to deliver value to the customers and stakeholders. It involves sharing information, resolving dependencies, aligning on goals, and providing feedback. Cross-team collaboration is essential for achieving the ART vision and objectives, as well as for delivering integrated and high-quality solutions.

The Scrum Master/Team Coach plays a key role in facilitating cross-team collaboration by 1:

Participating in the Scrum of Scrums (SoS) and ART Sync meetings, where they communicate the team’s progress, impediments, and dependencies, and coordinate with other teams and the Release Train Engineer (RTE)

Helping the team prepare for and participate in the PI Planning event, where they collaborate with other teams to define and commit to the PI objectives and identify risks and dependencies

Supporting the team in the System Demo, where they demonstrate the team’s work to other teams and stakeholders, and receive feedback and validation

Assisting the team in the Inspect and Adapt (I&A) event, where they review the ART performance, identify improvement opportunities, and create action plans

Encouraging the team to adopt Communities of Practice (CoPs), where they share knowledge, best practices, and learnings with other teams and experts

Promoting a culture of trust, respect, and cooperation among the team and other teams

One way a Scrum Master/Team Coach can support productive team Backlog Refinement sessions is to ensure subject matter experts are invited. Subject matter experts (SMEs) are people who have specialized knowledge or skills related to the domain or technical aspects of the product or solution. They can provide valuable input and feedback to the team during Backlog Refinement, such as clarifying requirements, validating assumptions, identifying dependencies, and suggesting solutions. SMEs can also help the team to split, estimate, and prioritize the backlog items more effectively and accurately. By inviting SMEs to the Backlog Refinement sessions, the Scrum Master/Team Coach can facilitate better collaboration, communication, and alignment among the team and the stakeholders.

One Iteration Retrospective anti-pattern is when the team only brings up issues that are outside of their control to address, such as organizational policies, external dependencies, or stakeholder expectations. This can lead to frustration, helplessness, and cynicism among the team members, as well as a loss of focus on their own improvement opportunities12 

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.

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.

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.

According to the SAFe 6 Scrum Master documentation, one of the elements on the Scrum Master/Team Coach responsibility wheel is to facilitate PI Planning. PI Planning is a two-day event where all the teams and stakeholders of an Agile Release Train (ART) collaborate to align on a common vision, define and commit to the PI objectives, and identify and manage risks and dependencies. The Scrum Master/Team Coach facilitates PI Planning by 1:

Helping the team prepare for the event, such as reviewing the business context, vision, and backlog, and creating draft plans

Supporting the team during the event, such as facilitating breakout sessions, resolving issues, and ensuring alignment and collaboration with other teams

Assisting the team after the event, such as finalizing the plans, updating the PI board, and conducting a retrospective

Facilitating PI Planning is one of the ways the Scrum Master/Team Coach helps the team and the ART achieve their goals and deliver value.

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 of the best practices Scrum Masters/Team Coaches can use to run successful meetings is to leave meetings with clear action items. Action items are specific tasks that need to be done by a certain person or group by a certain deadline. They help the team to follow up on the outcomes of the meeting, track progress, and ensure accountability. Action items should be SMART: Specific, Measurable, Achievable, Relevant, and Time-bound. Scrum Masters/Team Coaches should document and communicate the action items to the team and stakeholders, and review them in the next meeting.