Free Scaled Agile SAFe-Agilist Practice Exam with Questions & Answers

From the workbook section on forming cross-functional Agile Teams:

“Agile Teams are cross-functional self-organizing entities that can define, build, test, and—where applicable—deploy increments of value.”

“Optimized for communication and delivery of value” is also mentioned but for this question, the best indicators of a cross-functional team are thecapabilities of the team membersand their ability to deliver value independently.

Strategic Themes are highlighted in the workbook as:

“Differentiating business objectives that… Connect the portfolio to the Enterprise strategy.”

They provide context for budgeting and vision alignment across the organization.

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

The Lean-Agile Center of Excellence (LACE) plays a key role in enabling transformation and follows the SAFe Implementation Roadmap.

“LACE uses the SAFe Implementation Roadmap to guide the transformation… The roadmap outlines a step-by-step strategy from reaching the tipping point to sustaining and accelerating SAFe.”

In the workbook’s PI Planning agenda:

"After the draft plan review, the RTE facilitates amanagement review and problem-solving meetingwith Business Owners, Product Management, and other stakeholders. Here, capacity and load adjustments, scope changes, and planning adjustments are agreed upon."

Source:Workbook, PI Planning Module, Page 4-70

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

SAFe emphasizes that effective DevOps implementation is key to enabling continuous value delivery. The workbook highlights that:

“DevOps helps ensure a constant flow of value by automating the Continuous Delivery Pipeline and enabling continuous integration and deployment… A Value Stream with DevOps capabilities implements automation and integration for consistent quality and faster delivery.”

This makes automation a cornerstone in enabling flow within a Value Stream.

ROAM is an acronym for Resolved, Owned, Accepted, Mitigated. ROAM is a technique for categorizing and managing PI risks during the final plan review in the PI planning event. PI risks are potential events or conditions that may have a negative impact on the PI objectives or outcomes. ROAM helps teams address their PI risks by assigning them to one of four states: Resolved (the risk has been eliminated or is no longer relevant); Owned (the risk has been assigned to a person or a team who is responsible for managing it); Accepted (the risk has been acknowledged and its impact has been factored into the plan); Mitigated (the risk has been reduced or its likelihood has been lowered). References: PI Planning, Final Plan Review

This is one way to describe a cross-functional Agile team. A cross-functional Agile team is a group of 5-11 individuals who have the skills and authority to define, build, test, and deploy some element of solution value—all within a short iteration timebox. A cross-functional Agile team is optimized for communication and delivery of value by having clear roles and responsibilities, shared goals and commitments, frequent feedback and collaboration, high trust and accountability, and continuous improvement. References: Cross-functional Agile Teams

The workbook clearly outlines:

"Business Owners assign business value (BV) scores to PI Objectives from 1 (low) to 10 (high) after negotiation. These scores help teams understand what is most important to the business."

Source:SAFe Workbook, PI Planning Simulation Section

Features are found on an ART planning board. An ART planning board is a tool that helps teams visualize and manage the work items for an Agile Release Train (ART). An ART is a long-lived team of Agile teams that delivers value in a regular cadence. Features are high-level descriptions of system behaviors that provide business value to a stakeholder. Features are derived from epics and decomposed into user stories or enablers. Features are prioritized by business value using Weighted Shortest Job First (WSJF) and planned for Program Increments (PIs) by the ART teams. References: Organizing Around Value with ARTs, ART Planning Board