SSM Practice Questions

A constructive IP Iteration is one of the recommended practices for Scrum Masters/Team Coaches to

help teams avoid burnout, address technical debt, and foster innovation. An IP Iteration is a unique,

dedicated iteration that occurs every PI and provides an estimating buffer for meeting PI Objectives

and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events.

During the IP Iteration, teams can work on activities such as hackathons, research and design, spikes,

refactoring, automation, training, and other improvement initiatives that are difficult to fit into a

continuous, incremental value delivery pattern. An IP Iteration also allows teams to prepare for and

participate in the PI Planning and Inspect and Adapt events, which are essential for alignment,

collaboration, and learning across the ART. A constructive IP Iteration can improve the predictability

and flow of value delivery, increase employee engagement and satisfaction, enhance the agility and

resilience of the teams, and create a competitive advantage for the enterprise. (Must be taken from

SAFe 6 Scrum Master resources)

Reference:

Innovation and Planning Iteration - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline

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. (Must be taken from

SAFe 6 Scrum Master resources)

Reference:

CALMR - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline

One of the high-performing team characteristics that Team A is demonstrating is using regular

feedback loops built into the learning cycle. 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 organization1 One of the factors that enable a high-performing Agile Team is

using regular feedback loops to learn and improve. Feedback loops are mechanisms that provide the

team with information about the outcomes and impacts of their actions, as well as the needs and

expectations of their customers and stakeholders23 Feedback loops help the team to validate their

assumptions, measure their progress, and adjust their plans accordingly23 Feedback loops also help

the team to foster a culture of experimentation, innovation, and continuous improvement, as well as

to increase customer satisfaction and loyalty23 Team A is using regular feedback loops by releasing

the functionality with a method for collecting direct customer feedback. This allows them to learn

from the actual users of their product, and to incorporate their feedback into the next iteration of

development. This way, they can deliver value faster and more effectively, as well as to enhance the

quality and usability of their product4 (Must be taken from SAFe 6 Scrum Master resources)

Reference:

Feedback - Scaled Agile Framework

Agile Teams - Scaled Agile Framework

Feedback Loops: The Key to Building Better Products Faster | UserTesting Blog

The Importance of Customer Feedback in Product Development | SurveyMonkey

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. (Must be taken from SAFe 6 Scrum Master resources)

Reference:

PI Planning

Scrum Master/Team Coach

Say Hello to SAFe 6.0! - Scaled Agile Framework

One example of an Agile Team development practice is to demo working functionality frequently to

the product owner and other stakeholders. This practice helps the team to get fast feedback, validate

their assumptions, and ensure that they are delivering value that meets the customer needs and

expectations. Demoing frequently also helps the team to improve the quality of their work, as they

have to ensure that the functionality is tested and meets the definition of done before showing it to

others. Demoing frequently is part of the SAFe Scrum and SAFe Team Kanban practices, and is done

at the end of each iteration in the Iteration Review event.

Reference:

Iteration Review - Scaled Agile Framework

SAFe Team Kanban - Scaled Agile Framework

Agile Teams - Scaled Agile Framework

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. Reference: Innovation and Planning Iteration - Scaled

Agile Framework, Exam Study Guide: SSM (6.0) - SAFe® Scrum Master

The intended value of the Backlog Refinement event is that the team is able to prepare requirements

for Iteration Planning. Backlog 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 Backlog1 One 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 Iteration2 By doing so, the team can improve the quality, efficiency, and

effectiveness of their work, as well as deliver value to the customers and the organization123

Reference:

Team Backlog - Scaled Agile Framework

Backlog Refinement - Scaled Agile Framework

What is backlog refinement? | Miro

One recommended practice for Scrum Masters/Team Coaches when coaching teams on presenting a

draft plan at PI Planning is to align on how the team will answer questions about their proposed

objectives. This practice helps the team to prepare for the feedback and input they will receive from

the business owners, product management, and other teams and stakeholders during the draft plan

review. The team should agree on who will present the objectives, how they will explain the business

value and technical feasibility, and how they will handle any objections or concerns. The team should

also rehearse their presentation and anticipate potential questions and scenarios. By aligning on how

to answer questions, the team can increase their confidence and clarity, and demonstrate their

commitment and alignment to the vision and goals of the ART.

Reference:

PI Planning - Scaled Agile Framework

Presenting PI Planning Draft and Final Plan Reviews Virtually

SAFe Scrum Master/Team Coach - Scaled Agile Framework

One of the main responsibilities of a Scrum Master/Team Coach is to facilitate team events, such as Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective. These events help the team to plan, execute, inspect, and adapt their work throughout the Iteration. By facilitating these events, the Scrum Master/Team Coach ensures that the team follows the Agile principles and practices, collaborates effectively, and delivers value to the customers and stakeholders. (Must be taken from SAFe 6 Scrum Master resources) Reference: SAFe Scrum Master Course Outline Iteration Execution Iterations

The primary goal of a team in an Iteration is to deliver working functionality that meets the

acceptance criteria and the definition of done. This functionality is demonstrated to the stakeholders

and customers in the Iteration Review and Demo event, where the team receives feedback and

validation. By delivering working functionality at the end of the Iteration, the team contributes to the

Incremental value delivery, one of the SAFe Lean-Agile Principles. (Must be taken from SAFe 6 Scrum

Master resources)

Reference:

Iteration Goals

Iteration Planning

Iteration Review and Demo