Shu Ha Ri Agile A Fantastic Tool For Agile Coaches
Unveil the Shu Ha Ri Agile concept — a journey from following to mastery. Explore this Agile approach to foster growth and agility in teams.
Hi, this week I want to introduce you to an old Japanese martial art concept that describes the stages of learning to mastery – Shu ha Ri Agile.
In the transformative journey from project to product, embracing the “Shu Ha Ri” Agile practice can be pivotal. This concept, deeply rooted in martial arts, represents a path of mastery from obedience (Shu), through divergence (Ha), to fluency (Ri), delineating a progression from learning the rules to seamlessly integrating them into one’s instinctual responses.
When applied to a business setting, it guides teams to evolve naturally from a structured approach to one that is more fluid and intuitive over time. Initially, teams adhere strictly to Agile methodologies (Shu), before critically analyzing and adapting them to better suit their unique contexts (Ha), and eventually, reaching a point where the methodologies are second nature and can be fluidly adapted to meet changing needs (Ri).
This progression nurtures a more responsive, adaptable, and ultimately self-sufficient team capable of steering a product through its lifecycle with a deep understanding and agile response to the market’s ebbs and flows.
Hence, the “Shu Ha Ri” concept is not just a growth roadmap for individuals but is a blueprint for teams to organically grow and adapt, facilitating a successful transition from project to product while fostering a culture of continuous learning and adaptation.
ADAPT Methodology® is a unique Digital Product Development framework to change traditional project-centric companies toward product-led companies!
Society changed and leaders need support in the way how they lead and design their digital product organizations, that is the reason why the ADAPT Methodology® was created.
Shu ha ri is roughly translated to “first learn, then detach, and finally, transcend.” I got familiar with this concept during the training I took with Lyssa Adkins. In this post, I want to present this concept applied to agile teams and use it as a tool to help agile coaches identify in which stage their teams are.
As an Agile Coach, you must understand at which stage your team is to help the team perform in a more efficient way. As Lyssa said, if people in a team are in the “Shu” phase they are quite immature in agile, and they just follow the rules.
If they are more mature, they will be in the “Ha”, where they can break the rules safely. The last stage is the “Ri” phase where people are so mature that they can create their own rules. Below I will show you some behaviors that help you to see where the team is on the Shu Ha Ri Agile scale.
Lyssa Adkins points out different examples to check at which level a team is.
Is the team new to Agile methodologies or to one another? Has the team changed or dropped agile practices and lost the intention behind them? Have they mashed up Agile with something else so that their practices are not even clear to them? Do they look at you cockeyed when you bring up the agile manifesto?
If any of these are true, the team may have progressed to Ha too early. They are truly at Shu and need you to guide them to practice at Shu.
Does the team live by the ideals in the agile manifesto? In all they do, do they stand on the side of individuals and interactions, working software, customer collaboration, and responding to change? Do they have the basic practices working well and producing new insights that let them improve each sprint? Do they pause – really pause – to consider the ramifications before they alter, drop, or add an agile practice? Do they face the consequences of these changes squarely?
If these are true, your team is at Ha and needs you to coach them to a deeper expression of Agile.
Has the team altered their practice of Agile and done so consciously, keeping the values and principles of Agile alive? Have they broken through walls of dysfunction in their company so that their practice of Agile leads to progressively better and faster delivery and higher satisfaction?
Have they imbibed the skills and mindsets necessary to be truly self-monitoring and self-correcting?
If these are true, the team is at Ri and needs you to let them go.
As you can imagine all the different levels require different coaching styles, below, you can find the various coaching styles.
Teaching – As the name shows, at this stage, you must teach the rules. The teams that are at this level have a basic knowledge of agile values/principles/practices. They need to have someone to guide them. Examples from Lyssa Adkins:
- “Follow these rules. I have followed them before, and I know they will give you what you want. So, for now, just follow.”
- “The rules work. Anything else is an impediment.”
- “Everything you could need is right here, in this simple framework, so look here for your answers first.”
- “Here is how this works.”
Coaching – This is the next step. Here, teams have a good understanding of agile values/principles/practices, they start to interiorize them from their past experiences. They start to understand how they can use different approaches to achieve the same result.
At this stage, teams can come up with their solutions; they just need a coach to help them find different ways to achieve what they need. Examples from Lyssa Adkins:
- “Why does this way of working work?”
- “What kills it? What renews it? What feeds it?”
Advising – The last stage. In this stage, the team has fully internalized the values, principles, and practices. Everything runs quite well, the role of the coach works as an advisor. For example:
- “May I offer an observation?”
- “That could work. Try it.”
- “I do not know. What do you think?”
One important thing, each successive stage contains the others. For example, if a team is in “Ha”, but you want to introduce a new practice or idea, remember to use a “teaching” approach because they are new to that practice so they will be in Shu for that idea.
This is important because most probably you will be changing coaching styles depending on the practice or idea that you want to feed into the team.
Did you like this article?
We enable leaders to become highly valued and recognized by adapting their project-centric company into a product-led company, society changed and leaders need support to adapt their companies to the digital era, that is the reason why the ADAPT Methodology® was created!
If you are interested in knowing if your company is a project-centric or a product-led company simply take our Project To Product Scorecard.
If you want to know how we can help you to start your transformation please check out our: Project To Product Training.
If you are interested in doing a transformation in your company please check out our: Project To Product Consulting.