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

Answer : D

The Portfolio Backlog in SAFe contains the larger initiatives, known as Epics. Epics are substantial pieces of work that require analysis, investment, and development effort over multiple Program Increments (PIs). They represent significant business or technical needs that drive the long-term strategy of the organization. These Epics are prioritized and managed in the Portfolio Backlog, where they can be decomposed into smaller, actionable items as they progress through the development process.

Answer : D

In SAFe, systems builders and customers bear a significant responsibility to ensure that investments in new solutions deliver the necessary economic benefit. This means that any investment should provide value that justifies the costs and efforts involved. The focus on economic benefit helps ensure that resources are used effectively and that the solutions developed contribute positively to the organization's financial health.

SAFe Scrum Master Reference

SAFe Lean-Agile Principles: economic view and value delivery

SAFe 5.0 framework: ensuring investments align with economic benefits

Answer : B, C

Identify Impediments:

Purpose: The Scrum of Scrums meeting helps identify and address impediments that affect multiple teams. This ensures that these blockers are resolved quickly, allowing teams to continue their work without disruptions.

Process: Representatives from different teams come together to discuss challenges, share updates, and seek assistance in removing impediments.

Facilitate Cross-Team Collaboration:

Purpose: The meeting fosters collaboration among teams working on the same product or solution, ensuring that their efforts are aligned and integrated.

Process: Teams share their progress, dependencies, and upcoming work, enabling better coordination and synchronization across the Agile Release Train (ART).

SAFe Scrum Master Reference:

SAFe highlights the importance of the Scrum of Scrums meeting for coordinating efforts and solving cross-team issues, ensuring that the ART functions smoothly and efficiently.

Answer : D

One of the primary outputs from the problem-solving workshop in SAFe is identifying the top improvement items for the next Program Increment (PI). These workshops focus on analyzing issues, determining root causes, and formulating actionable improvements. By prioritizing and committing to these improvement items, teams can systematically address problems and enhance their performance and productivity in subsequent PIs.

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

Waterfalling the Iteration: The term 'waterfalling' in an Agile context refers to the anti-pattern where teams delay integration, testing, and other critical activities until the end of the iteration, mimicking the Waterfall model of sequential phases.

Agile Practice: In Agile, the goal is to continuously integrate and test stories throughout the iteration. This practice ensures that issues are identified and addressed early, and the product increment is always in a potentially shippable state.

Anti-pattern Explanation: Integrating and testing stories only on the last day of the iteration means the team is not practicing continuous integration. This can lead to hidden defects, reduced quality, and last-minute rushes that jeopardize the team's ability to meet commitments effectively.

SAFe Scrum Master Reference:

SAFe emphasizes continuous integration and regular testing as key practices to maintain quality and agility. Delaying these activities to the end of the iteration undermines these principles and can lead to significant issues.

Answer : A

Problem Statement: The ART has nothing to show at the System Demo, indicating potential issues with integration, quality, or coordination among teams.

Recommended Action: Stopping new development work to focus on integrating and testing the system allows the team to identify and resolve integration issues, ensuring that the system is in a stable state.

Scope Adjustment: Based on what is learned during integration and testing, the scope can be adjusted to focus on delivering a coherent and functional system increment.

SAFe Scrum Master Reference:

SAFe emphasizes the importance of a stable, integrated system increment to demonstrate progress and ensure quality. Addressing integration issues promptly is crucial for maintaining stakeholder confidence and delivering value.