SAFe-SASM Exam Questions & Answers

Completed by a Single Agile Release Train within one PI:

Definition: A Feature in SAFe is a service or functionality that meets the needs of a customer and can be delivered within a single Program Increment (PI) by an ART.

Prioritized using Weighted Shortest Job First (WSJF):

Definition: WSJF is a prioritization method used in SAFe to sequence work for maximum economic benefit.

SAFe Scrum Master Reference:

SAFe framework details the concept of Features, emphasizing their completion within a PI and their prioritization using WSJF to maximize value delivery.

To transform unpredictable events into predictable events (A): Cadence creates a regular, reliable schedule for events, which helps in managing and mitigating variability. This predictability allows teams to plan and execute their work more effectively, reducing the uncertainty of unforeseen events.

To synchronize planning for multiple teams and ARTs (C): Cadence helps align the planning cycles of multiple teams and Agile Release Trains (ARTs), ensuring that everyone works in a coordinated manner. This synchronization is critical for integrated, cross-team activities and for maintaining a cohesive workflow across the organization.

SAFe Scrum Master Reference

SAFe Principles: the importance of cadence and synchronization

SAFe 5.0 framework: benefits of applying cadence in Agile teams

Promoting T-shaped skill development means encouraging team members to develop a broad set of skills in addition to their specialization. This enhances team flexibility and resilience.

Pairing on Stories (A): By having team members pair up on stories, knowledge is shared, and members can learn from each other's expertise. This practice helps in building secondary skills and fosters a collaborative learning environment.

Cross-Functional Stories (E): Defining stories that require cross-functional skills ensures that team members have to work together, leveraging and developing a broader range of skills. This practice helps in cross-training and builds a more versatile team.

These methods help in breaking down silos within the team and promote a culture of continuous learning and skill development.

SAFe Scrum Master Reference:

SAFe Advanced Scrum Master Training Material, Chapter on Team Dynamics and Collaboration.

In SAFe (Scaled Agile Framework), lead time is an essential metric used to measure the efficiency and effectiveness of a process. Lead time is defined as the total time it takes for a work item to move through the entire process from the moment it is initiated until it is completed. To measure lead time accurately using a Team Kanban board, two specific timestamps are crucial:

When the Agile Team pulls a Story onto the board (Timestamp C):

This is the starting point of the lead time. It marks the moment when the team commits to working on a particular story by pulling it into the workflow. This action indicates that the story is now in progress and the clock starts ticking from this point.

When the Story is accepted by the Product Owner (Timestamp D):

This is the endpoint of the lead time. It signifies that the story has been completed to the satisfaction of the team and has met the acceptance criteria defined by the Product Owner. When the Product Owner accepts the story, it indicates that the work is done and the lead time measurement stops.

These two timestamps effectively capture the duration a story takes to go through the development process, providing valuable insights into process efficiency and identifying areas for improvement.

SAFe Scrum Master Reference

SAFe Advanced Scrum Master learning materials

SAFe 5.0 Scrum Master Certification resources

The 2020 Scrum Guide: Scrum Guide 2020

This information aligns with the principles and practices outlined in the SAFe framework and the Scrum Guide, ensuring a comprehensive understanding of lead time measurement within a Team Kanban board context.

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.