Release Train maturity path

Owned by Mats Janemalm
Last updated: 2019-04-01
3 min read

Cope level

Startup level

Delivery engine (Mature Agile at scale)

Organisation

  • One RTE at 100%

  • One Product Manager at 100%

  • One System Architect at 100%

  • No doubt about which teams are in the train

  • No doubt about who is part of Product Management

  • Between 20 and 125 individuals

Benefit

The organisation can start to prepare for the first and succeeding Program Increments.

Organisation

  • At least one Community of Practice

  • No doubt about who is or are the line manager(s) for the Agile Release Train

  • All dependencies of the value stream have been identified, and are known by line manager(s).

  • Established vertical work groups for RTE - Scrum masters, Product Manager - Agile Product Owners and System Architect - Developers.

Benefit

The organisation understands their path forward.

Organisation

  • RTE, PM and SA have full operational responsibility for the product backlog and the delivery

  • The Agile Release Train owns their value stream.

  • Line management owns the strategic organisational design

  • Several Community of Practices covering the need of the train and sponsored by line management

Benefit

The Agile Release Train gets content authority for the program backlog and can improve on a regular base.

Metrics

  • Velocity for the amount of Features delivered in one PI

  • Train happiness index

  • Predictability measurement on Business value

Benefit

The Product Management can start to understand how much can be accomplished in one Program Increment. The RTE can start taking actions to increase performance of the Agile Release Train.

Metrics

  • Velocity in Feature Points / Program Increment

  • Always up to date remaining planned Feature points in current PI

Benefit

The Product Management are able to prioritize based on predictable estimates.

Metrics

  • Average lead time

  • Actual WIP

  • Size of Product backlog items

  • SMART PI-Objectives with outcome

Benefit

The Agile Release Train is able to show and feel they are in control.

Process

  • Program Increment (PI) in 8 to 12 weeks

  • Regular Backlog refinement

  • PI-Planning, 2 days

  • Scrum of Scrums every week, max 30 minute meeting

  • PO-sync every week, max 60 minute meeting

  • Innovation & Planning sprint

  • Inspect and Adapt event at the end of each PI

Benefit

The Agile Release Trains get a habit of delivering value and improving together, in cadence and synchronized.

Process

  • System demo after each iteration or equivalent period

Benefit

The Agile Release Train can navigate based on feedback. Stakeholders are involved in valuable and short feedback loops.

Teams learn what is required to finalize deliveries together.

Process

  • The Agile Release Train working mission aligned in all teams

  • The Agile Release Train is able to finalize features and enablers within each Program Increment.

  • Collective ownership for the program backlog.

Benefit

All teams has a stable learning process which is based on real value delivery.

Product backlog

  • Sequenced estimated features for PI planning

  • Features estimated by the developers, on all features and enablers in the program backlog

  • Feature and Enabler Done checklist

Benefit

Transparency of what the Agile Release Train needs to deliver and when it can be done.

Product backlog

  • Agile Release Train improvement enablers

  • Program Epics

  • Feature points, estimated by the developers, on all features in the program backlog

  • Reference Feature

  • No activities as backlog items.

Benefit

The Product Management are able to prioritize based on Business value.

Product backlog

  • Business outcome defined for all backlog items.

  • Balance between features and enablers based on business benefits.

Benefit

The Agile Release Train understand and have focus on end user-business need.

Big visible radiators

  • Program board updated during PI-planning and PI-execution

  • ROAMed program risk board and PI-objectives during PI-planning

Benefit

Teams and stakeholders have a common understanding of the objectives and the plan to reach them.

Big visible radiators

  • Feature point burn down

  • Program Kanban with WIP-limit on all phases

Benefit

The Agile Release Train can start manage their queue in alignment with stakeholder need.

Big visible radiators

  • Cumulative Flow Diagram

  • PI Roadmap

Benefit

Full overall visibility and control over queues planning horizon.

 

 

Businessman-ship

  • Continuous Exploration with end customers

Benefit

Ability to find the balance between investments in current business and future business.

All material on this site is published in accordance with Konomark.