Facilitator at a flip chart with a team around a table in a brick-walled workspace

Workshop Guide

ART Organization Workshop Guide

Design Agile Release Trains and their teams around the flow of value, not the org chart.

01 / Summary

What Is ART Organization?

ART Organization is the structured practice of deciding who belongs on each Agile Release Train (ART), how those people form Agile Teams, and how those teams work with one another. An ART is a long-lived team of Agile Teams that develops, delivers, and often operates one or more solutions in a development value stream. Drawing its boundaries around value, rather than around departments or components, is what lets work flow with fewer handoffs.

Run this workshop after your value streams are identified and before your first ART launch. It turns a value stream map and a list of people into a draft ART design: ART boundaries, teams with a clear type and mission, a dependency map, and named ART roles that leadership can review and approve.

Organize Around Value

Align each ART to a development value stream so the people who define, build, test, and release a solution plan and deliver together.

Reduce Cross-Team Dependencies

Shape team boundaries and team types so most work can be finished inside one team, and the rest flows through clear interaction modes.

Launch with Clear Roles

Name the Release Train Engineer, Product Management, System Architect, and Business Owners before the first PI Planning event, not during it.

02 / Application

When to Use ART Organization

ART Organization is most useful at the moment an organization moves from identifying value streams to actually launching trains, and any time the current train structure is slowing work down. Use this workshop whenever teams are organized around functions or components, handoffs are eating delivery time, or an ART has grown too large to plan together.

Preparing for a First ART Launch

Value streams have been identified and leadership is ready to launch a train. This workshop converts that decision into a concrete design: who is on the ART, which teams it contains, and who fills each ART role.

Too Many Handoffs Between Teams

Features routinely wait on another team to finish its part. Reorganizing around value and choosing the right team types reduces the number of teams any one feature has to pass through.

An ART That Has Outgrown Itself

A train has grown past the point where everyone can plan together effectively. SAFe describes ARTs as generally 50 to 125 people; this workshop helps you split along value lines rather than by component or department.

After a Value Stream Mapping Session

A new or updated value stream map has exposed delays, rework, or missing skills. This workshop takes those findings and redesigns team and ART boundaries to remove them.

Prerequisites

Identified Value Streams

The operational value stream and the development value stream that supports it should already be identified. Without them, ART design turns into an org chart exercise instead of a design for the flow of value.

A People and Systems Inventory

Bring a current list of everyone who defines, builds, tests, or releases the solution, with their skills, managers, locations, and allocation, plus a list of the systems and components they work on.

Roles and Responsibilities

Facilitator (SPC, LACE, or RTE)

Runs the session, keeps design decisions anchored to the value stream, and makes sure open decisions are captured with owners rather than debated without end.

Business Owners and Executive Sponsor

Confirm the value stream and solution scope, approve the ART boundaries, and own decisions that need leadership authority such as reporting lines, funding, and hiring.

Product Management and System Architect

Explain how the solution and its architecture are structured so teams can be shaped around real slices of value and real system boundaries.

Functional Managers and Team Leads

Bring accurate knowledge of people, skills, and current allocation, and help identify scarce skills and realistic team compositions.

This workshop works best when both business and technical leaders are in the room. A design built only by technical leaders tends to mirror the architecture; one built only by business leaders tends to mirror the org chart. The goal is a design that follows the flow of value.

Scheduling and Timing

Run after value streams are identified and before ART launch preparation begins, so the design can inform launch planning and the first PI Planning event.
Plan for about three and a half hours for a single ART, including a break; block a full day when the session is designing several ARTs in one value stream.
Hold a 30-minute pre-session checkpoint with the Executive Sponsor and facilitator one week before to confirm scope, decision rights, and that the people inventory is ready.
Schedule a leadership review of the draft design within two weeks of the session so open decisions are closed before launch planning starts.

03 / Preparation

Preparing for the Workshop

An ART Organization session is only as good as the inputs in the room. When participants arrive with a confirmed value stream, an accurate people inventory, and clear decision rights, the session produces a design leadership can act on. When they arrive without them, the session turns into a debate about reporting lines. The checklist below covers what to prepare in advance.

Confirm the operational and development value streams in scope, and bring the most recent value stream map.
Build a current inventory of everyone who defines, builds, tests, or releases the solution: role, primary and secondary skills, manager, location and time zone, and allocation.
List the systems, components, and platforms the solution depends on, and which people work on each today.
Agree with the Executive Sponsor on decision rights: what the room can decide, and which decisions (reporting lines, funding, hiring) go to an Open Decisions log for leadership.
Prepare the ART Organization Excel Template by loading the people inventory into the People & Skills tab and confirming the size assumptions on the Instructions tab.
Set up the Miro board (or a wall) with a lane for each candidate ART, a space for each proposed team, and a parking lot for open decisions.
Download and prepare the Facilitator Presentation.
Send scheduling communication with agenda and pre-read materials
Email Template
Subject: [Value Stream Name]: ART Organization Workshop: [Date]

