Some problems are easy to name. Retrospectives that produce action items nobody completes. Planning meetings where stories are still being scoped in the second week of the sprint. Velocity charts that fluctuate in ways the team cannot explain. Each problem is visible on its own. Each generates frustration.
What remains invisible is the pattern connecting them. Not because the team lacks intelligence or commitment, but because perspective has limits when you are part of a system. Certain things disappear into familiarity. You work around what you have stopped questioning. The pattern that might explain everything sits just outside your field of view, and no amount of effort from inside the system will bring it into focus.
Over the past few weeks, I have written about retrospectives that produce no follow-through, velocity metrics that mislead more than they inform, and the behavioural, value, and momentum lags that quietly stall agile transformations. Each of those pieces described a specific dysfunction. This piece brings them together into a diagnostic framework: five signals that suggest a team would benefit from external support.
Sign 1: Your Retrospectives Produce Action Items That Go Nowhere
I wrote about this in detail earlier this month, but it bears repeating here. If your retrospectives consistently generate action items that are never completed, or that are completed but make no measurable difference, that is not a facilitation problem. It is a systems problem.
The pattern I see most often is this: the team identifies an improvement, assigns someone to drive it, and then moves on. Two weeks later, nothing has changed. The responsible person had no time, no resources, and no clear sense of what success would look like. The action item was well-intentioned but under-specified, and it died quietly under the weight of everything else the team was trying to accomplish.
An external coach helps by asking the questions the team has stopped asking. What specific outcome are we expecting? How will we know if this action succeeded? What resources does the responsible person actually need? The value is not in the questions themselves — the team could ask them — but in the fact that someone outside the system is holding the space for them to be answered properly.
Sign 2: You Are Scoping Stories in the Second Week of the Sprint
When I observe a planning meeting, one of the first things I watch for is how well the team understands the stories they are committing to. If stories are still being scoped, clarified, or broken down in the second week of the sprint, that tells me the planning process itself is broken.
This pattern usually stems from one of two causes. Either the stories were not discussed thoroughly enough during planning — the team committed to work they did not yet understand — or the team discovered dependencies and complexities mid-sprint that should have been surfaced earlier. In both cases, the result is the same: the sprint becomes reactive rather than deliberate, and the team spends more time managing surprises than delivering value.
An external coach can see this pattern immediately because they are not caught up in the urgency of the sprint itself. They can ask why the stories were not ready, what prevented the team from identifying the dependencies earlier, and what structural changes would make the planning process more robust. The team knows the answers, but they may not have the space or the permission to act on them.
Sign 3: Your Velocity Varies, and You Cannot Tell Why
Velocity variation is not inherently bad. As I discussed last week, variation is often the most honest signal your process can produce. But if your velocity fluctuates and the team has no coherent explanation for why — if every sprint feels unpredictable, and the retrospectives produce no useful insights about what is driving the changes — that is a signal worth attending to.
The problem is not the variation itself. The problem is that the team does not have a model of their own work that is detailed enough to explain what they are observing. They see the numbers move, but they cannot connect those movements to specific causes. That lack of interpretive clarity makes improvement impossible, because you cannot address problems you cannot diagnose.
An external coach brings a diagnostic lens that the team may not have developed yet. They ask whether the variation is tied to story size, team availability, dependencies, or something else entirely. They help the team build a more precise understanding of their own capacity, so that the variation becomes informative rather than merely frustrating.
Sign 4: Your Retrospectives Only Identify Improvements About ‘Doing Scrum Right’
There is a particular flavour of retrospective that I see in teams that have plateaued. The observations are procedural: ‘we need to update the board more consistently,’ ‘we should time-box our standups better,’ ‘we need to make sure everyone attends planning.’ These are all reasonable concerns. They are also surface-level.
When a team’s retrospectives focus exclusively on compliance with the ceremonies rather than on the outcomes those ceremonies are meant to produce, it suggests the team has lost sight of why they are doing any of this in the first place. They are optimising for the appearance of agile rather than for the delivery of value. And that is a cultural problem, not a procedural one.
An external coach can shift that conversation. They ask not ‘are we doing the ceremonies correctly?’ but ‘are the ceremonies producing the results we need?’ They help the team reconnect the mechanics of their process to the outcomes they are trying to achieve. That shift – from process compliance to outcome orientation – is often the first step toward genuine improvement.
Sign 5: Your Team Is Struggling to Navigate Conflicting Stakeholder Requirements
Most teams operate in an environment where demands are coming from multiple directions. The product owner has a roadmap. Internal stakeholders have urgent requests. Leadership has strategic priorities. And the team is caught in the middle, trying to satisfy everyone whilst maintaining some coherent sense of direction.
When this tension is managed well, it is productive. When it is managed poorly, it becomes paralysing. The team spends more time negotiating priorities than delivering work. Sprints are constantly disrupted by unplanned requests. The backlog becomes a dumping ground for everything anyone has ever asked for, and the concept of a sprint goal loses all meaning.
An external coach does not resolve these conflicts — that is not their role. But they can help the team articulate what is happening, make the trade-offs explicit, and create the structures that allow stakeholders to negotiate priorities in a way that does not destabilise the team’s work. The value is in bringing clarity to what has become chaotic, and in giving the team language and frameworks for managing the tension rather than being overwhelmed by it.
What External Coaching Actually Provides
The common thread across all five of these signs is this: the team knows something is wrong, but they cannot see it clearly enough to fix it. And that is not a failing. It is the nature of being embedded in a system. You see what you are conditioned to see. You miss what you are too close to observe.
An external coach brings a fresh view of the system. They have no stake in the internal politics, no attachment to how things have always been done, no need to defend past decisions. That detachment is what makes them valuable. They can echo what the team already knows but cannot say. They can ask the questions that feel too risky to ask from the inside. They can name the patterns that everyone is working around but nobody is addressing directly.
This is not about importing some external methodology or imposing a prescriptive framework. I have never found that methodology is where the leverage lives. The leverage is in helping the team see their own system more clearly, so that they can make better decisions about what to change and how to change it.
When to Seek External Support
Not every problem requires external coaching. Many issues can and should be addressed internally. But if you recognise your team in two or more of these signs — if your retrospectives are not producing results, if your planning is consistently inadequate, if your velocity tells a story you cannot interpret, if your improvements are procedural rather than substantive, if conflicting stakeholder demands are paralysing your work — then it is worth considering whether an external perspective might accelerate your progress.
The question is not whether your team is capable of solving these problems on its own. The question is how long it will take, and what it will cost in lost momentum, degraded morale, and missed opportunities whilst they work it out. External coaching is not a substitute for internal capability. It is a catalyst. It shortens the cycle between recognition and resolution, and it helps teams build the interpretive frameworks they need to improve sustainably over time.
If you recognised your team in two or more of these signs, you’re not alone — and the patterns don’t resolve on their own. That’s where evidence-based coaching creates momentum. Book a free consultation to discuss your team’s specific situation, and let’s explore whether external coaching is the right next step for you. Sometimes all it takes is a fresh view of the system to unlock the progress you’ve been working toward.
Discover more from The Software Coach
Subscribe to get the latest posts sent to your email.
