This message from a software developer team member pops out in our group chat. I know that he is half-joking, teasing. I just smiled and let it pass. I know better than debating this on the public chat. However, I will admit that that comment gave me a feel of uneasiness, a little bit offended, maybe.
Japan government encourages kids to stay home and study due to the possible outbreak of corona-virus. Another software developer that is affected commented in the same forum on how it is amusing to see how the school is doing short teleconference every morning with the parents asking questions like: how was the homework yesterday, explaining the homework today, and if they need the teachers help. “It just like our daily stand-up even though they don’t know Scrum”, he commented.
When I thought about it, both these comments have the same underlying perception that drives it, the thinking that Scrum events or activities is only a kind of ceremony, custom, habits, signature of a Scrum team. It, unfortunately, undervalues the benefit of these events.
Magic is mostly illusion. I remember the stories back how someone will invent something that looks impossible and perform in front of nobles and kings. The realization that we couldn’t understand and reason on why something is happening gives the illusion of Magic. For people in the 10th century stories of people flying through the sky sounds like Magic. Yet when we uncover the science behind it, people can start to reason and understand. When the illusion is revealed, it is not Magic anymore.
Scrum is much in the same situation. People always hears and sees the success. They see the mechanics, and experience the culture and atmosphere. But rarely they understand why? The explanation and reasoning on the science behind it always feels lacking that it feels like Magic. How come just by doing a daily stand-up every morning, or doing sprint retrospective, it can produce such a productive and successful team? Surely this is a work of Magic or intervention from a higher being. (Spoiler: it is not)
As a reflection, it is my job as a scrum master job to educate the team on Scrum and Agile. Most of the time we teach the shape, construct, the behavior of Scrum leaving the science and reasoning behind it. Like teaching Kung-Fu or Karate, it is quick win to educate the team on the form, so they start experiencing the benefit. But stopping there is not enough. We need to educate them on the reasoning and understanding of Scrum and Agile. I like how the Shu-Ha-Ri describe this journey of a team (and ourselves). How, as a beginner, we should follow the form, break the form, and, as mastery comes in, forget the form.
I can’t avoid this to sound like a religion in the beginning. Teaching these concepts and science behind it can be very difficult and require people to change their mindset. And, changing people mindset can not be done in one night. However, I can treat these curious comments as opportunities :). Admittedly my team is still at a very beginner stage of the journey, and it will take more time to get them to a better shape as a team. My hope is that sometime in the near future we will be ready to understand the science behind Scrum and Agile.
Agile & Cycling 