The first six months of an agile transformation are usually the easy part. There is a kickoff, a round of training, a few teams producing working software every two weeks, and a sponsor who likes the energy. Then the energy fades. Teams go through the motions, and the old way of working quietly returns.
We see the same stall patterns again and again. Most are organizational, not technical, which is why they’re easy to miss from inside a team.
Why transformations stall
Middle management is left out. Training reaches teams and executives, but the managers between them are asked to “empower” teams without being told what their own job becomes. When their role is unclear, they fill the gap with status meetings and approval steps.
Funding stays annual. Teams work in iterations, but budgets are still approved per project once a year, with fixed scope attached. The team learns something in March that changes the plan, and the budget process can’t absorb it.
Coaching ends when the contract does. Coaches show teams new habits. If the engagement ends before those habits are routine, no one inside the company is left to keep them going, and teams drift back.
Certification is mistaken for capability. A room of newly certified people is a good start. But training isn’t transformation. Knowing the vocabulary of Scrum doesn’t mean a team can slice work thinly, say no to a stakeholder, or fix a broken build before lunch.
Agile teams sit inside a waterfall organization. The teams iterate, but requirements still arrive as a thick document, testing happens in a separate phase, and release depends on a quarterly window. The team moves fast and then waits.
How to restart momentum
Consider a bank where six teams adopted Scrum, yet releases still happen twice a year because of a shared change board. Pushing the teams to work harder won’t help. Fixing the constraint will.
- Find the real constraint. Trace one request from idea to production and mark every wait. The longest wait is your next project.
- Bring middle managers in. Give them a clear role, such as removing impediments, growing people, and managing the flow of work, and involve them in the next phase of planning.
- Change one funding rule. Try funding a stable team or product for a longer period in place of a one-off project, and see what happens.
- Build internal coaches. Pair outside coaches with people inside, and agree early on the handover date.
- Judge by results. Review lead time, quality, and feedback, not course completions.
A stall isn’t a failure. It’s usually the point where the easy changes run out and the structural ones begin. Pick one obstacle, and fix it visibly. If you’d like an outside view of where yours is, we’re happy to take a look.