Scaled Agile SAFe Advanced Scrum Master SAFe-SASM SASM Exam Questions

Answer : A

One way a Scrum Master leads the team's efforts for relentless improvement is by helping teams become better problem solvers. This involves coaching and mentoring the team in effective problem-solving techniques, facilitating problem-solving workshops, and encouraging a mindset of continuous improvement. By empowering teams to identify and address issues autonomously, the Scrum Master supports the development of a high-performing, self-sufficient team.

SAFe Scrum Master Reference

SAFe 5.0 framework: role of the Scrum Master in promoting continuous improvement

SAFe Advanced Scrum Master learning materials: techniques for improving problem-solving skills within teams

Answer : D

The Scrum Master should coach Lee to discuss his progress in the context of the Iteration goals. By framing his updates around how his work contributes to the broader objectives of the iteration, Lee can provide the team with better visibility into his progress and the impact of his work. This approach encourages team members to think beyond individual tasks and understand how their efforts align with the team's goals, fostering greater collaboration and accountability.

SAFe Scrum Master Reference

SAFe Principles: focusing on outcomes and aligning individual efforts with team goals

SAFe 5.0 framework: effective daily stand-up practices

Answer : B

Relentless Improvement: This principle is a cornerstone of Agile and SAFe. It encourages teams to continuously seek ways to improve their processes, quality, and performance.

Scrum Master Role: The Scrum Master supports the team by fostering a culture of continuous improvement. This involves facilitating retrospectives, encouraging experimentation, and helping the team reflect on their practices and outcomes.

Taking Responsibility: By promoting relentless improvement, the Scrum Master helps the team take ownership of their actions and outcomes, driving self-management and accountability.

SAFe Scrum Master Reference:

SAFe emphasizes the role of the Scrum Master in supporting continuous improvement initiatives and helping teams develop a mindset of ongoing learning and development.

Answer : B, C

Two specific anti-patterns likely present within the team's retrospectives are:

The team identifies improvements but is not allowed to address them (B): This anti-pattern occurs when the team discusses potential improvements but lacks the authority or support to implement them. This leads to frustration and a sense of futility, as the team feels their efforts in retrospectives do not result in meaningful change.

The team does not identify and commit to improvement items for how they do their work (C): Effective retrospectives should result in actionable items that the team commits to addressing in the next iteration. If the team fails to identify and commit to these improvements, the retrospective becomes an empty ritual without real impact on the team's performance or processes.

SAFe Scrum Master Reference

SAFe Principles: continuous improvement and the importance of retrospectives

SAFe 5.0 framework: best practices for effective retrospectives

Answer : A, E

Iteration Planning:

Purpose: Iteration Planning is a crucial event where the team collaborates to determine what will be delivered in the upcoming iteration and how the work will be accomplished. The entire team, including the Scrum Master, Product Owner, and Developers, come together to plan the iteration's work.

Process:

The Product Owner presents the prioritized backlog items to the team.

The team discusses each item, clarifies any ambiguities, and breaks down the items into tasks.

The team estimates the effort required for each task and commits to what they believe can be achieved in the iteration.

Outcome: A detailed iteration plan that includes the selected backlog items and a clear understanding of the tasks and responsibilities for each team member.

Backlog Refinement:

Purpose: Backlog Refinement (also known as Grooming) is an ongoing process where the team and the Product Owner collaborate to review and update the backlog. This ensures that the backlog is in good shape for future iteration planning.

Process:

The team reviews the items in the backlog to ensure they are well understood and ready for future iterations.

The Product Owner provides context and clarifications for each backlog item.

The team discusses the requirements, refines the acceptance criteria, and estimates the effort required for each item.

The backlog items are prioritized based on their value and urgency.

Outcome: A well-maintained and prioritized backlog that facilitates effective and efficient iteration planning.

SAFe Scrum Master Reference:

Iteration Planning:

SAFe Advanced Scrum Master training materials emphasize the importance of Iteration Planning as a key event for team collaboration, ensuring everyone is aligned on the iteration goals and tasks.

2020 Scrum Guide: The Iteration Planning section outlines the collaborative nature of this event and its role in setting the stage for successful iterations.

Backlog Refinement:

In the SAFe framework, Backlog Refinement is highlighted as an essential activity to maintain a healthy backlog, allowing the team to prepare for future iterations effectively.

Scrum Open: This document discusses the significance of Backlog Refinement in fostering team collaboration and ensuring the backlog is well-groomed and ready for planning.

Answer : A

The program predictability measure is the primary metric used during the quantitative measurement part of the Inspect and Adapt (I&A) event in SAFe. This measure assesses how reliably the Agile Release Train (ART) can deliver business value within the Program Increment (PI) timebox. It helps to:

Evaluate the team's ability to meet their commitments.

Identify areas where predictability can be improved.

Ensure that the business value planned for the PI is actually delivered.

By focusing on the predictability of business value, organizations can better align their planning and execution efforts, ultimately enhancing customer satisfaction and achieving strategic goals more effectively.

SAFe Scrum Master Reference

SAFe Inspect and Adapt events

SAFe 5.0 framework: using program predictability as a key metric to assess and improve ART performance.

Answer : C

If a team consistently receives defect reports from production despite thorough testing of each story, the first step to address this issue is to ensure that development and testing environments are equivalent to production. Differences between environments can lead to undetected issues that only surface in the production environment. By aligning these environments, teams can ensure that tests accurately reflect real-world conditions, reducing the likelihood of defects slipping through.

SAFe Scrum Master Reference

SAFe Principles: ensuring quality by maintaining equivalent environments

SAFe 5.0 framework: best practices for aligning development, testing, and production environments