Teams were running every sprint event and using all the right words, and throughput still was not where it should have been.
Every Event on the Calendar
By the time we arrived at a global research and advisory firm, it had already adopted Scrum. The teams ran sprints. They held every event. They used the vocabulary fluently. By every visible sign, they were doing what the framework asked.
The results did not match the activity. Throughput was not where it should have been. Teams were not improving at the rate anyone expected. And nobody could explain why a framework this well documented and this widely used was producing such inconsistent results. The teams had been trained. The calendars were full. The work was not moving the way all that effort suggested it should.
The Training Covered the Rules, Not the Judgment
The training had covered the events, the roles, and the artifacts. What it had not covered, because training rarely does, was the judgment needed to make them work with these teams, on this kind of work, in this organization. Training explains what a sprint review is for. It does not show anyone how to run one when stakeholders are skeptical and product owners are defensive. It explains what a product owner does, not what to do when the people holding that title behave more like stakeholders than owners.
We started with an agility assessment that gave two views of each team. One was operational: how the team ran its events and where its practice diverged from what the framework required. The other was organizational: whether the business around the team was supporting its way of working or undermining it. The picture was tiered. One team was operating at what we called bronze. The events were happening, but the quality of the conversations inside them was inconsistent, and the measures we tracked, including throughput, scope variance, and team happiness, were not moving the right way. Others were further along and still short of what the framework could produce.
The leader who had brought us in recognized the problem quickly. The training had equipped the teams just enough to get into trouble. In our view it had given them the vocabulary without the judgment to apply it, which is harder to fix than no training at all, because the teams believed they were already doing Scrum.
- Sprints and events all held
- Vocabulary used fluently
- Priorities added mid-sprint
- Throughput below expectations
- Coaching inside the events
- Refinement producing clarity
- Priorities enter at planning
- Throughput up, variance down
The Tax Nobody Had Booked
What followed was embedded coaching. We sat with the teams in their events, observed, and gave feedback in the moment and in retrospectives. We helped product owners understand what refinement was supposed to produce. We helped Scrum Masters see that their role was not administrative coordination but active facilitation of the team's ability to improve.
The hardest conversation was with leaders. Some had a habit of inserting new priorities in the middle of a sprint. To them it felt like responsiveness. In the data it showed up as a tax on the team's capacity: higher scope variance and lower throughput, two of the measures we were tracking every sprint. Each inserted priority made the team busier and left less work finished. The leaders were not careless. A request that looked small on the day it was made simply never showed its cost to the person making it.

The Teams Moved at Their Leaders' Pace
The teams moved, though not all at the same pace and not all to the same place, which was expected. Teams are not identical even with identical inputs. The people differ, the work differs, the leaders around them differ, and willingness to change is spread unevenly across any organization.
The clearest pattern was leadership. Teams whose leaders leaned in moved faster. Teams whose leaders offered verbal support without changing their own behavior moved more slowly, because a framework cannot hold when the environment around it keeps undermining it. The same events, run by the same kinds of teams, produced different results depending on whether the people above them protected the sprint or kept reaching into it.
-
Assess each team How it runs, and what surrounds it.
-
Where it stood Bronze found Events held, conversations uneven.
-
What changed Coach inside the work Feedback in the events themselves.
-
What changed Protect the sprint Priorities enter at planning.
-
Where it landed Silver, and one gold Bronze teams moved up a tier.
Consistent Instead of Busy
By the end of the engagement, the teams that had started at bronze had reached silver, and one had reached gold. The measures told the story in terms the organization could use. Throughput was up. Scope variance was down. Team happiness had improved, which mattered beyond the score itself, because happier teams hold on to what they know, and that knowledge compounds into delivery capacity over a year in ways no single sprint shows.
The problem was not fully solved. An engagement that lasts as long as a budget cycle rarely lasts as long as a transformation needs. What it did was move three teams from a framework that produced inconsistent results to one that produced consistent ones, with enough judgment to keep improving after we left.
The teams had never lacked effort. Before the change they were busy with the framework. After it, the framework was busy with the work.
Activity proves a framework is being followed. Only the flow of finished work proves it is working.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


