SAFe-Agilist-6-0 SAFe 6.0 Agilist Practice Questions

The root cause of HealthFirst's problems is a lack of focus on quality during the development process. The concept of Built-in Quality addresses this directly by advocating for practices that ensure quality is part of every step, not an afterthought. Establishing a common Definition of Done would create a shared understanding of quality standards. Emphasizing continuous integration would ensure that integration issues are found early and often, rather than late in the PI. This addresses the systemic issues described, whereas just adding more testers would be a less effective, reactive measure.

The Inspect and Adapt (I&A) event is structured to provide a comprehensive review of the Program Increment. It begins with (1) the PI System Demo, where the full integrated solution is demonstrated to stakeholders. This is followed by (2) Quantitative Measurement, where the ART reviews metrics like the program predictability measure. Finally, it concludes with (3) the Problem-Solving Workshop, a retrospective to identify and address the systemic problems the ART faced during the PI.

In the SAFe House of Lean, Lean-Agile Leadership forms the foundation. This is because leaders are responsible for creating the environment and providing the resources necessary for the pillars (Respect for People and Culture, Flow, Innovation, Relentless Improvement) to stand strong and support the goal of delivering value. Without a strong leadership foundation, the entire system is unstable.

The Program Board is a key output of PI Planning. It is a large visual radiator that shows the features to be delivered, the iterations they are planned for, and most importantly, the dependencies between teams. Lines (strings) are drawn between team boards to represent these dependencies, making them visible to the entire ART and helping to ensure they are managed throughout the PI.

Systems thinking emphasizes that a system's performance is a result of the interactions between its components, not just the performance of the components themselves. A common problem in large organizations is local optimization, where each department tries to be as efficient as possible, which often creates bottlenecks and delays for the overall value stream. Systems thinking encourages looking at and optimizing the entire end-to-end flow of value.

Design Thinking is a customer-centric development process that helps create products that customers love. It uses techniques like personas, empathy maps, and journey maps to understand the problem space and then ideates on potential solutions. This process is ideal for breaking down a high-level vision into tangible features that address specific user needs, making it the correct tool to bridge the gap described in the scenario.

Flow Time measures the total time from when work starts until it is delivered. Flow Load measures the number of items currently in the system (WIP). A high Flow Time combined with a low Flow Load (not many items in progress) indicates that the few items in the system are taking a very long time to get through. This is a classic sign of significant delays, wait states, or bottlenecks in the process, rather than the system being overloaded with too much work.

SAFe Principle #1, Take an economic view, is operationalized through the use of Weighted Shortest Job First (WSJF) for prioritization. WSJF provides a formula (Cost of Delay / Job Duration) to make economic decisions. Simply looking at Cost of Delay or job size in isolation is insufficient. Calculating WSJF for both initiatives provides a quantitative basis for sequencing work to maximize economic benefit.

The principle 'Organize around value' advocates for creating cross-functional teams and ARTs that can deliver end-to-end customer value with minimal dependencies. Structuring teams around value streams (like the checkout process) ensures that each team can independently deliver features that customers care about. This contrasts with component teams (UI, API), which create dependencies and hinder the flow of value.