Lean thinking, which underpins SAFe, emphasizes achieving fast and sustainable flow through:

Understanding the full Value Stream (A): This enables identification and removal of bottlenecks and waste.

Constant reduction of delays (B): Reducing delays improves flow and time-to-market.

Reducing batch sizes (C): Smaller batches move through the system faster, reducing cycle time and increasing feedback.

Applying “subjective governance” (D) is not a Lean principle; governance should be objective and supportive of flow.

“Lean organizations achieve fast and sustainable flow by mapping the Value Stream, reducing batch sizes, and continuously removing sources of delay.”

(Source: SAFe 6.0 Framework: Lean-Agile Mindset and Principles; SPC 6.0 Guide, “Thriving in the Digital Age and Business Agility”)

===========

SAFe Principle #3 states: “Assume variability; preserve options.” The optimum path is to preserve flexibility in both system functionality and design as long as possible, enabling better decision-making with more information and reducing the risk of suboptimal solutions.

The other options either fix one dimension or another, which is contrary to the principle.

At the end of Day 1 of PI Planning, managers and key stakeholders meet to review program risks, PI Objectives, and dependency issues raised by teams. The primary purpose is to make adjustments to scope, resolve challenges, and provide guidance for Day 2 planning.

Long queues in product development systems create multiple problems:

Higher variability (A): Work spends more time waiting, which increases variability in lead times.

More multitasking (D): With many items in process, people switch between tasks, reducing effectiveness.

Slower delivery (E): The more work in the queue, the longer it takes to get through the system.

Lower quality (F): Long waits cause context loss, handoff errors, and rework, reducing quality.

“Long queues increase cycle times and variability, cause more multitasking, slow delivery, and lower quality.”

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

===========

SAFe requires that all Agile Teams conduct Iteration Planning at the start of every Iteration. This aligns the team on the work for that Iteration, enables fast feedback, and adapts to new learnings from the prior Iteration. It is not optional, regardless of dependencies or whether acceptance criteria were set in PI Planning.

“Iteration Planning is required at the beginning of every Iteration. This ensures that the team aligns on what can be delivered in the upcoming Iteration, establishes a clear plan, and sets up a fast feedback loop.”

(Source: SAFe 6.0 SPC Guide, "Building Solutions with Agile Product Delivery" module; Iteration Planning event.)

Enablers in SAFe are a specific type of backlog item used to support business features. They generally fall into three categories:

Architecture (A): To build or extend the Architectural Runway.

Exploration (C): To research, evaluate, or experiment (such as spikes).

Infrastructure (E): To build or enhance tools, systems, or processes required for development and delivery.

Team tasks and vertical feature slices are not enabler categories.

“Enablers support exploration, architecture, or infrastructure that enables future business functionality.”

(Source: SAFe 6.0 Framework: Enablers)

===========

WSJF (Weighted Shortest Job First) uses job size or duration as the denominator to prioritize work. SAFe often uses feature size (story points) as a proxy for duration. However, this is not always accurate:

B: If a Feature involves a team or member who is a bottleneck, the actual duration may be longer than estimated by size, due to limited availability.

D: If a Feature depends on a remote third-party vendor with formal approval processes, duration may be impacted by external delays not reflected in the feature’s size.

Options A, C, and E do not directly impact the suitability of size as a proxy for duration.

All Agile Release Trains (ARTs), regardless of being composed solely of Feature teams, require Architectural Runway. The runway provides the necessary technical foundation to support upcoming Features and to enable a sustainable pace of delivery. This is a universal need in SAFe, regardless of team composition.

According to SAFe 6.0, System Teams are integral to the ART and are considered equal members. The recommended best practice is:

“System Team members should attend SAFe for Teams training together with all other teams on the train to ensure shared understanding of Agile, SAFe, and the train’s objectives and practices.”

This approach supports alignment, collaboration, and shared learning. Other answers do not ensure integration with the ART or are targeted at other roles or less comprehensive.

Lowering WIP limits reduces multitasking, exposes bottlenecks, and encourages team members to collaborate to finish work before starting new work. This is a core Lean and SAFe principle to increase flow and throughput.

A is incorrect; excessive WIP delays feedback. B is incorrect; WIP is highly related to utilization and flow.