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

According to the SAFe 6 Scrum Master documentation, the type of work that should fit into one Iteration for one team is a Story. A Story is a short description of a small piece of functionality that provides value to the customer or stakeholder. Stories are derived from Features, which are larger units of value that typically span multiple Iterations. Stories are also decomposed into Tasks, which are the specific activities that the team members perform to implement the Story. Stories are the primary backlog items that the team plans, estimates, and delivers in an Iteration. They are also the basis for defining and committing to the Iteration goals. Stories should be small enough to be completed within one Iteration, and they should meet the definition of ready and the definition of done. (Must be taken from SAFe 6 Scrum Master resources)

References:

• Stories
• Features
• Tasks
• Iteration Planning

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 anduncertainty, and make informed and timely decisions that support the delivery of value to the customers. (Must be taken from SAFe 6 Scrum Master resources)

References:

• PI Planning - Scaled Agile Framework
• Planning Interval (PI) - Scaled Agile Framework
• Preparing for PI Planning | Checklist for Scrum Masters and Product …
• Scrum Master - Scaled Agile Framework
• Scrum Master role in PI Planning - ValueGlide

One Agile development value is customer collaboration over contract negotiation. This value is one of the four core values of the Agile Manifesto, which states: “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” 1 This value emphasizes the importance of building a trusting and collaborative relationship with the customers, rather than relying on rigid and formal contracts that may limit the ability to respond to changing needs and expectations2 Customer collaboration means involving the customers throughout the development process, seeking their feedback, input, and validation, and delivering solutions that meet their requirements and expectations3 Customer collaboration also means respecting the customers’ opinions and perspectives, and resolving any conflicts or issues in a constructive and respectful manner4 Customer collaboration helps the Agile teams to deliver value faster and more effectively, as well as to increase customer satisfaction and loyalty34 (Must be taken from SAFe 6 Scrum Master resources)

References:

• Manifesto for Agile Software Development
• Customer Collaboration Over Contract Negotiation - Mountain Goat Software
• Customer Collaboration Over Contract Negotiation - Agile Alliance
• Customer Collaboration Over Contract Negotiation - Scrum Inc