Photo by Joshua Earle on Unsplash+
At the beginning, Scrum is very visible.
There are named roles, scheduled events, artefacts with capital letters. Stand-ups are announced. Refinement is booked in advance. The backlog is a thing that needs managing.
This visibility is not a failure. It is scaffolding.
Scrum exists to create just enough structure to help a team notice reality more clearly: what is actually happening, where value is flowing, and where it is getting stuck.
But something interesting happens as a team matures.
The more deeply the principles are understood and embodied, the less the framework itself needs to be seen.
Inspection and adaptation stop being calendar events and start becoming habits.
Planning becomes a shared conversation about intent and trade-offs, not a meeting.
Leadership emerges where the work is, not where the job title sits.
At that point, Scrum begins to dissolve.
Not because it has failed, but because it has succeeded.
Shu – ha – ri … obey – detach – transcend.
There are no ceremonies’, only natural rhythms of checking in and adjusting course.
There are no ‘roles’, only people taking responsibility when it is needed.
There is no ‘backlog’, only a clear and continuously updated sense of what matters most next.
The danger is that organisations often mistake invisible Scrum for no Scrum.
From the outside, it can look informal. Unstructured. Even chaotic.
But inside the team, clarity is high. Feedback is fast. Decisions are grounded in value rather than habit or hierarchy.
This is agility as a state of being, not a process.
Scrum, at its best, is not something a team does.
It is something a team grows out of.
When that happens, the framework quietly steps back, having done its job.
—
Where does your team sit – still building scaffolding, or afraid to let go of it?
