Matt Breon

Case study • Enterprise delivery

Enterprise Email Platform Migration

Turning six teams into one coordinated release train.

Coordinated delivery for a cloud migration supporting a platform processing more than 1.2 billion emails every month.

Release Train EngineerSix Teams1.2B+ Emails / Month
A planning wall with six swim lanes, pinned notes, and dependency threads that connect work across lanes.

My evolution

  1. Senior IT Project Manager
  2. Joined the Agile PMO
  3. Certified Scrum Master
  4. Release Train Engineer

As the organization adopted SAFe, my responsibilities expanded from leading a single team to coordinating planning and delivery across the Agile Release Train.

The challenge

Six teams couldn't plan independently if they were expected to deliver together.

PI Planning created alignment. Weekly Scrum of Scrums sustained it. My role was turning dozens of cross-team dependencies into one coordinated execution plan.

  1. 01

    Cross-Team Dependencies

    Features often depended on work being completed across multiple teams before delivery could move forward.

  2. 02

    PI Planning

    Every Program Increment required coordinated planning, sequencing, and commitment across the Release Train.

  3. 03

    Continuous Alignment

    Weekly Scrum of Scrums surfaced blockers, resolved dependencies, and kept delivery on track throughout execution.

What I owned

Creating shared visibility across the release train.

01

PI Planning

Prepared and facilitated Program Increment planning events.

02

Scrum of Scrums

Maintained weekly alignment across teams while surfacing blockers and dependencies.

03

Release Coordination

Managed sequencing across multiple teams.

04

Dependency Management

Identified, tracked, and resolved cross-team dependencies.

05

Program Visibility

Translated planning outputs into executable Jira plans.

06

Stakeholder Communication

Maintained shared visibility across leadership and delivery teams.

From planning to execution

Planning created the starting point. Alignment kept work moving.

Planning was not the end goal. Alignment throughout execution kept six teams moving together.

  1. 01

    Planning Inputs

    Requirements, priorities, team objectives

  2. 02

    PI Planning

    Shared objectives and commitments

  3. 03

    Integrated Release Plan

    Cross-team sequencing and dependencies

  4. 04

    Executable Roadmap

    Coordinated delivery plan

  5. 05

    Weekly Execution

    Scrum of Scrums and ongoing coordination

Turning six plans into one delivery plan

Independent planning. Coordinated execution.

Six independent planning lanes with connected work converge into one integrated release plan, resulting in resolved dependencies, shared priorities, and predictable delivery.

Independent planning lanes

Integrated release plan

Shared sequencing, dependencies, and priorities

Resolved Dependencies

Cross-team conflicts identified before execution

Shared Priorities

Every team worked toward the same increment goals

Predictable Delivery

One coordinated roadmap replaced six disconnected plans

The real deliverable

A shared operating rhythm for enterprise delivery.

01

Program Alignment

Created a planning model that kept six teams moving toward the same objectives.

02

Systems Thinking

Turned complex dependencies into an executable delivery plan.

03

Predictable Execution

Built visibility and coordination that reduced uncertainty throughout the migration.

“The migration was the initiative. Building a repeatable planning and coordination system that kept six teams aligned was the lasting result.”
← Back to Home