Get Scaled Agile SSM Exam Dumps

Answer : A

Backlog Refinement is the Agile Team event where team members estimate relative story sizes.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 Backlog1One 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 iteration2To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35(Must be taken from SAFe 6 Scrum Master resources)

Team Backlog - Scaled Agile Framework

Backlog Refinement - Scaled Agile Framework

Story - Scaled Agile Framework

How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog

Why Your Agile Team Should Use Relative Story Point Estimation

Answer : B

Norming is the stage of team development where team members stop focusing on their own goals and begin focusing on developing better ways of working together.Norming occurs after the team has gone through the Forming and Storming stages, where they have established their roles and responsibilities, and have resolved their initial conflicts and disagreements12In the Norming stage, the team starts to build trust, respect, and cohesion among themselves.They also align on a common vision, mission, and goals, and agree on the norms and expectations for their collaboration and communication12The team becomes more productive, efficient, and effective, as they leverage their collective strengths and skills, and support each other in overcoming challenges and delivering value12The team also develops a sense of identity and pride, and celebrates their achievements and learnings12(Must be taken from SAFe 6 Scrum Master resources)

Agile Teams - Scaled Agile Framework

5 Stages of Team Development | Agile Scrum Guide | Book | Blog

Answer : C

A safe environment for taking risks without fear of embarrassment or criticism is one of the characteristics of a high-performing Agile Team.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 product1They are empowered, collaborative, aligned, and committed to delivering value to the customers and the organization2One of the factors that enable a high-performing Agile Team is a safe environment where team members can experiment, learn, and grow without fear of failure, blame, or judgment3A safe environment fosters a culture of innovation, creativity, and continuous improvement, as well as a sense of psychological safety, trust, and belonging among team members4Team C is demonstrating this characteristic by creating a new workflow to speed up the testing process, even though it did not work out as expected. The rest of the team was excited to hear what was learned from the failed experiment, rather than being disappointed or critical. This shows that the team values learning over perfection, and supports each other in taking risks and trying new things. (Must be taken from SAFe 6 Scrum Master resources)

Agile Teams - Scaled Agile Framework

High-Performing Teams - Scaled Agile Framework

How to Create a Safe Environment for Agile Teams | AgileConnection

Psychological Safety - Scaled Agile Framework

Answer : A

One benefit of having an IP Iteration every PI is that it creates an estimating buffer for meeting PI objectives. PI objectives are a set of SMART goals that align the teams and stakeholders to a common vision and mission for the upcoming Program Increment (PI).They are derived from the business context, priorities, and dependencies, and are agreed upon and committed by the teams during PI Planning1However, since PI objectives are based on estimates and assumptions, there is always a degree of uncertainty and variability in the delivery process. To account for this, SAFe recommends that teams reserve 10% of their capacity for each PI as an estimating buffer.This buffer is used during the IP Iteration, which is a unique, dedicated iteration that occurs every PI and provides dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events2By having an IP Iteration as an estimating buffer, the teams can improve the predictability and flow of value delivery, as well as reduce the stress and pressure of meeting the PI objectives23(Must be taken from SAFe 6 Scrum Master resources)

PI Objectives - Scaled Agile Framework

Innovation and Planning Iteration - Scaled Agile Framework

SAFe Scrum Master Course Outline

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

CALMR - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline