As Scrum Masters we want to help our teams succeed. And we do everything we can to help them. Sometimes a bit too much. Sometimes we might become the bottleneck. Running from meeting to meeting, trying to answer all the questions, help everybody. But that does not scale. How can we break free from that anti-pattern? Karthik shares with us his journey and what he learned back then that helps him stay in his zone, help without taking over.
About Karthik Nagarajan
Karthik has worked as a Product Manager, Scrum Master and QA Manager across a variety of domains, including: Fintech, Travel, Human Capital Management, CRM, Recruitment, Insurance, Banking and Financial Services. He loves tackling complex business challenges and being a positive bridge between Product, Design, Engineering, Quality Assurance, Customers and Business Teams.
In this story that Adrian shares with us we explore our tendency to hide the failures, to cover for each other rather than addressing the problems we are facing. We discuss the consequences of that Anti-Pattern and how we should, as Scrum Masters, help the teams we work with address the problems head-on.
A Scrum Master who specialises in Mobile and User Centred Design based approaches, Adrian comes from a testing background and he still finds that he champions making testing easier for the teams he works with. Due to that Adrian is also a strong advocate of XP practices (and, from that, BDD)
When working in certain organizations we are challenged with contexts that we just can’t cope with. Whether it is a personality problem, or just a complex social conflict, it is crucial to understand where our limits are, and accept those. Being humble is key to keep our sanity and move on. As a Scrum Master we should be very clear on what kind of situations we are not ready, or even wanting to face. Jacopo shares just that kind of story in this episode.
About Jacopo Romei
Agile practitioner since 2003, entrepreneur more than once, he has been agile coach in eBay Italia, co-founder of the ALE Network and a former member in Cocoon Projects, an open governance based company. His main focus now are contracts and lean-thinking-compatible agreements.
Scrum made it clear from the start that Scrum Master and Product Owner roles are different and require different mind-sent and therefore also different people. But still many companies want to push for having only one person in both roles. Does that work? Maybe it can work, but in this episode we listen to a story where that did not work and what are the signs to look for if are ever in that position.
About Jonas Allared
Jonas is an experienced Scrum Master and Agile Coach and he is especially passionate about creating effective teams and healthy organizations. With focus on the human side he enjoys raising both the well-being and productivity of those he works with.
Tony shares a great story about how to get people to enter the Agile/Lean mindset, and a story about how we, as Scrum Masters can easily forget the capital rule of Scrum: involve the team.
About Tony Richards
Tony is an Agile coach working with a global insurer wanting to become more Agile. Starting his career as a software developer working with Toyota he has a background in Lean and came across Agile in 2010 as part of a test and learn initiative. He is keen to help leaders understand their role in creating an environment where Agile can flourish. To support this he has been working on a game inspired by the research of Michael Spayd and Lyssa Adkins to support this journey.