Hi team,

We are holding an ART Organization Workshop on [Date] from [Start Time] to [End Time] [Time Zone] via [Platform/Location]. In this session we will design how our people and teams come together into one or more Agile Release Trains (ARTs) for the [Value Stream Name] value stream, so that work can flow with fewer handoffs.

To make the most of our time together, please come prepared with the following:

Confirmation that your team members are listed correctly in the attached people inventory (role, skills, manager, location, and allocation)

The systems and components your team works on today

Any known constraints, such as shared specialists, time zone limits, or upcoming staffing changes

Please review the attached value stream map before the session. We will leave with a draft ART design and a list of open decisions for leadership. No final reporting-line decisions will be made in the room.

Please reach out with any questions before the session.

Thank you,
[Your Name]
[Title] | Stephens Insight Group
Calendar Invite Copy

Subject: [Value Stream Name]: ART Organization Workshop: [Date]

Purpose: Design ART boundaries, teams, and ART roles for the [Value Stream Name] value stream.

Please bring: A reviewed people inventory for your area, the systems your team works on, and any known staffing constraints.

Agenda:
– Set the Stage (15 min)
– Confirm Value Stream and Solution Scope (20 min)
– Inventory People and Skills (30 min)
– Define ART Boundaries (30 min)
– Design Teams by Team Type (45 min)
– Map Dependencies and Interaction Modes (30 min)
– Assign ART Roles and Confirm Next Steps (20 min)

Location/Link: [Meeting Link or Room]

Room and Technology Setup

Seating

Seat participants in mixed groups of business and technical leaders around tables that face a shared wall or screen. Avoid seating by department, which tends to reproduce the current org chart.

Visual Aids

Give each candidate ART its own lane on a wall or Miro board, with one sticky note or card per person. Moving people between teams should be physical and visible, not hidden in a spreadsheet.

Technology

Open the ART Organization Excel Template on a shared screen so team headcount, ART size checks, and dependency flags update as the design changes. Have the value stream map and architecture diagrams available to reference.

Virtual Setup

Use Microsoft Teams, Zoom, Google Meet, or Webex with screen sharing, plus a shared Miro board with editing access for all participants. Use breakout rooms for team design and test board access at least 15 minutes before the start.

04 / Facilitation

Running the Workshop

Run this as a design session, not a presentation. Every step moves the room from the value stream toward a concrete design: who is on each ART, which teams it contains, how those teams interact, and who fills each ART role. Keep the conversation anchored on the flow of value and park anything that needs leadership authority.

Purpose

Produce a draft ART and team design, organized around the flow of value, that leadership can review and approve.

Style

Hands-on and visual. Move people and teams on the board, test each design against the value stream, and let the worksheet flag size and dependency issues as you go.

Outcome

Clear ART boundaries, teams with a defined type and mission, a dependency map with interaction modes, named ART roles, and an owned list of open decisions.

Duration: Most ART Organization workshops for a single ART run about three and a half hours, including a break. Designing several ARTs in one value stream usually needs a full day. Protect time for the team design step; that is where most of the real trade-offs surface.

Presenting the ART Organization Process

Set the Stage: 15 minutes
- State the goal: a draft ART and team design organized around the flow of value, not a final org chart.
- Agree on working norms: design for flow first, then fit people; capture concerns rather than debating them.
- Confirm decision rights with the Executive Sponsor and introduce the Open Decisions log for anything the room cannot decide.
Confirm Value Stream and Solution Scope: 20 minutes
- Walk through the operational value stream and the development value stream that supports it.
- List the solutions, products, and systems in scope, and name what is explicitly out of scope.
- Record each candidate ART on the ART Boundary Check tab of the worksheet.
Inventory People and Skills: 30 minutes
- Review the People & Skills tab together and correct anything out of date.
- Flag people split across several teams or programs and note their current allocation.
- Identify scarce skills that several teams will need, since these often drive platform or enabling team decisions.
Define ART Boundaries: 30 minutes
- Group people and systems by the solution they help deliver, not by department or component.
- Check each candidate ART against the size range on the worksheet; SAFe describes ARTs as generally 50 to 125 people.
- If an ART is too large, split along value lines such as customer segment or product line. If it is too small, confirm scope or combine it with a related value stream.
Design Teams by Team Type: 45 minutes
- Start with stream-aligned teams that own a slice of value end to end, then add platform, complicated subsystem, and enabling teams only where they reduce load on stream-aligned teams.
- Keep teams to typically ten or fewer people, each with a clear mission and the systems it owns.
- Fill in the Team Design tab, including Product Owner and Scrum Master or Team Coach, and rebalance any team the Size Check flags.
Map Dependencies and Interaction Modes: 30 minutes
- List each remaining dependency in the Dependency Matrix: who needs what from whom, and how often.
- Assign one interaction mode to each: Collaboration, X-as-a-Service, or Facilitating.
- Treat any dependency flagged as crossing an ART boundary as a design signal, and adjust boundaries where one change removes several dependencies.
Assign ART Roles and Confirm Next Steps: 20 minutes
- Confirm the Release Train Engineer, Product Management, System Architect, and Business Owners for each ART.
- Read back the Open Decisions log and assign an owner and due date to every item.
- Set the date for the leadership review of the draft design before closing the session.

