# Agile Transformation: Why Programs Stall After Two Years

Author: Marin Niehues, Niehues Consulting · Published: 2025-04-10 · Updated: 2026-11-16 · Transformation & Change
Source: https://www.niehuesconsulting.com/blog/agile-transformation-why-programmes-stall/

Agile transformations stall once the roll-out beyond the pilot teams meets annual budgets, committee approvals and functional targets, usually between the first and third year. Pilot teams show impact quickly, yet the steering of the organization stays in the old model, and in the end the program mostly administers itself. This article describes the five points of failure, a diagnostic grid for the executive team, guide values for duration and cost, and an approach that makes the delivery capability of the organization the yardstick.

**An agile transformation comes to a standstill where teams have changed how they work while the steering of the organization has stayed the same. Delivery capability only rises when budgets and decision rights, as well as metrics, follow suit.**

The article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/) covers structure, decision paths and delivery metrics as a whole.

## What is an agile transformation?

An agile transformation is the redesign of an organization in which, beyond the way teams work, budgeting and decision rights as well as leadership are switched to short cycles and fast feedback. That is the difference from agile working within a team. A team using Scrum or Kanban changes its own routines: planning in short iterations, visible work, regular retrospectives. A transformation changes the rules under which all teams work, meaning the flow of money and the decision paths as well as the yardsticks for managers.

The distinction matters in practice for the executive team. Agile teams can be launched within a few weeks. Switching budgets and decision rights requires decisions that only the executive team can take, and that is exactly where it is decided whether a program keeps moving.

## The typical pattern

The course usually follows three phases. In the first phase individual teams start with new roles and rituals, supported by coaches. Results are visible, morale is good, and the executive team approves the roll-out. In the second phase the program grows into further areas and meets processes built for a different working model there: annual project budgets, approvals by committees, target agreements per function. In the third phase the teams lose pace. The program then reports on the number of teams and training sessions, while the lead time of orders stays unchanged. In larger organizations a program usually reaches this third phase between the first and third year.

The trigger rarely lies in the method. Scrum and Kanban as well as the scaled frameworks work where the organization around them is adapted. SAFe even brings a budget model per value stream with Lean Portfolio Management. It only takes effect once finance and the executive team actually switch annual planning over to it. No framework takes that decision for you. The article [Scaled agile frameworks compared](/blog/scaled-agile-frameworks-comparison/) offers a comparison of the frameworks.

## Why do agile transformations fail?

Agile transformations fail on the steering of the organization, at one or more of five points of failure:

- Budget logic: annual budgets per project clash with teams that reprioritise continuously. As long as every change triggers a budget request, prioritization remains flexible only on paper.
- Decision rights: teams are meant to decide, but approvals still sit with committees. Every decision on the critical path that the team may not take itself extends the lead time by the wait until the next committee date.
- Role of middle management: second-line managers lose their previous task, the allocation of work, and receive no new one. Their silent resistance is then rational.
- Metrics: the program measures activity, such as the number of agile teams, instead of delivery such as lead time or schedule reliability.
- Ownership of the program: the transformation runs as a side task without a mandate or its own budget, and without access to the line.

The fourth and fifth points of failure mask the others. Without delivery metrics it stays invisible that the first three points are slowing things down, and without a mandate the program lacks the authority to change them.

**Two program logics compared**
Criterion | Method program | Delivery program | With Niehues Consulting
Starting point | Introduction of roles and rituals | Bottlenecks in delivery | Analysis of the delivery chain with a bottleneck map before the first team
Budget | Annual project budget | Budget per value stream | Transition from project to product budget in stages
Measurement | Number of teams and training sessions | Lead time and schedule reliability | Metric set that measures delivery, with a baseline before the start
Ownership | Agile coaches | Line management with a mandate | Delivery manager with decision mandate as a bridge to the line

## Diagnostic grid: how to recognize standstill

Standstill shows up in delivery before it reaches the mood survey. The executive team can detect it early with a few questions.

**Five questions for the program**
Has the lead time of a typical order shortened compared with the start?
How many decisions are waiting for a committee date even though a team could take them?
Is budget being shifted between initiatives this year without a new request?
Can every second-line manager name their new task in one sentence?
Does the program have a mandate to change the rules of the line?

If the answer is no several times, the problem lies in the steering of the organization. More training and additional teams change little, as they enlarge the part of the organization working against the same rules.

A distinction by cause helps with the evaluation. If delivery metrics are missing, the work starts with measurement: without a baseline no progress can be proven and no stage approved. If the mandate is missing, the first step lies with the executive team itself, which must transfer decision rights over the rules of the line to the program. If the cause lies in middle management, every second-line manager needs a new, verifiable task, such as responsibility for the lead time of a value stream. The sequence of measures follows the point of failure with the longest waiting time in the delivery chain, because that is where the gain in pace becomes visible fastest.

