SAFe-Agilist Practice Exam Questions with Answers SAFe 6 Agilist - Leading SAFe (SA) (6.0) Certification

The workbook explains that ROAM stands for:

“Resolved – Addressed; no longer a concern

Owned – Someone has taken responsibility

Accepted – Nothing more can be done and if risk occurs, release may be compromised

Mitigated – Team has plan to adjust as necessary.”

Source: Workbook, Page 4-60

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

According to the SAFe Agilist 6.0 domain of Apply SAFe Principles, when basing decisions on economics, lead time, product cost, value, and development expense are used to:

Evaluate the economic impact of different design alternatives

Optimize the flow of value delivery by minimizing delays and waste

Maximize the return on investment by delivering the most valuable features first

Balance the tradeoffs between speed, quality, and cost

https://scaledagileframework.com/take-an-economic-view/

The Lean Budget Guardrails defined in SAFe include "Guiding investments by horizon" as one of the main components. This ensures strategic alignment and responsible use of funds.

“Fund Value Streams; Lean budgets and Guardrails… Value Stream budgets adjusted dynamically…”

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 first ART. References: SAFe Implementation Roadmap, Coach ART Execution, Launch more ARTs and Value Streams

This statement is one of the values from the Agile Manifesto. The Agile Manifesto is a declaration of four values and twelve principles that guide Agile software development. The four values are: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan. Customer collaboration over contract negotiation means that Agile teams value building strong relationships with their customers based on trust, feedback, and shared understanding, rather than relying on rigid contracts that limit flexibility and creativity. References: Thriving in the Digital Age, Agile Manifesto

SAFe Principle #10 emphasizes:

“Organize around value” and states that enterprises must continuously adjust their organizational structure to optimize for the flow of value when market demands change.

This means reorganizing the network around the new value flow is the recommended approach.

Comprehensive and Detailed Explanation From Exact Extract:

The System Team is a specialized Agile team that:

Builds and maintains development environments

Provides infrastructure and tooling support

Supports continuous integration (CI), test automation, and system-level testing

Helps ARTs integrate and validate their work

This makes the System Team the correct answer.

(Source: Scaled Agile Framework – System Team)

Customer Centricity is described as:

“A mindset and way of doing business that focuses on creating positive experiences for the customer by understanding their needs, behaviors, and preferences.”

This drives innovation and aligns solutions to real customer problems.

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

Empathy maps are a tool associated with design thinking that help to understand the user’s needs, goals, pain points, and emotions. Empathy maps are visual representations of what the user thinks, feels, sees, hears, says, and does in relation to a problem or a solution. Empathy maps help to create a shared understanding of the user among the team and stakeholders, and to generate insights for designing user-centric solutions. Empathy maps can be created based on user research, interviews, observations, or personas123.

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—fostering ongoing learning.”

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

Trust is developed by:

“Delivering value consistently and predictably… Predictability builds confidence between teams and stakeholders.”

This is reinforced during PI Planning and Iteration Reviews.

Decisions that deliver large and broad economic benefits are the type of decisions that should remain centralized even in a decentralized decision-making environment. Decentralized decision-making is a principle and practice that empowers individuals and teams to make decisions about their work without excessive interference or control from others. Decentralized decision-making fosters autonomy, agility, innovation, and ownership among knowledge workers. However, some decisions are better made centrally by those who have more authority, information, or expertise. These include decisions that affect the whole enterprise or portfolio, such as strategy, vision, budgeting, governance, compliance, etc. References: SAFe Lean-Agile Principles, SAFe Principle #9

Transparency is one of the SAFe core values. SAFe core values are the fundamental beliefs that guide the behaviors and actions of SAFe enterprises. Transparency means that all the relevant information about the strategy, plans, progress, risks, and issues are openly shared and visible to everyone who needs it. Transparency helps build trust, alignment, collaboration, and learning among all the stakeholders in a SAFe enterprise. References: SAFe Core Values, Transparency

The workbook lists multiple benefits of SAFe and Agile adoption including:

“Faster time-to-market” and “Ability to respond to changing priorities” are consistently shown as primary motivators in SAFe case studies and business agility metrics.

A SAFe portfolio is a collection of development value streams. A development value stream is a long-lived series of steps that an enterprise uses to continuously deliver value to a customer or stakeholder. A development value stream typically consists of one or more ARTs and Solution Trains that build and deliver solutions. A SAFe portfolio aligns and governs one or more development value streams that share a common business mission, vision, strategy, and funding. A SAFe portfolio helps enterprises achieve Lean Portfolio Management, which is one of the core competencies of business agility in SAFe. References: SAFe Portfolio, Development Value Streams

SWOT and TOWS are used to brainstorm potential portfolio future states. SWOT is an acronym for Strengths, Weaknesses, Opportunities, and Threats. SWOT analysis is a tool that helps identify the internal and external factors that affect the portfolio’s performance and position in the market. TOWS is an acronym for Threats, Opportunities, Weaknesses, and Strengths. TOWS analysis is a tool that helps generate strategic alternatives based on the SWOT factors. SWOT and TOWS help create a portfolio vision that reflects the desired future state of the portfolio. References: SAFe Portfolio, Portfolio Canvas

Strategic themes are an example of differentiating business objectives. Strategic themes are specific, itemized business objectives that connect a portfolio to the enterprise strategy. Strategic themes provide guidance and direction for portfolio vision, budget allocation, value stream identification, epic prioritization, and metric definition. Strategic themes help differentiate a portfolio from its competitors and create a unique value proposition for its customers. References: SAFe Portfolio, Strategic Themes

Planning adjustments are agreed upon during the management review and problem-solving meeting in the PI planning event. The management review and problem-solving meeting is a session that occurs at the end of day one of the PI planning event. In this session, the management team reviews the draft plans of all the teams in the ART, identifies any issues or risks that need to be resolved, and proposes any changes or adjustments that are necessary to achieve the program objectives. The management team then communicates their feedback and recommendations to the teams on day two of the PI planning event. References: PI Planning, Management Review and Problem-Solving

The Continuous Delivery Pipeline represents the workflow, activities, and automation needed to deliver new functionality more frequently. The Continuous Delivery Pipeline is a key enabler of Agile Product Delivery, which is one of the core competencies of business agility in SAFe. The Continuous Delivery Pipeline consists of four elements: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand. These elements help teams continuously explore customer needs, develop high-quality solutions, deploy them to various environments, and release them to customers when and where they want. References: Agile Product Delivery, Continuous Delivery Pipeline

Reducing delays is the focus of Lean thinking. Lean thinking is a philosophy and a set of principles and practices that aim to eliminate waste and optimize value delivery. Waste is anything that does not directly contribute to customer value or that causes delays in delivering value. Delays are the primary cause of waste, as they increase inventory, risk, variability, overhead, and dissatisfaction. Reducing delays means minimizing the time between customer need and value delivery, which improves quality, efficiency, and customer satisfaction. References: Thriving in the Digital Age, SAFe Principle #2

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

From the Agile Manifesto as stated in the SAFe Workbook:

“Customer collaboration over contract negotiation”

This is one of the four core value statements that define Agile methodology.