Agile release train (ART)
An Agile Release Train is a long-lived team-of-teams in SAFe — typically 50-125 people across 5-12 Agile teams — that plans, commits, and releases together on a fixed cadence called a Program Increment (PI). The ART aligns all included teams to a shared vision, mission, and PI Objectives.
ARTs are SAFe's primary unit of value delivery above the single team. The 50-125 person sizing is deliberate: small enough that PI Planning fits in a single room (physical or virtual), large enough to deliver end-to-end value without external dependencies. Each ART has standing roles — Release Train Engineer, Product Management, System Architect, Business Owners — and a fixed cadence of events (PI Planning every 8-12 weeks, System Demo every iteration, Inspect & Adapt at PI end). The choice of how to slice an organisation into ARTs is one of the most consequential SAFe design decisions; getting it wrong leads to constant cross-ART dependencies that destroy the cadence benefit.
Related terms
- Program increment (PI)
A Program Increment is SAFe's timebox for an Agile Release Train — typically 8-12 weeks, usually 5 iterations of 2 weeks each.
- PI planning
PI Planning is the 1-2 day event at the start of each Program Increment where the entire Agile Release Train — all teams, Product Management, Business Owners, System Architect — assembles to plan the upcoming PI.
- Release train engineer (RTE)
The Release Train Engineer is the chief Scrum Master of an Agile Release Train — facilitating PI Planning, removing impediments across teams, managing risks and dependencies, and coaching the ART on SAFe practices.