Project Management Process

2. Program Level (ART – Agile Release Train): New in SAFE

• Program Level = Team of Agile Teams

• Organized as an Agile Release Train (ART).

• Typically includes 5–12 Agile teams (~50–125 people).

• Each team follows Scrum or Kanban.

• Roles:

• Release Train Engineer (RTE): Chief Scrum Master; facilitates PI Planning across all SQUADs

• Product Manager: Manages program backlog; defines Features. He is higher level of PO, who manages all POs.

• System Architect: Guides architecture and technical design for the program.

• Key Artifacts:

• Program Backlog: Features (not stories).

• Program Increment (PI): 8–12 week planning/delivery cycle.

• PI Objectives: Business goals for the PI.
  
  

• Key Events:

• PI Planning: Cross-team planning session.

• System Demo: Integrated demo from all teams.

• ART Sync: Synchronizes teams (includes Scrum of Scrums).

3. Solution Level (for large systems)

The Solution Level coordinates multiple Agile Release Trains (ARTs) and Suppliers to deliver large-scale, capability-level solutions (e.g., aerospace, defense, telecom platforms).

• Key Roles:

• Solution Train Engineer: Coordinates multiple ARTs

• Solution Manager: Manages capabilities, roadmap

• Solution Architect: Leads solution-level technical direction

• Best Practices for Applying Solution Level:

•  Use Capabilities instead of Features
  → Enables cross-ART alignment.

•  Synchronize ARTs with common PI cadence
  → Enables unified delivery via Solution Train.

• Conduct Pre-PI & Post-PI Planning
  → Align ARTs and stakeholders early and often.

• System Thinking at Scale
  → Apply SAFe Principle #2: “Apply Systems Thinking” to entire solution.

• Solution Demo Every PI
  → Ensures full visibility across all trains.

• Artifact

• Solution Vision

• Solution Roadmap

• Program Backlog: Contains prioritized Features managed by the Product Management team.

• PI Objectives: What the ART commits to delivering in a Program Increment.

• Program Board: Visualizes feature delivery over time and cross-team dependencies.

Involved Roles:

• Epic Owners – Drive epics from idea to implementation

• Enterprise Architects – Ensure technical alignment

• Business Owners – Prioritize value

• LPM Team – Oversees budgets, strategy, governance

4. Portfolio Level

The Portfolio Level is the highest level in SAFe. It aligns strategy with execution across the entire enterprise.

The Portfolio Level provides:

• Strategic direction

• Investment funding

• Lean governance

• Management of Epics, Value Streams, and budgets

Key Components:

• Value Streams: End-to-end workflows delivering value; each may include ARTs or Solutions

• Epics: Large, strategic initiatives (Business or Enabler)

• Lean Portfolio Management (LPM): Governs strategy, funding, and governance using Lean principles

• Portfolio Backlog: Holds approved Epics awaiting implementation

• Guardrails: Set policies for funding and decision-making