Most Recent Scaled Agile SSM Exam Dumps

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

One method a Scrum Master/Team Coach can use to help teams overcome a fear of conflict is to give every team member the opportunity to contribute.Fear of conflict is one of the common dysfunctions of a team, which can result in artificial harmony, lack of trust, and avoidance of issues1To overcome this fear, the Scrum Master/Team Coach can facilitate a safe and respectful environment where team members can express their opinions, ideas, and concerns without being judged, ignored, or attacked23Giving every team member the opportunity to contribute can help them feel valued, respected, and heard, as well as foster a culture of collaboration, feedback, and learning45The Scrum Master/Team Coach can use various techniques to ensure equal participation, such as round-robin, fist of five, dot voting, silent brainstorming, and liberating structures45By encouraging healthy and constructive conflict, the Scrum Master/Team Coach can help the team improve their performance, creativity, and innovation23

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)

Iteration Goals

Iteration Planning

Iteration Review and Demo

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

According to the SAFe 6 Scrum Master documentation, one of the important attendees to the PI System Demo is the Business Owners. Business Owners are a small group of stakeholders who have the primary business and technical responsibility for governance, compliance, and return on investment (ROI) for a Solution developed by an Agile Release Train (ART). They are key stakeholders on the ART who must evaluate fitness for use and actively participate in certain ART events. The PI System Demo provides them an opportunity to see the integrated view of new features delivered by the ART, give feedback, and influence the future direction of the solution. (Must be taken from SAFe 6 Scrum Master resources)

System Demo

[Business Owners]