Enterprise Architects focus on cross-ART and cross-Value Stream strategy and technical alignment. Defining Solution design for Agile Release Trains (C) is the responsibility of Solution/System Architects at the ART or Solution Train level, not Enterprise Architects.

“Enterprise Architects define and communicate a shared technical and architectural vision for the enterprise. Solution and System Architects design at the ART/Solution Train level.”

(Source: SAFe 6.0 Framework: Enterprise Architect, Solution Architect)

===========

A: Business Owners assign business value to PI Objectives during PI Planning, ensuring alignment with business priorities and objectives.

B: Business Owners participate in PI events (including Post-PI Planning) and help ARTs adjust plans to better meet business needs.

Assigning value to Epics/Features (C) is the responsibility of Product Management. Ensuring the Solution Demo (D) is a shared leadership responsibility, not specific to Business Owners. Determining the roadmap (E) is owned by Product Management.

Capacity allocation in SAFe is the explicit allocation of a portion of backlog capacity to Enablers, which include activities like building or maintaining the Architectural Runway. This ensures that teams continuously invest in infrastructure and architectural work needed for sustainable development, rather than focusing solely on immediate feature delivery.

“Capacity allocation ensures that a portion of team and ART resources is always dedicated to Enabler work, such as building the Architectural Runway, allowing the enterprise to invest in future capabilities while delivering current value.”

(Source: SAFe 6.0 Framework: Capacity Allocation; SPC 6.0 Guide “Building Solutions with Agile Product Delivery”)

===========