Agile and Change: Making Delivery Stick

Agile delivery is often praised for adaptability, rapid feedback, and continuous improvement. Teams release value earlier, learn faster, and evolve solutions as they go. But as we explored in the recent Wellingtone community masterclass, early delivery can create an illusion that change has already taken hold. A user story is complete, a feature is live, or a new way of working is launched, and assumptions quickly follow that adoption is done.

The truth is very different.

Agile enables change to be delivered sooner, but early release does not guarantee that people understand it, accept it, or integrate it into their daily habits. Many organisations celebrate too soon. Behaviours often remain unchanged, teams drift back to familiar routines, and the benefits promised in the business case begin to fade away.

This is why managing change after delivery is essential within an agile environment. Agile does not remove adoption challenges. It simply reveals them earlier. The real work begins after something goes live, not before.

Why Change Does Not End at Delivery

In traditional delivery models, the end of a project feels like the finish line. Agile disrupts that mindset. Because value is released incrementally, stakeholders experience change earlier in the lifecycle, which introduces its own complexities.

Premature celebration

A feature goes live and is treated as a success long before users have been trained or supported.

Change fatigue

Frequent updates without clear messaging may overwhelm people rather than empower them.

Lack of reinforcement

After each sprint, teams turn their attention to the next set of tasks. Without reinforcement, new ways of working receive little support and people naturally revert to the old way.

Wellingtone’s guide Change Management: Everything You Need to Know explains that reinforcement is a formal stage of change and not a nice to have. It is the part that prevents regression and helps new habits form.

Reinforcement is the mechanism that turns delivered outputs into adopted outcomes.

Understanding Resistance After Delivery

One of the richest conversations in the masterclass focused on resistance. Most organisations expect resistance to be loud and visible, yet most of it is quiet and subtle. The article Change Management Roles and Responsibilities highlights that resistance often grows because no one is formally accountable for sustaining the change once delivery is complete:

Resistance may show up as:

• Ignoring the change and continuing with old processes
• Appearing supportive while secretly reverting
• Openly challenging the value or purpose of the change

Agile brings these behaviours to the surface early because progress is visible early. This gives change leads and delivery teams the chance to understand what people need and how ready they are to make the shift.

Importantly, resistance is not personal. It is a natural human response to uncertainty, loss of control, or fear of failure. Recognising resistance early helps prevent small concerns from becoming major blockers.

The Change Curve Still Applies

The Kubler Ross Change Curve remains fully relevant in agile environments. Agile may change the pace of delivery, but it does not change how people emotionally process transition. Participants in the masterclass matched real statements to phases of the curve, reinforcing that familiar reactions such as denial, frustration, bargaining, and acceptance are universal.

The Wellingtone article The Four Elements of Change Management reinforces this idea. Transition requires people to let go of the current state, understand the future state, travel through the bridge between them, and receive reinforcement to stay there.

People adopting a change experience this curve at their own pace. Delivery teams are usually further along the curve than those impacted by the change, which naturally creates a gap in perception.

Understanding this difference helps teams provide the right type of support, whether reassurance, clarity, or time.

Using ADKAR to Sustain Change

The ADKAR model is one of the most effective ways to structure adoption. While many teams invest heavily in Awareness, Desire, Knowledge, and Ability, it is Reinforcement that makes the change stick. Without reinforcement, people quietly return to previous habits.

Real examples shared during the masterclass showed that reinforcement is not a single activity but an ongoing approach. This includes pulse checks, targeted coaching, updates, social proof, and visible leadership involvement.

The themes align with the Wellingtone blog The Role of a Change Leader, which emphasises the importance of a change lead or change champion guiding people through the entire journey, not just the go live moment:

Reinforcement gives people the confidence and competence to continue using the new way of working.

Practical Reinforcement Ideas

Behavioural nudges

Subtle prompts, reminders, and social proof that reinforce new norms.

Gamification

Adding creativity and fun to build energy around adoption.

Visible leadership support

People adopt faster when they see leaders reinforcing the why behind the change.

Celebrating small wins

Recognising progress maintains momentum and confidence.

Agile Specific Reinforcement Strategies

Agile and change management blend naturally when used intentionally. The masterclass explored several practical approaches.

1. Use retrospectives to reinforce behaviours

Retrospectives can examine adoption, comfort, and behaviours, not only delivery output.

2. Track behavioural metrics

Metrics such as tool usage or ceremony attendance help teams understand adoption more accurately than velocity alone.

3. Add reinforcement activities to the backlog

If adoption matters, it should be visible in sprint planning and prioritisation.

4. Start reinforcement early

Agile surfaces resistance quickly, so support should begin as soon as a change is introduced.

Culture: The Hidden Enabler of Successful Agile Change

A powerful insight from the Wellingtone article Organisational Culture and Change is that change will only succeed if it aligns with the cultural norms of the organisation.

Culture determines how people respond to change, how quickly they embrace new behaviours, and whether they feel empowered or threatened by change.

Even well delivered agile work will struggle in a culture that rewards predictability, hierarchy, or control. In contrast, a culture that values openness, learning, and collaboration will support agile adoption naturally.

This is why reinforcement must always be tailored to the culture it serves.

Final Thoughts

Agile accelerates delivery, but sustainable change requires ongoing reinforcement. A feature going live does not mean that people understand it or trust it, and it certainly does not mean they have made it part of their daily habits.

Reinforcement is what turns delivery into adoption. It is the final step that allows people to feel confident, supported, and capable in the new way of working.

Organisations that invest in reinforcement see their agile transformations take root. Those that do not often return to old habits and wonder why the benefits never appeared.

APM Endorsed Assurance Practitioner Training Course

Ready to strengthen how your organisation delivers projects? This course gives you practical skills, proven techniques, and the confidence to apply effective assurance straight away. As the only Endorsed course of its kind, it’s a powerful way to build capability and boost real delivery confidence. Explore the course and take the next step in your assurance journey.

APM Endorsed Change Management Practitioner Training Course