JB Rainsberger is a software development consultant who has a unique perspective on Agile software development, team motivation, team leadership, and team management for Scrum Masters. In his early career, JB worked as a software developer and had a keen interest in the personal aspects of software development. Over time, he began to focus more on interpersonal aspects, such as communication and empathy, as many of his assignments required him to develop those skills.
These days, JB works with individuals and organizations to help them improve their software development processes, with a particular focus on the human aspect of development. He has spoken at events, and written on this topic on his blog blog.JBrains.ca. One key inspiration for JB was the book “The Secrets of Consulting” by Gerald (aka Jerry) Weinberg.
Understanding the Systemic Challenges: Why Scrum Masters Struggle to Build Empathy
Building empathy is critical for Scrum Masters to become effective leaders. However, there are several reasons why Scrum Masters may struggle to build empathy towards developers. According to JB, one systemic problem is the way people are pushed into Scrum Master roles. In larger organizations, there is often a pseudo Agile transition where people are given the Scrum Master label without necessarily being ready for it. Additionally, the word “master” in the term Scrum Master can be misleading and create an unwarranted sense of superiority.
When people feel that they need to change something, they often focus on themselves and overlook empathy towards others.
Another challenge can be the death march environment, where Scrum Masters may feel overwhelmed with deadlines and performance expectations. JB’s advice is to adopt a servant leadership mentality, which puts the focus on helping others to succeed, rather than imposing authority. Scrum Masters who can build empathy towards developers will be better equipped to lead their teams towards success in Agile software development.
From Tracker to Coach: The Importance of Empathy in Scrum Master Roles
Low levels of empathy in Scrum Masters can have significant consequences for Agile software development teams. According to JB, when Scrum Masters lack empathy towards their team members, they may become more like “trackers” rather than coaches. This can lead to a focus on deadlines and performance metrics rather than a focus on team collaboration and communication.
Scrum Masters who lack empathy may also become impatient when interacting with their team members, leading to a lack of trust and cooperation. Additionally, Scrum Masters may become micromanagers who fail to provide their team members with the autonomy they need to succeed.
This can create a blame cycle in the team, where developers may blame each other or the Scrum Master for their behavior. This blame cycle can be detrimental to team morale and collaboration, ultimately leading to suboptimal performance.
By contrast, Scrum Masters who build empathy towards their team members can break the blame cycle and create a culture of collaboration and trust. Empathy is a critical component of effective leadership in Agile software development, and Scrum Masters who prioritize empathy can help their teams to achieve their full potential.
The Law of Generous Interpretation: A Key to Developing Empathy as a Scrum Master
When working with Scrum Masters, there are several tips and approaches that can help them better understand and build empathy with developers and testers. One useful model to understand how interactions happen between people is the Satir Interaction Model by Virginia Satir. This model provides a way to “debug” interactions that went wrong and helps people recognize the fundamental irony of interaction.
Scrum Masters can benefit from asking themselves why they find themselves blaming someone and how their behavior may be objecting to the behavior of others. It’s important to recognize that behavior is a response to an interpretation of what happened, and Scrum Masters can develop empathy by looking at the interpretation. Strategies such as the law of generous interpretation, which involves assuming positive intent, and the law of three interpretations, which encourages thinking of at least three different ways to interpret what is going on, can be helpful in this regard. Scrum Masters can also practice cognitive empathy, which involves putting oneself in the shoes of others and imagining what they might be thinking or feeling. Norm Kerth’s work and the Prime Directive can also be useful resources for Scrum Masters looking to build empathy with their teams.
Ultimately, the journey towards empathy may lead Scrum Masters from cognitive empathy to compassion, a deeper and more personal understanding of the struggles and challenges faced by their team members.
Signs to Look Out for as a Scrum Master: How to Know When Developers and Testers Need Support
In order for Scrum Masters to effectively build empathy with their team, it’s crucial that they are able to “read the room” and understand the needs of their team members. One key aspect to pay attention to is when developers may be retreating to technical work.
As JB explains, many programmers find comfort in the fact that the computer does exactly what they tell it to do. However, when they are struggling to understand what is happening in the broader context of the project or team, they may retreat to technical work as a coping mechanism.
This can be a sign that they need additional support and guidance from the Scrum Master. Another important aspect to pay attention to is the communication patterns within the team. Are team members consistently blaming each other for mistakes or errors? Are they being defensive in their interactions? These can be indicators that there is a lack of trust and empathy within the team. By paying attention to these signs and being proactive in addressing them, Scrum Masters can help foster a more collaborative and empathetic team dynamic.
Empathy-Building Tools for Scrum Masters: A Guide to Helpful Resources
There are several great resources available that can help Scrum Masters develop their empathy skills. One book that JB recommends is “The Responsibility Virus” by Roger Martin. This book explores what happens when there is a responsibility imbalance in teams and how this can affect team dynamics and productivity. Another great resource is “How the Way We Talk Can Change the Way We Work” by Robert Kegan and Lisa Laskow Lahey. This book focuses on the language we use in the workplace and how it can either support or hinder productive communication and collaboration. The Heath brothers’ book “Switch”, which includes a chapter named “Scripting the Critical First Steps” is also a valuable resource for Scrum Masters, as it provides practical strategies for creating effective communication and collaboration within teams. Another excellent book is “Agile Conversations” by Douglas Squirrel and Jeffrey Fredrick, who have been previous guests on the podcast. This book offers practical advice on how to have meaningful conversations in an agile context, with a focus on improving empathy, collaboration, and productivity. Finally, JB also recommends exploring Nonviolent Communication (NVC) as a tool for developing empathy and effective communication skills.
About J.B. Rainsberger
JB is a seasoned software developer, consultant, and trainer based in Canada, known for his expertise in Test-Driven Development (TDD). With his extensive knowledge and experience in the field, he authored the acclaimed course “The World’s Best Intro to TDD” and actively contributes to the community through his blog “The Code Whisperer.” JB is a sought-after speaker and has been invited to present at numerous events worldwide. In addition to his passion for software development, he is also a skilled Bowling player. JB’s diverse set of skills and experiences help him inspire and empower fellow developers through his work.
You can link with J.B. Rainsberger on LinkedIn, visit his home on the net at JBrains.ca, and even ask him questions at ask.JBrains.ca.
If you want to know more about his offer, and get support from JB, you can visit experience.JBrains.ca.
