Why Agile Transformations Still Struggle

Many organisations introduce Agile teams, adopt Scrum or Kanban, and invest heavily in transformation programmes. Yet despite the new roles, ceremonies, and terminology, progress often feels slower than expected.

In this episode of The Deep Dive, we explore why Agile transformations still struggle to deliver the value they promise.

Drawing on insights from the books of Matthew Coxall, the conversation looks beyond team practices to examine the deeper organisational structures that shape how work really happens.

We discuss how many organisations adopt the vocabulary of Agile while still operating with project-era assumptions around funding, governance, and decision-making. These structural patterns create friction that no amount of stand-ups, retrospectives, or backlog refinement can resolve.

Topics explored in this episode include:

• The hidden impact of project logic in modern digital organisations
• Why funding models often reinforce delivery against scope rather than learning
• The reality of conditional autonomy inside Agile teams
• How governance layers create decision latency
• Why many Agile transformations stall despite genuine effort from teams

The episode concludes by introducing the concept of Product Agile Harmony, where Product, Engineering, Design, and Business operate as a connected system rather than separate functions.

Agile transformation is not simply a delivery change. It is a structural shift in how organisations learn, make decisions, and invest in digital products.

Podcast Format
 A reflective conversation exploring organisational design, leadership dynamics, and product thinking in modern digital organisations.

Source Material
 Insights drawn from books by Matthew Coxall including:

Product Agile Harmony (WIP)
 Agile How To Succeed as a Product Owner
 How to Navigate the Agile Journey as a Scrum Master
 How to Lead in Agile as an Engineering Leader