Facilitate program increment planning events that align multiple teams around shared objectives and a release cadence.
Information & Communications Technology
Release Train Coordination for Multi-Team Software Delivery
Coordinate agile release trains across multiple teams, from program increment planning to dependency management and synchronised production releases.
🗓️Duration5 training days
📚Content4 modules · 8 sessions
🎓On completionAccredited attendance certificate
About the programme
Course Overview
When several teams build components of the same product on independent sprint cycles, dependencies collide late, integration testing slips, and a release date becomes a guess rather than a plan. Coordinating an agile release train aligns those teams around a shared cadence, so dependencies surface during planning instead of during a failed deployment. This course teaches participants to run program increment planning events, map cross-team dependencies on a program board, and manage the release train engineer role that keeps the train moving when a team falls behind. Participants practise facilitating a Scrum of Scrums, sequencing programme-level features into a shared backlog, and negotiating scope trade-offs when a dependency risk threatens the increment's objectives. Sessions also cover architectural runway planning, managing shared components across teams without a big-bang rewrite, and coordinating a synchronised production release across services owned by different teams. Case-based exercises simulate a train with a blocked dependency discovered mid-increment, requiring participants to resequence work, communicate the change to stakeholders and protect the increment's committed objectives. By the end, participants can plan, run and troubleshoot a multi-team release train from increment planning through to a coordinated release.
Expected Learning Outcomes
Map cross-team dependencies on a program board and sequence features to avoid late-stage integration surprises.
Run a Scrum of Scrums that surfaces blockers early and keeps the release train informed without duplicating team stand-ups.
Manage architectural runway work so shared components support planned features without unplanned rework.
Negotiate scope and sequencing trade-offs when a dependency risk threatens a committed increment objective.
Coordinate a synchronised production release across services owned by independent teams.
Report train-level progress, risk and predictability metrics to stakeholders without teams losing planning autonomy.
Who Should Attend
Release train engineers and programme managers coordinating multiple agile teams.
Scrum masters who need to represent their team's dependencies at programme level.
Product managers sequencing features that span more than one delivery team.
Engineering leads responsible for shared components used across several teams.
Agile coaches introducing release train practices into a multi-team organisation.
Delivery managers accountable for coordinated production release dates.
Course Modules
Select any module to see its sessions and points.
01Planning the Program Increment
2 sessions · 8 points
Session 1Preparing for Program Increment Planning
- Prepare a programme backlog of features sized and prioritised for the upcoming program increment planning event.
- Brief team representatives on draft objectives and known dependencies before the planning event begins.
- Assess architectural runway readiness to confirm shared components can support the features being planned.
- Identify capacity constraints across teams, including planned leave and shared specialist resources.
Session 2Running the Planning Event and Program Board
- Facilitate breakout sessions where each team drafts its increment plan against the shared feature set.
- Build a program board that visualises cross-team dependencies, milestones and feature delivery sequencing.
- Surface dependency conflicts during the planning event and resequence work before commitments are finalised.
- Capture team confidence votes and committed versus stretch objectives for the increment.
02Coordinating Delivery Across Teams
2 sessions · 8 points
Session 1Running the Scrum of Scrums
- Facilitate a Scrum of Scrums that focuses on cross-team blockers and dependency status rather than task-level detail.
- Track dependency resolution against the program board and escalate items at risk of missing the increment.
- Coordinate shared component changes so consuming teams are notified before an interface changes.
- Maintain a risk log for the release train and review it at each Scrum of Scrums.
Session 2Managing Scope and Sequencing Changes
- Renegotiate feature scope with product management when a dependency risk threatens committed objectives.
- Resequence features across teams to protect the increment's highest-priority objectives when capacity shifts.
- Communicate scope or sequencing changes to stakeholders with the reasoning and revised delivery impact.
- Distinguish decisions the release train engineer can make directly from those requiring stakeholder sign-off.
03Architectural Runway and Shared Components
2 sessions · 8 points
Session 1Planning the Architectural Runway
- Plan architectural runway work ahead of feature delivery so shared platforms are ready when teams need them.
- Balance investment between architectural runway, technical debt reduction and new feature delivery within capacity.
- Coordinate changes to shared libraries or platforms across teams to avoid breaking dependent services.
- Review architectural decisions with affected teams before they are locked into the increment plan.
Session 2Managing Shared Component Ownership
- Define ownership and change approval processes for components used by more than one team.
- Version shared interfaces so consuming teams can migrate on their own schedule without blocking the train.
- Run integration testing for shared components ahead of team-level feature testing to surface conflicts early.
- Track technical debt in shared components that could constrain future increments if left unaddressed.
04Delivering and Reviewing the Increment
2 sessions · 8 points
Session 1Coordinating the Synchronised Release
- Plan a synchronised release sequence across services owned by different teams to minimise integration risk.
- Coordinate release rehearsals and rollback plans across teams before a combined production deployment.
- Align release communication with support, operations and customer-facing teams ahead of the deployment window.
- Manage a release day command structure that gives each team a clear escalation path if an issue appears.
Session 2Inspecting and Adapting the Train
- Run an increment system demo that shows integrated, working features across all participating teams.
- Facilitate an inspect and adapt workshop that reviews predictability metrics and quality trends across the train.
- Report train-level velocity, predictability and dependency resolution metrics to programme stakeholders.
- Capture retrospective actions that improve dependency visibility and planning accuracy for the next increment.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.