## An approach that keeps programs moving

The alternative to a broad roll-out is the stage with proof of delivery. First, a diagnosis establishes where orders actually wait. Then a single value stream unit is rebuilt completely: teams and budget together with decision rights and metrics. Only when this unit delivers measurably faster does the next one follow. The budget is switched step by step from the project to the value stream.

This approach also changes reporting. For each stage, the executive team sees how lead time and schedule reliability develop and can decide whether to approve the roll-out. The program thus gains a yardstick that goes beyond the number of teams.

Guide values from practice apply to duration. A division with a few hundred employees needs twelve to 24 months to reach a stable operating model. A group plans several years in waves, with each wave starting with a value stream unit of three to six months.

## What does an agile transformation cost?

The cost of an agile transformation consists mostly of external support and internal working time and can be calculated from the number of support days per stage. External consulting in the German market is billed at around 1,000 to 2,500 euros per consultant day, depending on seniority. Training and tools come on top, as does the time that managers and teams invest in redesign and coordination. The largest hidden item is the transition period in which old and new routines run in parallel.

**Calculation: external support for one stage**
Assumption: one value stream unit with five teams, supported by two external specialists on three days per week each over six months (around 26 weeks).

Support days: 2 × 3 × 26 = 156 days
External cost: 156 × 1,000 euros = 156,000 euros up to 156 × 2,500 euros = 390,000 euros

Test question: what reduction in lead time must the stage show for this sum to pay off? The executive team sets this target before the start.

A broad roll-out multiplies this calculation by the number of units, without any proof of delivery securing the expansion. The stage with proof of delivery limits the risk, because every further investment is tied to a measured effect.

## Niehues Consulting as a partner for transformations that deliver

[Niehues Consulting](/) supports agile transformations with a focus on delivery. In delivery management and organization design, Niehues Consulting steers initiatives as delivery manager or product owner and designs structures and roles as well as decision paths, so that the organization delivers reliably in day-to-day business and in the transformation alike.

The approach follows the Niehues Delivery Model with the phases Understand, Build and Introduce. In the Understand phase, the diagnosis of bottlenecks is guided by the test question of what the baseline is and how success is measured. In the Build phase a first unit is rebuilt with proof of delivery, guided by the question of which roles and decision paths operations need and what the interfaces look like. In the Introduce phase the roll-out follows with processes and responsibilities, together with the enablement of those involved. After 90 days the lead time shows whether the solution is landing.

Founder Marin Niehues comes from the delivery perspective. He builds organizations that deliver, in projects ranging from VC-funded scale-ups to DAX 40 groups, with assignments in 20+ countries on six continents. The entry point is a free initial consultation of 30 minutes, which you can [request here](/#kontakt).

**Recommendation for the executive team**
Test the running program against lead time. If budgets and decision rights are unchanged, start the next stage where orders demonstrably wait, and approve the roll-out only after measurable proof of delivery.

**Sources**
- Bundesverband Deutscher Unternehmensberatungen (BDU): Honorare in der Unternehmensberatung, fee study 2022

## Frequently asked questions

### What is an agile transformation?

An agile transformation is the redesign of an organization in which, beyond the teams, budgeting and decision rights as well as leadership are switched to short cycles. It therefore goes beyond introducing Scrum or Kanban. It is measured by the delivery capability of the organization.

### Why do agile transformations fail?

Agile transformations fail on the steering of the organization. Teams change how they work, while budgeting and decision rights as well as metrics from the old model remain in place. As a result, the teams hit limits that they cannot change themselves.

### How long does an agile transformation take?

A division with a few hundred employees needs twelve to 24 months to reach a stable operating model, and a group several years in waves. Stages of three to six months, each with proof of delivery, work best. After each stage the executive team decides whether to continue.

### How much does an agile transformation cost?

The cost arises mainly from days of external support and internal working time. At day rates of around 1,000 to 2,500 euros, external support for a stage with five teams over six months costs roughly 156,000 to 390,000 euros. Training and tools come on top, as does the cost of the transition period.

### What is the difference between an agile transformation and agile working in a team?

Agile working changes the routines of a team, while an agile transformation changes the rules of the entire organization. A team can start with Scrum within a few weeks. Switching budgets and decision rights requires decisions by the executive team.

### How can I tell that my program is stagnating?

A program is stagnating when lead time stays unchanged despite a growing number of teams and decisions wait for committee dates. Second-line managers without a new task are another sign. The diagnostic grid above condenses this check into five questions.

### Do we need a scaled framework such as SAFe?

A scaled framework such as SAFe makes sense when several teams work on a shared product with tight dependencies. With Lean Portfolio Management, SAFe contains a budget model per value stream that only takes effect once finance and the executive team switch annual planning over to it. The choice follows the delivery situation of the organization.