Common Anti-Patterns to Avoid

Redrawing the org chart and calling it an ART

If every ART lines up with an existing department, the design has not changed how value flows. Start from the value stream and let reporting lines follow, not lead.
Defaulting to component teams

Teams built around a single layer or system force most features to pass through several teams. Default to stream-aligned teams and add other team types only where they clearly reduce load.
Ignoring team cognitive load

A team asked to own too many systems or domains slows down no matter how skilled it is. If a team’s mission takes more than a sentence or two to explain, split or narrow it.
Deciding reporting lines in the room

Reporting-line debates stall design work and create anxiety. Capture them in the Open Decisions log for leadership and keep the room focused on the flow of value.
Launching with ART roles still open

An ART without a named Release Train Engineer, Product Management, and Business Owners will struggle in its first PI Planning event. Treat open roles as launch blockers, not follow-ups.

05 / Follow-Up

After the Workshop

An ART design only creates value once it is reviewed, decided, and communicated. The follow-up communication records the draft design, makes every open decision visible with an owner, and gives leadership and affected team members a single reference point before anything is announced more widely.

Expected Outputs

ART Design Summary
Team Roster by ART
Team Type Map
Dependency Matrix
Open Decisions Log

Share the completed worksheet and a one-page design summary with participants and Business Owners within 24 hours of the session. Keep the distribution to the workshop group and leadership until open decisions about reporting lines and staffing are closed, then communicate team assignments directly to every affected person before any wider announcement.

Follow-Up Communication Template

Subject: [Value Stream Name]: ART Organization Workshop: Draft Design and Open Decisions

Hi team,

Thank you for your work in today’s ART Organization Workshop. Below is a summary of the draft design and the decisions still open before we move into ART launch planning.

Proposed ARTs:
[ART name, development value stream, solutions delivered, and headcount for each ART]

Proposed Teams:
[Team name, team type, and mission for each team, grouped by ART]

Key Dependencies and Interaction Modes:
[Top dependencies, especially any that cross ART boundaries, with the agreed interaction mode and mitigation owner]

ART Roles:
[Release Train Engineer, Product Management, System Architect, and Business Owners for each ART; note any roles still open]

Open Decisions for Leadership:
[Decision, owner, and due date for each item]

The full worksheet is available at [Link to Shared Document or Miro Board]. Please keep this draft within the workshop group until leadership has reviewed it on [Review Date].

Thank you,
[Your Name]
[Title] | Stephens Insight Group

Ongoing Next Steps

Share the worksheet and a one-page design summary with participants and Business Owners within 24 hours of the session.
Hold the leadership review of the draft design and close each Open Decisions item by its due date.
Communicate team assignments directly to every affected person before any wider announcement.
Fill any open ART roles and confirm a Product Owner and Scrum Master or Team Coach for every team.
Use the approved design as the basis for ART launch planning, including the date of the first PI Planning event.
After the first Planning Interval, revisit ART boundaries, team types, and cross-team dependencies using what the teams learned, and adjust in small steps.

06 / References

References and Resources

Complimentary Workshops

Strategic Themes Workshop

Translate executive vision into investment priorities that cascade down to programs and teams.

Portfolio Kanban Workshop

Visualize epic flow, set WIP limits, and give leadership a shared view of where investment is moving.

Road Mapping Workshop

Connect strategic priorities to delivery timelines and show where work is headed and why.

Lean Business Case Workshop

Turn a promising epic into a testable, fundable hypothesis before the portfolio commits real money.

Ready to facilitate?

Download templates and tools to run your own ART Organization session.

Facilitator Presentation
ART Organization Excel Template