Sometime back a colleague had shared a post online on the concept and also an interesting scale to measure self as Scrum Master & Agile Coach in #Agile #Scrum methodology.
This piqued my interest in what is exactly “#Shu #Ha #Ri” in Scrum/Agile context and got me thinking how it will help the Scrum Masters??
So some quick facts & info about it which I found during my research on this subject:-
- The concept of Shu Ha Ri comes from the Japanese martial art of Aikido
- Alistair Cockburn introduced it as a way of thinking about learning techniques and methodologies for software development.
- Shu-Ha-Ri is a way of thinking about how you learn a technique.
- The Shu Har Ri concept can be used to consider what qualities make a great ScrumMaster? And what does a ScrumMaster do in each state?
- The idea is that a person passes through three stages of gaining knowledge:
- Shu: In this beginning stage the student follows the teachings of one master precisely. He concentrates on how to do the task, without worrying too much about the underlying theory. If there are multiple variations on how to do the task, he concentrates on just the one way his master teaches him.
- Ha: At this point, the student begins to branch out. With the basic practices working he now starts to learn the underlying principles and theory behind the technique. He also starts learning from other masters and integrates that learning into his practice.
- Ri: Now the student isn’t learning from other people but from his own practice. He creates his own approaches and adapts what he’s learned to his own particular circumstances.
- Now, this idea in Scrum methodology can be taken up as follows:
- In the Shu state, the ScrumMaster sets up the process, helps the team get to a sustainable pace with known velocity and uses the Retrospective to introduce a change that improves velocity.
- In the Ha state, the ScrumMaster has a team that gets software done (all features tested and no bugs) at the end of the sprint and has a good product owner with ready backlog at the beginning of a sprint, has data that clearly show at least a doubling of productivity, and has strong management support. The team is positioned to work on hyperproductivity, the design goal of Scrum.
- In the Ri state, the team is hyperproductive. But what is the ScrumMaster doing and do you really need one? You need the ScrumMaster but they don’t have to do much essentially.
- It essentially help you on how to make a Scrum Team so self-organized that it can function WITHOUT a Scrum Master also (Yes, quite a radical idea!! J )
Reference Links and More info:-
