The ART Sync is a program-level synchronization event that brings together Scrum Masters and Product Owners. It is typically facilitated by the Release Train Engineer (RTE), who serves as the chief Scrum Master for the train, ensuring smooth coordination and flow across teams.

“The Release Train Engineer (RTE) is the servant leader and coach for the ART and typically facilitates the ART Sync.”

(Source: SAFe 6.0 Framework: ART Events; SPC 6.0 Guide, “Coaching ART Execution”)

===========

In SAFe 6.0, Capabilities are defined as "higher-level solution behaviors that typically span multiple ARTs." They are maintained in the Solution Train Backlog and are sized and split into Features for implementation by individual ARTs. The SAFe 6.0 guidance specifically states:

“Capabilities are larger solution behaviors that often span multiple Agile Release Trains. They are typically sized to be delivered in a Planning Interval (PI) and are broken down into Features to facilitate implementation.”

This distinguishes Capabilities from Epics and Features. Unlike Epics, which require Lean Business Cases and approval through Portfolio Kanban, Capabilities follow a breakdown path to Features for execution. Therefore, they are a level above Features , not a synonym for Epics or Features.

Cost of Delay is the economic impact of delaying or deferring work. It combines opportunity cost and potential revenue lost due to not delivering value sooner. It is a key metric for prioritizing work in SAFe.

WSJF (Weighted Shortest Job First) is a prioritization method recommended by SAFe for use at the Program and Portfolio levels, especially for prioritizing Features and Epics. At the Team level, backlog items (Stories) are generally prioritized based on local context, dependencies, and feedback, not through WSJF.

“WSJF is the recommended approach for prioritizing the Program Backlog (Features). It is generally not used for the Team Backlog (Stories), which are usually prioritized in collaboration with the Product Owner based on iteration goals, dependencies, and value.”

(Source: SAFe 6.0 SPC Guide, "Establishing Team and Technical Agility" module; Team Backlog section.)

===========

Limiting WIP:

Reduces multiplexing (A): Teams and individuals do less context switching and focus more.

Decreases wait times (B): Items flow through the system faster with less time spent waiting.

Increases throughput (E): Limiting WIP ensures more items complete in a given period.

“Limiting WIP decreases wait times, reduces context switching (multiplexing), and increases throughput.”

(Source: SAFe 6.0 Framework: Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths.)

===========

The Solution Context defines the environment in which the solution operates, including operational, regulatory, deployment, and support conditions. For a Solution Architect, understanding this environment is essential to ensure the solution will function as required in its real-world context.

In the transition to SAFe, traditional program managers most often assume the role of Release Train Engineer (RTE) or Value Stream Engineer (VSE).

The RTE is described as “the chief Scrum Master for the train,” focusing on program-level facilitation, coordination, and execution—duties very similar to those of a traditional program manager.

The VSE supports the coordination of multiple ARTs in a Solution Train.

The SAFe Practice Consultant (SPC) 6.0 guide explicitly notes:

“Program managers typically become Release Train Engineers (RTEs) or Value Stream Engineers (VSEs) in SAFe, as these roles align with their experience in coordinating teams and managing delivery at scale.”

The Architectural Runway in SAFe consists of the existing code, components, and technical infrastructure necessary to support the implementation of prioritized, near-term Features without excessive redesign and delay. Its importance is twofold:

It supports a stable velocity (A): Teams need sufficient architectural runway to maintain a predictable velocity and reduce technical debt. As stated in SAFe, “Architectural Runway enables teams to build features quickly and efficiently, thus maintaining stable velocity.”

It iteratively evolves the architecture to meet changing needs (C): SAFe recommends an incremental and emergent architectural approach. The runway is not static; it evolves to meet the emerging business and technical requirements, “just enough, just in time.”

Incorrect options:

B is incorrect—while documentation may be produced, the runway itself is not documentation but actual working infrastructure.

D is incorrect—runway specifically supports technical changes, not nontechnical ones.

Story points are used for estimating the size of Stories (team-level items). Features and Capabilities are estimated using Story points or other measures, but Epics are usually estimated in person-months or t-shirt sizes, not Story points, due to their scale and complexity.

Lean-Agile leaders in SAFe are characterized by:

A: Establishing clear objectives, providing clarity and direction.

D: Supporting decentralized decision-making, empowering teams.

E: Emphasizing lifelong learning, modeling and fostering a growth mindset.

Leaders do not directly develop solutions (B)—that’s the teams’ responsibility. Protecting subordinates from all outside influence (C) is not Lean-Agile leadership; instead, leaders encourage collaboration and openness.