Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches

Episode: Breaking Remote Agile Team Divides Through Unscripted, Informal Connection
Guest: Gosia Smoleńska
Release Date: November 18, 2024

Introduction

In this episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Gosia Smoleńska from Poland, an experienced Agile Coach and Certified Scrum Master. Gosia shares her journey into Agile methodologies, her diverse background, and a poignant story about overcoming significant challenges within a remote Agile team.

Guest Background

Gosia Smoleńska brings a unique perspective to the world of Agile, having started her career in the IT sector in 2013. Unlike many in the field, Gosia's academic background is in land measurement, mining, and geology. Her transition into the tech industry began with an internship at a small startup, where she embraced various roles from QA automation to project management. This diverse experience eventually led her to her first Scrum Master position, where she was instrumental in fostering an Agile culture within the company. Gosia is proficient in multiple Agile frameworks, including Scrum, Kanban, Nexus, and Lean, and is also a certified professional Kanban trainer.

Gosia Smoleńska [01:13]:
"I started in a small startup with seven people. I was the only one not a programmer, so I had the opportunity to explore roles in QA automation, Python development, project management, and business analysis. This diverse exposure naturally led me to becoming a Scrum Master."

The Challenge: Divided Remote Teams Before the Pandemic

Gosia recounts a particularly challenging period when she was part of a dispersed team working across different locations—a scenario that predated the widespread adoption of remote work during the pandemic. The team, consisting of five to seven members, was fraught with interpersonal conflicts and a lack of effective communication.

Initial Attempts to Bridge the Divide

Efforts to conduct retrospectives were ineffective as team members were disengaged and uncommunicative. Conflict manifested in Slack conversations and code reviews, creating a toxic environment where open dialogue was stifled.

Gosia Smoleńska [03:22]:
"We couldn't go through any retrospective. Even sitting in the retrospective room was quiet. When you opened Slack, you'd see all the fights and unpleasant comments in code reviews."

Physical Meet-up: A Misstep

Seeking to mend the fractured team dynamics, Gosia and her team traveled to another country to meet in person. However, the attempt at informal connection fell flat. Their invitation to lunch was ignored, leaving Gosia and an office manager to dine alone, leading to increased feelings of isolation and awkwardness.

Gosia Smoleńska [05:09]:
"We went to the office and suggested going for lunch, but no one responded. We ended up staying alone with the office manager, and it didn't feel right."

The Turning Point: Uncovering Cultural Misunderstandings

The situation reached a critical point when the team leader, recognizing the tension, organized a casual gathering over beers. It was during this informal setting that the root cause of the discord was revealed: a mistranslated nickname that carried negative connotations in the local language, leading team members to harbor unwarranted fears and misconceptions about one of their own.

Gosia Smoleńska [07:00]:
"In our team's native language, the nickname had really bad connotations. They had created an image based on a nickname without understanding its true meaning."

Key Insights and Takeaways

From this experience, Gosia highlights several crucial lessons for Scrum Masters and Agile Coaches:

1. The Importance of Cultural Sensitivity

Understanding and respecting cultural nuances is vital in diverse teams. A seemingly harmless nickname can have unintended negative implications, leading to misunderstandings and friction.

Gosia Smoleńska [09:27]:
"There was a lot of cultural differences among us, and we realized that Baltic countries are not as similar as we initially thought."

2. Facilitating Open Communication

Creating a safe space for team members to express their concerns and misunderstandings is essential. Retrospectives and casual interactions should encourage honesty and transparency to address underlying issues.

Vasco Duarte [09:40]:
"As Scrum Masters, we need to create the space for team members to talk to each other, to introduce themselves in a comfortable way, even if it might not always feel safe."

3. People Over Processes

Agile frameworks are merely tools to guide teams, but the success of any Agile implementation hinges on the people involved. Building a cohesive team requires emotional intelligence, empathy, and proactive efforts to foster trust and collaboration.

Gosia Smoleńska [10:25]:
"As individuals and as a group, building a team requires a lot of skills and willingness. It's not just about following the framework."

4. Adaptability of Agile Practices

Agile methodologies should be adapted to fit the unique dynamics of each team. Rigidly adhering to processes without considering the human element can hinder progress and team harmony.

Host Vasco Duarte [09:49]:
"It's not only the framework that we should go through. This framework is just a guidance and information on how to do things, but the people part is crucial."

Conclusion

Gosia Smoleńska's story serves as a powerful reminder that the human aspect of Agile practices cannot be overlooked. Effective Scrum Masters must prioritize building strong, empathetic teams and remain vigilant about cultural and interpersonal dynamics. By fostering open communication and understanding, Agile leaders can navigate and overcome the challenges that arise within diverse and distributed teams.

Notable Quotes:

• Gosia Smoleńska [01:13]:
  "I started in a small startup with seven people. I was the only one not a programmer, so I had the opportunity to explore roles in QA automation, Python development, project management, and business analysis."

• Gosia Smoleńska [03:22]:
  "We couldn't go through any retrospective. Even sitting in the retrospective room was quiet. When you opened Slack, you'd see all the fights and unpleasant comments in code reviews."

• Vasco Duarte [09:49]:
  "It's not only the framework that we should go through. This framework is just a guidance and information on how to do things, but the people part is crucial."

• Gosia Smoleńska [10:25]:
  "As individuals and as a group, building a team requires a lot of skills and willingness. It's not just about following the framework."

This episode offers invaluable lessons for Scrum Masters and Agile Coaches aiming to build resilient and harmonious teams, especially in remote or culturally diverse settings. Gosia's experiences underline the significance of addressing human factors to successfully implement Agile methodologies.