Download SAFe Advanced Scrum Master-SASM.SAFe-SASM.Pass4Success.2026-03-30.28q.tqb

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.

Phase-gate milestones are traditional project management mechanisms that mark the end of one phase and the beginning of another. One major problem with phase-gate milestones is that they assume a point solution exists and can be built correctly the first time. This assumption does not account for the iterative nature of Agile methodologies, where solutions are developed incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of delivering a product that does not meet the actual needs or expectations.

The program predictability measure is the primary metric used during the quantitative measurement part of the Inspect and Adapt (I) 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 ReferenceSAFe Inspect and Adapt eventsSAFe 5.0 framework: using program predictability as a key metric to assess and improve ART performance.

Creating a buffer state between two states in a Kanban board can help regulate the flow of work and address the varying completion times.Buffer State Purpose: Acts as a holding area to balance the flow between different stages of work, smoothing out variances in completion times.Flow Regulation: Ensures that work can continue smoothly without bottlenecks or idle times.Work In Progress (WIP) Limits: Helps maintain a steady flow by preventing too much work from accumulating in any one state.This approach aligns with Lean principles of managing flow and reducing variability in processes.SAFe Scrum Master Reference:SAFe Advanced Scrum Master Training Material, Chapter on Kanban Systems.

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.

Cumulative Flow Diagram (CFD): A CFD is a visual tool used in Kanban and Scrum to show the progress of work items through different stages of the workflow over time.Arrival and Departure Curves: These curves represent the work items entering (arrival) and leaving (departure) the system.Growing Distance: If the distance between the arrival and departure curves on the CFD is growing apart, it indicates that work items are taking longer to move through the system.Lead Time: This term refers to the total time from when a work item is created until it is completed. An increasing distance between the curves means that work items are spending more time in the system, thus increasing the lead time.SAFe Scrum Master Reference:SAFe materials on flow metrics and Kanban principles highlight the importance of monitoring lead time and using CFDs to identify bottlenecks and inefficiencies in the workflow.

Decentralized decision-making is a principle in SAFe aimed at distributing decision authority to the people closest to the information and most affected by the decisions. The primary goal of decentralized decision-making is to reduce delay in the decision-making process, which can often occur when decisions need to pass through multiple layers of hierarchy. By empowering individuals and teams to make decisions quickly, organizations can respond faster to changes, improve agility, and maintain a steady flow of work.

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.

The primary measurement during the Inspect and Adapt (I) event in SAFe is the program predictability measure. This metric assesses the Agile Release Train's (ART) ability to deliver on its commitments within a Program Increment (PI). It helps teams understand how accurately they can plan and execute work, providing a basis for continuous improvement. By focusing on predictability, organizations can improve their planning processes, align better with business objectives, and ensure more reliable delivery of value.

An effective Agile Team focuses on delivering value by reliably deploying features that meet customer needs.Value Delivery: The primary measure of success for an Agile team is the continuous delivery of valuable, working software.Customer Focus: Teams work collaboratively to understand and deliver what is most valuable to customers.Incremental Progress: Regularly delivering increments of the product that are potentially shippable ensures continuous feedback and improvement.This characteristic emphasizes the Agile principle of delivering working software frequently, with a focus on customer value.SAFe Scrum Master Reference:SAFe Advanced Scrum Master Training Material, Chapter on Agile Teams.