パスできるSAFe-Agilist試験最速合格保証2026問題集！ [Q57-Q71]

Explanation
According to the SAFe Agilist 6.0 domain of Develop on Cadence, Release on Demand, an Agile Release Train (ART) is a long-lived team of Agile Teams that delivers value in a regular and predictable manner1. An ART has a set of events that occur every Program Increment (PI), which is a fixed timebox of 8 to 12 weeks2.
These events are:
PI Planning – A two-day event where all members of the ART collaborate to align on a shared vision, identify dependencies, and plan the work for the next PI3.
PI System Demo – A demonstration of the new functionality delivered by the ART in the current PI, integrated with other solutions where applicable4.
Inspect and Adapt (I&A) – A one-day event where the ART reflects on the current PI and identifies improvement actions for the next PI5.
Innovation and Planning (IP) Iteration – A two-week iteration that occurs at the end of every PI, where the ART reserves time for innovation, planning, and continuous improvement.
In addition to these PI events, an ART also has iteration events that occur every two weeks, which are:
Iteration Planning – A meeting where each Agile Team plans the work for the current iteration, based on the PI objectives and team backlog.
Iteration Review – A meeting where each Agile Team demonstrates the working software they have built in the current iteration and collects feedback from stakeholders.
Iteration Retrospective – A meeting where each Agile Team inspects their processes and practices in the current iteration and identifies improvement actions for the next iteration.
Scrum of Scrums (SoS) – A meeting where representatives from each Agile Team coordinate and collaborate on cross-team dependencies and impediments.
Product Owner Sync (PO Sync) – A meeting where Product Owners from each Agile Team align on backlog priorities and dependencies.
Therefore, out of the three options given, only Iteration Retrospective is one of the ART events. Backlog refinement is not an official event in SAFe, but rather an ongoingactivity that occurs throughout the PI.
Product Owner sync is not an iteration event, but rather a PI event that occurs every two weeks.

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.

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

Explanation
According to the SAFe Agilist 6.0 domain of Built-in Quality, this practice reduces bottlenecks and ensures consistency by:
Encouraging teams to share responsibility for the quality of their work products Establishing common standards and guidelines for coding, testing, documentation, etc.
Enabling teams to collaborate and coordinate across domains and dependencies Promoting a culture of continuous improvement and learning
https://scaledagileframework.com/built-In-quality/

Explanation
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

SAFe draws from Kotter’s model and describes the dual operating system:
“Organize the Enterprise around the flow of value while maintaining the hierarchies… This dual system leverages stability and speed.”

This statement is true about batch size. Batch size is the amount of work that moves as a unit through a process or system. Large batch sizes increase variability by creating more uncertainty, complexity, dependencies, and unpredictability in the workflow. Large batch sizes also increase waste by causing delays, queues, handoffs, rework, overproduction, and inventory accumulation. Reducing batch size is one of the key ways to optimize value delivery and improve flow efficiency. References: SAFe Lean-Agile Principles, SAFe Principle #5

The primary goal of SAFe is to achieve business agility. Business agility is the ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative solutions. Business agility requires that everyone involved in delivering solutions-business and technology leaders, development, IT operations, legal, marketing, finance, support, compliance, security, and others-use Lean and Agile practices to continually deliver innovative, high-quality products and services faster than the competition. References: Thriving in the Digital Age, Business Agility

Explanation
This statement is true about batch size. Batch size is the amount of work that moves as a unit through a process or system. Large batch sizes increase variability by creating more uncertainty, complexity, dependencies, and unpredictability in the workflow. Large batch sizes also increase waste by causing delays, queues, handoffs, rework, overproduction, and inventory accumulation. Reducing batch size is one of the key ways to optimize value delivery and improve flow efficiency. References: SAFe Lean-Agile Principles, SAFe Principle #5

“Precisely specify value by product” is central to Lean thinking. Lean thinking is a philosophy and a set of principles and practices that aim to eliminate waste and optimize value delivery. Value is defined as anything that a customer is willing to pay for or that meets their needs or desires. Value is specified by product, which means that each product or service should have a clear and explicit definition of what value it provides to the customer and how it differs from other products or services. Specifying value by product helps avoid ambiguity, confusion, andinefficiency in the value delivery process. References: Thriving in the Digital Age, SAFe Principle #1

User business value and time criticality are components of cost of delay. Cost of delay is a way of quantifying the economic impact of delaying the delivery of a product or feature. Cost of delay consists of four factors:
user or customer value, time criticality, risk reduction or opportunity enablement value, and job size or duration. Cost of delay is used to prioritize features using Weighted Shortest Job First (WSJF), which is a method that maximizes the economic value delivered by a product development flow. References: ART Backlog and WSJF, SAFe Principle #1