Free Practice Questions for Scaled Agile SAFe-Agilist Exam

The SAFe Lean-Agile Principle that includes the critical part of “delaying decisions to the last responsible moment” is “Assume variability; preserve options”. This principle is based on the concept of set-based design, which is a way of managing uncertainty and complexity in product development. Set-based design means exploring multiple possible solutions in parallel, eliminating inferior options over time, and converging on the best solution as more information becomes available. Delaying decisions to the last responsible moment means keeping multiple options open until enough data and feedback are gathered to make an informed decision, which reduces risk and waste. References: SAFe Lean-Agile Principles, SAFe Principle #4

From the Workbook’s Portfolio Kanban section:

“Once an Epic is approved with a Lean business case, it moves to the ‘Ready’ state in the Portfolio Kanban system, provided it receives a 'go' decision from Lean Portfolio Management (LPM).”

This marks the transition from analysis to readiness for implementation.

Source:01 Workbook SA (6.0).pdf, Page 5-32

This is how SAFe describes Customer Centricity. Customer Centricity is one of the core competencies of business agility in SAFe. Customer Centricity means putting the customer at the center of everything the enterprise does, and understanding their needs, desires, and problems deeply. Customer Centricity also means adopting a mindset that focuses on observing and learning from customer behaviors that produce the best innovations, rather than relying on assumptions or opinions. Customer Centricity helps enterprises deliver solutions that delight their customers and achieve market differentiation. References: Customer Centricity

An enabling team is a type of cross-functional Agile team that is organized to assist other teams with specialized capabilities and help them become more proficient in new technologies. Enabling teams provide coaching, mentoring, training, and technical guidance to other teams in areas such as DevOps, test automation, security, compliance, etc. Enabling teams help other teams achieve the core competency of Technical Agility in SAFe. References: Cross-functional Agile Teams, Technical Agility

According to the SAFe Glossary and reiterated in the Workbook:

“The Release Train Engineer (RTE) is a servant leader and ART coach who facilitates ART events and processes and supports teams in delivering value.”

Source:SAFe Glossary & Workbook Page 3-19

According to the SAFe Workbook:

“The Continuous Delivery Pipeline represents the workflows, activities, and automation needed to deliver new functionality more frequently… It enables continuous exploration, integration, deployment, and release on demand—fosteringongoing learning.”

Source:01 Workbook SA (6.0).pdf, Pages 4-81 to 4-84

The SAFe Implementation Roadmap provides an ordered sequence of transformation activities. After training leaders, the next step is:

“Identify Value Streams and ARTs – this step is essential to organizing around value, ensuring future trains are aligned with value delivery.”

Launching more ARTs and Value Streams is the implementation step that follows Coach ART Execution on the SAFe Implementation Roadmap. The SAFe Implementation Roadmap is a guide that helps enterprises implement SAFe in a structured and reliable way. The roadmap consists of 12 critical moves that span from reaching the tipping point to extending to the portfolio and beyond. Coach ART Execution is the seventh move, where the first ART is launched and coached by a SAFe Program Consultant (SPC) or other expert. Launch more ARTs and Value Streams is the eighth move, where the enterprise expands the implementation of SAFe to other value streams and ARTs, based on the learnings and successes of the firstART. References: SAFe Implementation Roadmap, Coach ART Execution, Launch more ARTs and Value Streams

According to the SAFe Agilist 6.0 domain of Lean Thinking, a value stream is triggered by a demand for some value, such as a new feature, a change request, or a defect fix1. A feature is a service that fulfills a stakeholder need2. Therefore, a feature request is a valid trigger for a value stream.

A spike request is a type of exploration enabler that addresses technical uncertainty or risk3. A user story request is a type of backlog item that represents an end user goal or function4. These are not triggers for a value stream, but rather work items that flow through a value stream.