Agile Release Train (ART) Launch

Foundations

Agile Release Train (ART)

A long-lived team of Agile teams (50–125 people) that develops and delivers value on a Program Increment cadence within a value stream.

ART Launch

The process of preparing teams, roles, backlog, and logistics and running the first PI Planning so an ART begins delivering value on cadence.

Why Launch Well

A strong launch establishes alignment, cadence, and momentum; a weak launch undermines the ART's performance for PIs to come.

Program Increment (PI)

A timebox (typically 8–12 weeks) during which the ART delivers value and which provides the planning and integration cadence.

Identify Value

Value Stream Identification

Identifying the operational and development value streams and the ARTs that realize them, so the train is organized around value.

Operational vs. Development Value Stream

Operational streams deliver value to customers; development streams build the solutions that enable them. ARTs align to development value streams.

Organizing Around Value

Designing teams and the ART around the flow of value rather than functional silos, minimizing dependencies.

Sizing the ART

Forming a train of roughly 50–125 people so it is large enough to deliver meaningful value and small enough to plan together.

Teams & Roles

Agile Teams

Cross-functional teams of 5–11 people that can define, build, test, and deliver value; several make up an ART.

Release Train Engineer (RTE)

The servant leader who facilitates ART events and processes and helps the train deliver value.

Product Management

Owns the ART backlog and vision and defines features for the train.

System Architect

Provides architectural guidance and enablers so the ART builds a coherent solution.

Business Owners

Key stakeholders accountable for the value delivered by the ART, who assign business value to objectives.

Preparation

Implementation Plan

The plan for which ARTs launch and when, and the steps to prepare each one.

Preparing the ART Backlog

Defining and prioritizing the features and vision so teams have meaningful content for the first PI Planning.

Vision and Roadmap

A clear vision and near-term roadmap that give teams direction and context for planning.

Training Teams

Preparing everyone with the SAFe knowledge and roles they need before the launch, often via a quickstart.

Readiness (Org, Content, Logistics)

Ensuring organizational alignment, ready content, and event logistics are all in place before launch.

PI Planning

First PI Planning

The cornerstone launch event where all teams plan the first PI together, align to the vision, and commit to objectives.

PI Objectives

Business and technical goals teams commit to for the PI, with business value assigned by Business Owners.

Program Board

A visualization of features, milestones, and cross-team dependencies produced during PI Planning.

Confidence Vote

A vote at the end of PI Planning expressing the teams' confidence in meeting the plan.

ROAM Risks

Classifying risks as Resolved, Owned, Accepted, or Mitigated so each is visible and handled.

After Launch

Executing the First PI

Running iterations, ART sync, and system demos to deliver and integrate value after launch.

Coaching the ART

Supporting teams and roles through early PIs to build capability and improve performance.

Inspect & Adapt

The end-of-PI event to demo, measure, and identify improvements for the next PI.