SSM Exam Dumps : SSM (6.0) - SAFe Scrum Master Practice 6.0

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.

In the Scaled Agile Framework (SAFe®), a key element of building a high-performing Agile Team is fostering T-shaped skills among team members. T-shaped skills refer to individuals who have deep expertise in one area (the vertical bar of the "T") but also possess the ability and willingness to collaborate across disciplines (the horizontal bar of the "T").

Encouraging team members to acquire T-shaped skills increases flexibility, improves collaboration, and reduces bottlenecks since work is not blocked by specialization. It also strengthens the team’s ability to self-organize and deliver value collectively, rather than relying on handoffs.

From SAFe guidance:

“High-performing Agile Teams are built on cross-functional, self-managing individuals who have or develop T-shaped skills, enabling them to collaborate effectively and support each other’s work.”

Therefore, the correct answer is A. Encourage team members to acquire T-shaped skills, as it directly contributes to stronger, more adaptive, and collaborative teams.

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 Planning1 However, 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 events2 By 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