Solution Train maturity path

Cope level

Startup level

Delivery engine (Mature agile at large scale)

Organisation

• One Solution Train Engineer at least 50%

• One Solution Manager at least 50%

• One Solution Architect at least 50%

• No doubt about which Agile Release Trains are part of the Solution Train

• No doubt about who is part of Solution Management

Organisation

• One Solution Train Engineer at least 100%

• One Solution Manager at least 100%

• One Solution Architect at least 100%

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

• Established vertical work groups for Solution Train Engineer - Chief scrum masters, Solution Manager - Chief Product Owners and Solution Architect - System Architects.

Organisation

• STE, SM and SA have full operational responsibility for the product backlog and the delivery

• The Agile Solution Train owns their value stream.

• Line management owns the strategic organisational design

Metrics

• Train happiness index

• Predictability measurement on Business value

Metrics

• Velocity in Mother Feature Points / Program Increment

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

• Aggregated PI Objectives

Metrics

• Average lead time

• Actual WIP

• Size of Product backlog items

• SMART PI-Objectives with outcome

Process

• Pre- and Post-PI planning

• Regular Backlog refinement

• All Agile Release Trains have the same cadence

• Chief Scrum-sync every week, max 30 minute meeting

• CPO-sync every week, max 60 minute meeting

• Inspect and Adapt event at the end of each PI

• Policy for what is handled in by Solution Management and by in each Product Management.

Process

• Solution demo after each Program Increment

Process

• The Agile Solution Train is able to finalize Mother Features and enablers within each Program Increment.

• Collective ownership for the program backlog.

Product backlog

• Sequenced Solution Epics

• Epic hypothesis statement

• No activities as backlog items.

Product backlog

• Sequenced Capabilities

• Mother Feature points, estimated by the system architects, on all Mother Features in the Solution backlog

• Reference Capabilities

Product backlog

• Business outcome defined for all backlog items.

• Balance between features and enablers based on business benefits.

• Agile Solution Train improvement enablers

Big visible radiators

• Solution Kanban with WIP-limit on all phases

• Solution Planning board updated during PI-execution

Big visible radiators

• Solution intent

• Cumulative Flow Diagram

Big visible radiators

• Solution Road map

Businessman-ship

• Continuous Exploration with end customers