ART · Roles
ART roles: the Triangle
Product Management, System Architect and Release Train Engineer: three overlapping roles that lead the train as one team. SAFe doesn’t name these three roles together; we call them the Triangle.
01Three roles, one team
Product Management, the System Architect and the Release Train Engineer lead the ART together. Each brings a different question: Product Management the why, the System Architect the how, the RTE the way of working.
It is the same shape as a Scrum team one level up. Product Owner, Developers and Scrum Master overlap, interact and collaborate; so do the three ART roles. The overlap is where the work happens, not a fault in the role descriptions.
The roles overlap on purpose, not as silos. They are interdependent by design: none of the three can succeed on its own, so they have to collaborate. Clean boundaries and hand-overs would make each role look efficient and the train slow. The overlap is what turns three roles into one team.
Their first team is the one they belong to, the Triangle itself, not the one they lead. One purpose for the ART, carried by the three of them, and each of them answers for the result of the ART beyond the output of their own role.
02What the three share
Servant leadership. All three lead by serving the train: they create the conditions in which the teams can do their best work, remove what is in the way, and grow the people around them. Authority comes from helping, not from position.
Continuous improvement. The way of working is never finished. All three inspect it and adapt it at every System Demo and every Inspect & Adapt, starting with how the Triangle itself works.
Systems thinking. All three optimise the whole value stream, not their own part of it. A local improvement that slows the flow somewhere else is no improvement; the result of the train, for the customer, is what counts.
03Product Management — the why
Owns what the train works on next, and why: the ordered ART backlog, from the Epic's hypothesis to each Feature's benefit hypothesis.
Works outward and upward with customers, Epic Owners and Business Owners: the vision and the roadmap of the train, kept honest by what the market says.
Presents the vision and the ordered Features at PI Planning, accepts Features at the System Demo, brings the evidence to the QBR.
Does for the train what a Product Owner does for a team: with the Product Owners, not over them.
04System Architect — the how
Keeps one solution whole across many teams: the architectural runway, the enablers that keep options open, the interfaces and the non-functionals.
Brings the architecture vision to PI Planning, the dependencies and technical risks to the board, and the integrated system to the System Demo.
Asks rather than designs for the teams: “How will five teams build one thing?” The teams answer. The architect provides guardrails; decisions stay where the information is.
05Release Train Engineer — the way of working
Facilitates the train; the train does the work. PI Planning, ART Sync, System Demo, Inspect & Adapt.
Makes flow visible: the ART board, the dependencies, the risks and the impediments that cross teams. What the board shows, the train sees.
Coaches Scrum Masters, Product Owners and Business Owners on how the train works together, rather than on what it builds.
Makes no plan for the teams. The RTE makes the room where the teams make it, and keeps it running.
06What it turns into under business as usual
The three roles are filled with the old titles. Product Management becomes the boss of the Product Owners and hands out work to them, the System Architect becomes the design authority that approves solutions, and the RTE becomes the programme or project manager who chases status.
Each guards its own territory and escalates to the other two. The overlap, where the decisions should be made together, becomes a gap that nobody owns.
07How you notice
- The Product Owners wait for Product Management to tell them what to do.
- Teams wait for the architect's design before they can start.
- The RTE writes the PI plan, or reports status upward.
- The three roles rarely meet without the teams, or only meet with them.
- Nobody can say what the three of them decide together.
08How to make it work
Draw three overlapping circles and place every responsibility: mine, shared between two, common to all three, or the teams'. Talk only about what lands in the overlaps, the centre and outside.
For the real decisions of the first PI, ask where the information is best, who decides with whom, and by when at the latest.
Write working agreements the three of you can point each other to, and revisit them at every Inspect & Adapt.
Working with a starting ART? The ART day builds the Triangle's own first version of its roles, events and backlog in one day.