Agile guide · Scaling Agile
What Is an Agile Release Train (ART) in SAFe?
An Agile Release Train (ART) is a long-lived team of Agile teams that plans, commits and delivers together on a shared schedule. It is the central delivery structure of the Scaled Agile Framework.
Key takeaways
- An ART is a long-lived team of Agile teams, typically 50 to 125 people.
- It plans together every PI and shares a common cadence.
- The Release Train Engineer facilitates and coaches the ART.
Characteristics of an ART
- Typically 50 to 125 people in several Agile teams.
- Organised around a flow of value, such as a product, customer journey or service.
- Has all the skills needed to define, build, test and release its solution.
- Shares a common cadence: all teams start and end iterations together.
- Plans together every Program Increment (PI), usually 8 to 12 weeks.
- Is long-lived: work is brought to the train rather than forming new teams for each project.
Key roles
| Role | Responsibility |
|---|---|
| Release Train Engineer (RTE) | Facilitates ART events, removes impediments, coaches leaders and teams |
| Product Management | Defines and prioritises features in the ART backlog |
| System Architect | Provides architectural guidance and enablers |
| Business Owners | Set business objectives and accept outcomes |
| Agile teams | Deliver stories and features in iterations |
ART events
- PI Planning: the whole train plans the next increment together.
- ART Sync: a regular coordination meeting covering progress, dependencies and impediments.
- System Demo: the integrated result of all teams is shown at the end of each iteration.
- Inspect and Adapt: a workshop at the end of each PI to review results and solve problems.
Launching an ART
- Identify the value stream and the people needed to serve it.
- Train leaders and teams.
- Prepare the ART backlog of features.
- Hold the first PI Planning event.
- Run the PI and inspect and adapt at the end.
Free templates for this topic
Frequently asked questions
Why is it called a release train?
Like a train timetable, the ART runs on a fixed, predictable schedule. Features that are ready catch the train; those that aren't wait for the next one.
Does an Agile Release Train release only at the end of a PI?
No. Planning follows the PI cadence, but teams can release whenever value is ready.
What is an Agile Release Train?
In SAFe, a long-lived team of Agile teams, typically 50 to 125 people, organised around a flow of value and planning and delivering together.
How many teams are in an Agile Release Train?
Usually several Agile teams of about ten or fewer people each, giving a total of around 50 to 125 people.
What does a Release Train Engineer do?
Facilitates ART events such as PI Planning, removes impediments and coaches leaders and teams.
What is a System Demo on an Agile Release Train?
A demonstration of the integrated work of all teams on the ART, held at the end of each iteration.
What is Inspect and Adapt for an Agile Release Train?
A workshop at the end of each PI in which the ART reviews results and solves systemic problems.
What is ART Sync on an Agile Release Train?
A regular coordination meeting covering progress, dependencies and impediments across the teams on the train.
How is an Agile Release Train different from a project team?
An ART is long-lived and work is brought to it, while a project team is formed for one project and disbands at the end.
How does a value stream relate to an Agile Release Train?
The series of steps an organisation uses to deliver value to a customer. ARTs are organised around value streams.
How do you launch an Agile Release Train?
Identify the value stream and people, train leaders and teams, prepare the feature backlog, hold the first PI Planning, then run and review the PI.