Shu Ha Ri: the three stages of Agile mastery

Shu Ha Ri — a martial arts concept representing the three stages of mastery. Scrum teams typically move through these same phases, though not always in a straight line.

Shu — Follow the rule

Learning how to be Agile begins with the what and the why of Scrum. Why do we have the ceremonies? What are the responsibilities of the roles? What is a backlog and how do I groom it?

At this stage, teams need guardrails. The rules aren’t arbitrary — they’re scaffolding that lets you build something before you understand the underlying structure. A new Scrum team that starts skipping retrospectives because they seem redundant is like a student skipping scales because they want to play songs.

Ha — Break the rule

Once a team has internalized the fundamentals, they can start adapting. This stage is often marked by some turbulence — velocity dips, friction in ceremonies, debates about process. That turbulence is healthy. The team is learning how, when, and if they can bend the rules.

Maybe two-week sprints don’t fit their delivery cadence. Maybe the daily standup format needs adjustment for a distributed team. These are valid experiments — but only the team that knows the rules deeply can break them productively.

Ri — Be the rule

The final stage is where Agile becomes invisible. The team doesn’t think about Scrum — they just work in a way that happens to reflect its values. Empiricism, transparency, and adaptation are baked into how they communicate, not ceremonies they attend.

What to do when teams regress

Even teams that have achieved mastery can regress. A reorganization, a new product pressure, a change in team membership — any of these can knock a team back toward Shu.

The instinct is to jump to fixing the symptoms: retros feel stale, velocity is inconsistent, the backlog is a mess. But the better move is to coach the principles — not the mechanics.

Ask the team where they might not be living up to the Scrum values. Use empirical data to surface problems: velocity trends, bug rates, the gap between value promised and value delivered. Then ask the team to come up with improvements. Suggestions from the team stick; mandates from above don’t.

Mastery isn’t a destination. It’s a practice — and occasionally, going back to basics is part of that practice.