Features in SAFe should be right-sized, delivering value and being small enough for incremental

delivery within a PI. If the current backlog items are too large (“big tasks”), the best technique is to

split them into smaller, more manageable Features. This enables meaningful WSJF prioritization and

supports flow-based delivery.

Reference:

SAFe 6.0 Website: Features and Capabilities

SPC 6.0 Guide: “Right-size Features to fit within a PI for effective prioritization and delivery.”

===========

SAFe defines four Core Values: Alignment, Built-in Quality, Transparency, and Program Execution.

These values help executives understand the framework’s foundation and address concerns about

consistent delivery, quality, trust, and business alignment.

“SAFe’s four core values are: Alignment, Built-in Quality, Transparency, and Program Execution.”

(Source: SAFe 6.0 Framework: Core Values; SPC 6.0 Guide, “Becoming a Lean-Agile Leader”)

SAFe emphasizes enabling leadership over command-and-control. Legitimate enabling functions include: B: Communicating vision helps teams align without dictating execution. C: Facilitating cross-team communication removes barriers, enabling team success. F: Developing skills and career paths grows team capability and autonomy. G: Creating mutual influence supports empowerment and innovation. Options A, D, and E are examples of directive, top-down control—antithetical to Lean-Agile leadership. Reference: SAFe 6.0 Website: Lean-Agile Leadership SPC 6.0 Guide: “Lean-Agile leaders enable, coach, and develop teams instead of directing their work.” ===========

In SAFe, when a solution requires more capacity than a single ART (Agile Release Train) can provide,

multiple ARTs are grouped into a Solution Train. These ARTs work together within a Value Stream.

The Value Stream level provides coordination, additional roles, and artifacts to align the multiple

ARTs toward delivering larger, complex solutions.

“When multiple ARTs collaborate to build a solution, coordination at the Value Stream level is

required. The Solution Train roles and events support alignment and integration of the work across

ARTs and Suppliers.”

Reference:

SAFe 6.0 Framework: Solution Train and Value Stream Level

SAFe 6.0 SPC Guide: “Establishing Team and Technical Agility” module

The Spanning Palette is a set of roles and artifacts that may apply across multiple SAFe levels,

including Team, ART, Solution Train, and Portfolio. The Spanning Palette includes functions like

System Architect, Release Management, Shared Services, and more. SAFe explicitly notes that these

elements are used “as needed at each level, including the Team level, depending on context.”

Reference:

SAFe 6.0 Website: Spanning Palette

SPC 6.0 Guide: “Spanning Palette elements are used across one or more SAFe levels, including the

Team level.”

===========

A key SAFe Principle is “Take an economic view.” SAFe encourages developing and using an economic

decision-making framework to ensure all work is evaluated and prioritized based on its economic

impact, such as using WSJF and other economic trade-off tools.

“Developing an economic framework for decision-making is a key tool for ensuring that decisions

maximize the economic outcomes for the business.”

(Source: SAFe 6.0 Framework: Economic Decision Making; SPC 6.0 Guide “Exploring Lean Portfolio

Management”)

===========

Enabler Features are used to extend the Architectural Runway and/or address Nonfunctional

Requirements (NFRs). They can do both simultaneously, as enablers provide the necessary

infrastructure, tooling, or compliance support to both functional and nonfunctional solution needs.

Reference:

SAFe 6.0 Website: Enabler

SPC 6.0 Guide: “Enabler Features can support runway and NFRs at the same time.”

===========

Enablers in SAFe are a special type of backlog item used to build or enhance architecture,

infrastructure, and exploration activities that enable future business functionality. They are essential

for creating and maintaining the development and delivery pipeline.

“Enablers build or enhance the Architectural Runway, development infrastructure, and support

exploration necessary for future Features.”

(Source: SAFe 6.0 Framework: Enablers; SPC 6.0 Guide “Building Solutions with Agile Product

Delivery”)

===========

“Expedite” is a Kanban class of service for critical items that require immediate attention. SAFe

permits items in the Expedite lane to override or break WIP (Work In Process) limits to ensure urgent

delivery.

“Expedite items are allowed to break WIP limits to ensure that urgent issues are addressed as quickly

as possible.”

(Source: SAFe 6.0 Framework: Kanban Classes of Service)

===========

SAFe recognizes that cultural change occurs alongside, not before, SAFe implementation. Leading

change, including shifts in mindset and behavior, is integral to the SAFe Implementation Roadmap

and happens through practice and reinforcement as the framework is adopted.

“Cultural change happens concurrently with the implementation of SAFe—not as a prerequisite.

Mindset and behaviors evolve as people begin to experience new ways of working.”

(Source: SAFe 6.0 Framework: Implementation Roadmap; SPC 6.0 Guide “Leading the Change”)

===========