Episode Summary: Learning to Spot Team Performance Warning Signs Early As A Scrum Master | Somya Mehra
Podcast Title: Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Host: Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner
Guest: Soumya Mehra, Scrum Master at U-Blox
Release Date: August 11, 2025
Introduction
In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Soumya Mehra from Finland, a seasoned Scrum Master with nearly seven years of IT experience spanning India and Finland. Soumya shares her journey, challenges, and invaluable lessons learned in her role, providing actionable advice for Scrum Masters aiming to enhance team performance and dynamics.
Guest Background: Soumya Mehra
Soumya Mehra brings a diverse background with experience in both waterfall and agile methodologies. Currently a Scrum Master at U-Blox, she emphasizes a people-first approach, driven by her deep interest in human behavior and understanding the motivations behind team members' actions.
Key Quote:
"It's about the role choosing you to become." – Soumya Mehra [04:11]
Journey to Becoming a Scrum Master
Soumya began her career as a business analyst. Her interest in Scrum was piqued when her company experimented with Scrum ceremonies amidst a traditional waterfall framework. Observing effective teamwork and communication during refinements contrasted sharply with the waterfall model, sparking her curiosity.
During the COVID-19 pandemic, with ample time and limited job opportunities, Soumya pursued certifications in both Product Ownership and Scrum Mastery. Although she initially leaned towards the Product Owner role, unforeseen opportunities led her to embrace the Scrum Master position, a role she now thoroughly enjoys.
Key Quote:
"When I look back now, I feel like it's about not what you choose to become, it's about the role choosing you to become." – Soumya Mehra [04:17]
Difficult Moment Story: Declining Team Performance
Soumya recounts a challenging experience early in her Scrum Master career. She joined a seemingly balanced team comprising senior developers, mid-level developers, junior developers, a product owner, and a tester. However, shortly after her arrival, two senior developers left, disrupting the team's balance.
Timeline of Events:
- Team Imbalance: Loss of senior developers reduced team velocity.
- Hiring Attempts: Attempted to rebalance by hiring internally and externally, but velocity continued to decline.
- Signs of Frustration: Middle and remaining senior developers became silent and frustrated.
- Revelation: Upon individual conversations, Soumya discovered that the last senior developer was disengaged and not contributing effectively for two years.
Key Quote:
"I failed as a Scrum Master because I was observing the Velocity and the team mood, but I was not discussing it with anyone." – Soumya Mehra [08:17]
Lessons Learned
Soumya emphasizes the critical importance of proactive communication and early detection of team issues:
- Regular One-on-Ones: Establishing consistent individual meetings with team members to gauge their sentiments and uncover underlying issues.
- Transparent Communication: Encouraging open dialogues within the team to address frustrations and performance concerns.
- Early Intervention: Acting promptly when warning signs are detected to prevent morale and velocity from declining further.
Key Quote:
"As a Scrum Master, what is the value of having one-to-ones with your team, listen to them? And even as a Scrum Master, if you think something is fishy or something is wrong, talk to your team. Do not wait for them to come to you." – Soumya Mehra [11:04]
Recommendations for Scrum Masters
Drawing from her experience, Soumya offers valuable strategies for Scrum Masters:
- Initiate One-on-Ones Early: From the outset, engage with team members individually to build trust and understand their perspectives.
- Evaluate Team Dynamics: When joining a new team, inquire about existing team dynamics and any pre-existing issues from previous Scrum Masters.
- Monitor Metrics with Context: While metrics like velocity are essential, they should be interpreted alongside qualitative insights from the team.
- Address Underperformance Tactfully: When dealing with underperforming team members, assign clear responsibilities and set expectations without resorting to blame.
Key Quote:
"Not taking an action is also a decision." – Soumya Mehra [11:28]
Conclusion
Soumya Mehra's candid recounting of her early challenges as a Scrum Master underscores the pivotal role of communication and proactive engagement in fostering a healthy and productive team environment. Her insights serve as a valuable guide for Scrum Masters aiming to identify and address performance warning signs early, ensuring sustained team morale and efficiency.
For more actionable advice and inspiring conversations with Scrum Masters worldwide, subscribe to the Scrum Master Toolbox Podcast.