Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

A maturity path is a practical explanation of the ever-ongoing change journey an organizational unit is willing to undertake. The purpose is not for anyone to approve or judge the organizational unit, it is a tool for themselves to enable planning and get support to take the next step. It is also important to make the future path visible.

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

Benefit

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

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.

Benefit

The organisation understands their path forward.

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

Benefit

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

Metrics

  • Train happiness index

  • Predictability measurement on Business value

Benefit

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

Metrics

  • Velocity in Mother Feature Points / Program Increment

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

  • Aggregated PI Objectives

Benefit

The Solution 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 Solution Train is able to show and feel they are in control.

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.

Benefit

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

Process

  • Solution demo after each Program Increment

Benefit

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

The Agile Release Trains learn what is required to finalize deliveries together.

Process

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

  • Collective ownership for the program backlog.

Benefit

All Agile Release Trains has a stable learning process which is based on real value delivery.

Product backlog

  • Sequenced Solution Epics

  • Epic hypothesis statement

  • No activities as backlog items.

Benefit

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

Product backlog

  • Sequenced Mother Features

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

  • Reference Mother Feature

Benefit

The Solution 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.

  • Agile Solution Train improvement enablers

Benefit

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

Big visible radiators

  • Solution Kanban with WIP-limit on all phases

  • Solution Planning board updated during PI-execution

Benefit

Agile Release Trains and stakeholders have a common understanding of the objectives and the plan to reach them.

Big visible radiators

  • Solution intent

  • Cumulative Flow Diagram

Benefit

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

Big visible radiators

  • Solution Road map

Benefit

Full overall visibility and control over queues.



Businessman-ship

  • Continuous Exploration with end customers

Benefit

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

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

Benefit

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

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.

Benefit

The organisation understands their path forward.

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

Benefit

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

Metrics

  • Train happiness index

  • Predictability measurement on Business value

Benefit

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

Metrics

  • Velocity in Mother Feature Points / Program Increment

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

  • Aggregated PI Objectives

Benefit

The Solution 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 Solution Train is able to show and feel they are in control.

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.

Benefit

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

Process

  • Solution demo after each Program Increment

Benefit

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

The Agile Release Trains learn what is required to finalize deliveries together.

Process

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

  • Collective ownership for the program backlog.

Benefit

All Agile Release Trains has a stable learning process which is based on real value delivery.

Product backlog

  • Sequenced Solution Epics

  • Epic hypothesis statement

  • No activities as backlog items.

Benefit

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

Product backlog

  • Sequenced Mother Features

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

  • Reference Mother Feature

Benefit

The Solution 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.

  • Agile Solution Train improvement enablers

Benefit

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

Big visible radiators

  • Solution Kanban with WIP-limit on all phases

  • Solution Planning board updated during PI-execution

Benefit

Agile Release Trains and stakeholders have a common understanding of the objectives and the plan to reach them.

Big visible radiators

  • Solution intent

  • Cumulative Flow Diagram

Benefit

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

Big visible radiators

  • Solution Road map

Benefit

Full overall visibility and control over queues.



Businessman-ship

  • Continuous Exploration with end customers

Benefit

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

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

Benefit

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

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.

Benefit

The organisation understands their path forward.

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

Benefit

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

Metrics

  • Train happiness index

  • Predictability measurement on Business value

Benefit

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

Metrics

  • Velocity in Mother Feature Points / Program Increment

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

  • Aggregated PI Objectives

Benefit

The Solution 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 Solution Train is able to show and feel they are in control.

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.

Benefit

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

Process

  • Solution demo after each Program Increment

Benefit

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

The Agile Release Trains learn what is required to finalize deliveries together.

Process

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

  • Collective ownership for the program backlog.

Benefit

All Agile Release Trains has a stable learning process which is based on real value delivery.

Product backlog

  • Sequenced Solution Epics

  • Epic hypothesis statement

  • No activities as backlog items.

Benefit

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

Product backlog

  • Sequenced Mother Features

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

  • Reference Mother Feature

Benefit

The Solution 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.

  • Agile Solution Train improvement enablers

Benefit

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

Big visible radiators

  • Solution Kanban with WIP-limit on all phases

  • Solution Planning board updated during PI-execution

Benefit

Agile Release Trains and stakeholders have a common understanding of the objectives and the plan to reach them.

Big visible radiators

  • Solution intent

  • Cumulative Flow Diagram

Benefit

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

Big visible radiators

  • Solution Road map

Benefit

Full overall visibility and control over queues.



Businessman-ship

  • Continuous Exploration with end customers

Benefit

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

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.