The case for Agile training is reasonably well understood. Teams learn the terminology, the frameworks, the values and principles. They come back from the training with a shared vocabulary and a basic understanding of the practices. And then, in a significant proportion of cases, the gap between what they learned and what they actually do at work remains stubbornly wide.

This is not a failure of the training. It is a predictable consequence of relying on training alone.

Why training alone is not enough

Training provides theoretical knowledge in a context removed from the team's actual work. The examples used are necessarily generic. The challenges explored are necessarily simplified. The practices demonstrated exist in a training environment where the political dynamics, the legacy systems, the existing habits, and the specific pressures of real work are all absent.

When participants return to their actual work, they face a translation problem. The framework makes sense in principle. Applying it to this backlog, this stakeholder, this team, these constraints — that is a different and harder task. Without support for that translation, theoretical understanding tends to remain theoretical.

Why coaching alone is not enough either

The inverse problem also exists. Teams that receive agile coaching without prior training often lack the conceptual foundation to understand why they are being asked to change how they work. A coach facilitating a retrospective with a team that does not understand what a retrospective is for will face resistance — not because the team is obstinate, but because the request to change behaviour without the reasoning that justifies the change is experienced as arbitrary.

Coaching without training also places an unreasonable burden on the coach to develop fundamental understanding on the fly, in the middle of applied work. This is possible but inefficient — and it means the coaching time that should be spent on application is instead spent on instruction.

How they work together

The combination addresses each limitation directly. Training establishes the shared foundation: the vocabulary, the values, the understanding of why certain practices exist. This is particularly important for teams where members have very different backgrounds — the sprint that felt natural to one person may feel completely alien to another. Training creates the common starting point from which coaching can operate.

Coaching then bridges from that foundation to the team's specific context. A coach who knows the team has understood the Scrum values can refer to them when exploring a specific challenge. A coach who knows the team has practised estimation can work with their actual numbers rather than explaining the technique from scratch.

The feedback loop matters too. As teams apply what they learned in training and encounter real obstacles, coaching creates a space to examine those obstacles specifically: not "what does the framework say about this?" but "given what your team understands, what is getting in the way of doing this well here?"

The cultural dimension

Perhaps the most significant contribution of combining training and coaching is cultural rather than technical. Agile is not primarily a set of practices — it is a set of values about how people should work together. Embedding those values requires both cognitive understanding (training) and experiential learning (coaching). The combination, sustained over time, produces the kind of cultural shift that makes the practices sustainable rather than fragile.

Our approach at Better Change combines both by design. The training is highly interactive, with practical exercises that coaches can refer back to during the implementation phase. The coaching is grounded in what the team learned rather than starting from scratch. The intention is that by the end of the engagement, the team can see its own work clearly enough to improve it without ongoing external support.