SAFe-Agilist-6-0 Sample Questions & Answers

This statement is false. 'Develop on Cadence, Release on Demand' decouples the development rhythm (cadence) from the release of value. While the ART develops and integrates on a fixed PI cadence, the business decides when to release that value based on market needs and business goals. A release can happen at any time, not just at the PI boundary.

This is the best application of LPM principles. Large Epics introduce significant risk and delay value delivery. By breaking the Epic into smaller MVPs, GLI can validate the hypothesis incrementally, manage the investment within established guardrails (e.g., limits on single investments), and deliver value sooner. This approach also facilitates better coordination with the constrained 'Data Platform' value stream, allowing for smaller, more manageable pieces of work to be scheduled.

Continuous Exploration is the 'front-end' of the delivery pipeline. Its purpose is to foster innovation and build alignment on what to build. This involves activities like hypothesizing, collaborating with stakeholders, synthesizing research, architecting solutions, and prioritizing the backlog. It ensures that the ART builds the right thing, before focusing on building it right (Continuous Integration) and building it fast (Continuous Deployment).

SAFe Principle #8 is based on Daniel Pink's work on motivation, which highlights that for knowledge workers, traditional extrinsic motivators (like bonuses) can be ineffective or even counterproductive. Instead, leaders should focus on fostering intrinsic motivation through autonomy (the desire to direct our own lives), mastery (the urge to get better at something that matters), and purpose (the yearning to do what we do in the service of something larger than ourselves). The manager's approach failed because it relied on an outdated extrinsic model.

The Business Agility Value Stream (BAVS) represents the fundamental flow of value for any business in the digital age. It starts with sensing an opportunity (market change, new technology, competitive threat) and ends with delivering an innovative business solution. The seven core competencies of business agility are the key enablers that allow an organization to execute its BAVS quickly and effectively.

The assignment of Business Value (BV) by Business Owners is a crucial communication tool. It allows them to express the relative importance of each PI Objective from a business perspective. This is not about calculating velocity or comparing teams; it's about creating alignment between the business and the development teams on priorities, guiding trade-off discussions, and providing a basis for measuring the actual business value delivered at the end of the PI.

The principle 'Decentralize decision-making' also defines which decisions should remain centralized. Decisions that are infrequent, long-lasting, and provide significant economies of scale should be centralized. The choice of an encryption standard fits all these criteria: it's not made often, it will be in place for a long time, and a single standard across the system provides massive benefits. Therefore, centralizing this strategic technical decision is the correct approach.

The 'Analyzing' state of the Portfolio Kanban is where the detailed work on a potential Epic happens. This includes creating a full business case, defining the MVP to test the Epic's hypothesis, identifying potential solutions, and performing a WSJF calculation for prioritization. This rigorous analysis ensures that only well-vetted and valuable Epics move into the Portfolio Backlog for implementation.

This statement is false. Writing user stories and managing the team backlog is the primary responsibility of the Product Owner. A SAFe Agilist is a Lean-Agile leader who helps lead the transformation and guides the organization in applying SAFe principles and practices. Their focus is on the broader system of delivery, coaching, and enabling Agile Release Trains.