Scaled Agile SSM (6.0) - SAFe Scrum Master Exam Practice Test

Answer : C

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

Answer : A

One example of Scrum Masters/Team Coaches helping without diminishing the commitment of others is facilitating necessary meetings for the team.Facilitating means providing guidance and support to the team in conducting effective and productive meetings, such as Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective1Facilitating does not mean taking over the meeting or making decisions for the team.Rather, it means creating a safe and respectful environment, ensuring clear and shared objectives, encouraging participation and collaboration, managing time and agenda, resolving conflicts and issues, and summarizing outcomes and action items23By facilitating necessary meetings for the team, Scrum Masters/Team Coaches help the team to achieve their goals, improve their processes, and deliver value to the customers and the organization14At the same time, they respect and empower the team's autonomy, self-organization, and self-management, and do not interfere with their commitment or accountability14(Must be taken from SAFe 6 Scrum Master resources)

Scrum Master/Team Coach - Scaled Agile Framework

Facilitation - Scaled Agile Framework

How to Facilitate Effective Meetings as a Scrum Master | Agile Velocity

The Scrum Master Balancing Act | Scrum.org

Answer : B

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.''1This 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 expectations2Customer collaboration means involving the customers throughout the development process, seeking their feedback, input, and validation, and delivering solutions that meet their requirements and expectations3Customer collaboration also means respecting the customers' opinions and perspectives, and resolving any conflicts or issues in a constructive and respectful manner4Customer 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)

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

Answer : A

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 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 Iteration2By 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

Team Backlog - Scaled Agile Framework

Backlog Refinement - Scaled Agile Framework

What is backlog refinement? | Miro

Answer : D

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 product1They are empowered, collaborative, aligned, and committed to delivering value to the customers and the organization1One 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 stakeholders23Feedback loops help the team to validate their assumptions, measure their progress, and adjust their plans accordingly23Feedback loops also help the team to foster a culture of experimentation, innovation, and continuous improvement, as well as to increase customer satisfaction and loyalty23Team 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)

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

Answer : C

One anti-pattern that emerges when teams do not spend enough time refining the backlog is that they enter new Iterations without enough Stories prepared.This can result in several negative consequences, such as:123

The team may struggle to plan and commit to the Iteration Goals, as they lack clarity, feasibility, and testability of the Stories.

The team may face delays, rework, and waste, as they encounter unanticipated dependencies, risks, or technical issues during the Iteration.

The team may deliver low-quality or incomplete Stories, as they rush to meet the Iteration deadlines or compromise on the Definition of Done.

The team may lose focus, alignment, and motivation, as they work on ambiguous or unrealistic Stories that do not deliver value to the customers or the organization.

To avoid this anti-pattern, the team should dedicate sufficient time and effort to refine the backlog on a regular basis, preferably every Iteration123Backlog 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 Backlog4One 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 Iteration2By doing so, the team can improve the quality, efficiency, and effectiveness of their work, as well as deliver value to the customers and the organization

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