The three stages:

Shu (Obey) — Follow the rules exactly

• Do not modify, do not question, do not "adapt to your context"
• Learn the form as prescribed — every ceremony, every artifact, every role
• This feels rigid and sometimes uncomfortable. That is the point.
• You are building muscle memory, internalizing patterns, and experiencing the system as designed
• Duration: weeks to months, depending on the discipline

Ha (Detach) — Understand the principles behind the rules

• You have mastered the basics and now see the principles beneath the practices
• Begin adapting: shorten standups, combine ceremonies, modify artifacts
• Changes are grounded in understanding — you know what you are changing and why
• You can explain the tradeoff of every adaptation you make
• Duration: months to years

Ri (Transcend) — The technique is internalized

• You no longer think about rules — you act from deep, intuitive understanding
• You create new approaches naturally, grounded in the same principles
• Your practice looks nothing like the textbook, but it embodies the textbook's intent
• Others may study your approach as a new "method" — but it is just mastery in action

Applied to Scrum adoption:

• Shu: Run Scrum by the book. All four ceremonies, product backlog, sprint backlog, roles as defined. No shortcuts.
• Ha: After 6+ months of working Scrum, adapt. Maybe your standups are 10 minutes. Maybe you combine review and retro. You know what you are trading off.
• Ri: Your team's process is unique, highly effective, and unrecognizable as "textbook Scrum." But it embodies every Scrum principle: inspect and adapt, short cycles, working software, team autonomy.

The fatal mistake:

Teams in Shu who jump to Ri. "We don't need daily standups — we communicate fine." "Sprint retros feel wasteful — we'll just do them monthly." They strip away practices they have never actually experienced working correctly. They are not transcending the rules; they are avoiding them.