Planning is not the ultimate solution to problems we face. Agilists know this to be true, and it is even one of the values in the Agile Manifesto: Responding to Change Over Following A Plan.
But planning is still necessary, and a critical part of how teams and organisations work. As Scrum Masters, the planning discipline is one of the key aspects we should focus on. In this episode we talk about one possible evolution of planning for our teams. From hard estimates, to Story Points.
Featured Book of the Week: Coaching Agile Teams by Lyssa Adkins
The coaching stance and the ability to help team members progress in their own learning journey is critical for us, Scrum Masters. In Coaching Agile Teams, Lyssa Adkins describes and teaches us about Coaching as an approach to help teams, and how that affects our Scrum Master role.
About Zeshan Ilyas
With a firm focus on Agile and Scrum methodologies, Zeshan has worked within high profile organisations, including the HSBC, Capgemini Financial Services, Talk, Talk, and many more.
Having worked with Agile companies for many years, Zeshan identified a need for a community of Agilists in Pakistan, which would bring together professionals adopting an Agile or Scrum approach, help increase awareness of Agile.
When teams are stuck in their Agile adoption, it is tempting to bring in more training, do more teaching and expect that to solve the problem. In reality, however, the situation is much more complicated. We need to understand the real reasons for the team’s lack of progress, and adapt our approach to the reality we face. Training may be a good option, but it certainly isn’t the only one. In this episode we talk about a team that was stuck, not completing sprints, no tester in the team, etc. And we cover some practical tips on how to deal with similar situations.
Featured Book of the Week: Scrum Field Guide by Mitch Lacey
In the Scrum Field Guide, Mitch Lacey lays out advice for the Scrum practitioner’s first year. It is a practical advice-filled book that will help you face, and overcome the most common problems that Scrum Masters face in their first few months on the job.
About David Spinks
David has over 15 years experience in the IT industry. He began his career as a software developer before becoming a Scrum Master in 2012. He calls himself an ‘agile adventurer’ and believes in continuous learning in himself and others. His passion is getting the best out of teams and seeing people reach their full potential. He has worked in a variety of industries, including eCommerce, social housing and education.
When strong personalities are in positions of power, their ideas become “law”. But sometimes the leaders are themselves prisoners of their own approach to work. In this episode we discuss how we, as Scrum Masters, can help those leaders recognize the anti-patterns they create and overcome those obstacles to the performance of the team.
Featured Book for the Week: The Alchemist by Paulo Coelho
In The Alchemist, Paulo Coelho tells the story of a pilgrimage and journey where the hero of the story goes through many challenges and is pushed to learn more about himself, and face the world without fear. This book was an inspiration for Jem when he was introducing the Scrum Master role to a new organization, and he was himself a new Scrum Master. Fear is part of the journey, and this book helped Jem accept and overcome that fact.
About Jem D’jelal
Jem trained to be a social worker, but ended up dropping out & joining the dark side instead : investment banking 🙂 In a funny way, Jem was led back to his passion – helping people. This happened when he was introduced to Scrum in 2006, and has been a career Scrum Master since. He calls himself “nomadic”, having had almost 30 roles in 10 + years. He does say that he will be searching for a home at some point. Some of Jem’s other passions involve running, a part time mentoring charity for repeating youth offenders in North London & callisthenics.
When working with multiple teams, in a multi-team Scrum project, we may face what Andreas faced: the finger pointing anti-pattern. This is especially common in environments where no one wants to “be wrong” or take risks.
Even if learning and growing requires taking risks and sometimes “being wrong”, the fact is that no one wants to be that team that delays the project, so the finger pointing starts.
But how can a Scrum Master overcome that problem? How can the Scrum Master help the teams collaborate? That’s the topic of this episode.
Featured Book of the Week: Succeeding with Agile by Mike Cohn
Teams need to take ownership of their own work, so that they can effectively focus on delivering running, working software every Sprint. However, sometimes there are strong personalities in the team. We may want to ignore that anti-pattern, but it won’t ignore us. In this episode we talk about one such story, where the Architect in the team wanted to overrule the team members, and even escalated the issue to the team’s manager. Listen in to learn about Mark’s role in that story, and how we, as Scrum Masters, can handle similar situations.
Featured Book of the Week: 10% happier by Dan Harris
The book 10% happier by Dan Harris is a true story of how Dan found a way to keep focused, but lose the stress and self-doubt. For Mark however, this was a book about learning to focus on the events in front of him. The “now” that must be our focus as Scrum Masters.
About Mark Cruth
Mark has been playing in the Agile space since 2009, helping multiple organizations move towards a more Agile perspective on work across several industries, including manufacturing, eCommerce, and FinTech. Today Mark works as an Agile Coach for Quicken Loans, as well as operates his own Consulting company called Teal Mavericks.
Listening is not the easiest part of the Scrum Master job. However, that’s one of the most important and powerful tools we have in our toolbox. In this episode we explore the case of a team that was entering a spiral of conflict and what was needed to avoid that from going out of control.
Featured Book of the Week: The Human Side of Agile by Gil Broza
Sarah is passionate about helping teams work together to bring value to their work lives. She has worked in the Scrum Master role for the past 6 years after transitioning out of waterfall as a senior software engineer. Her (not so) secret goal is to help people bring agile practices home.
Many of us have been in teams where there’s a “dominant” team member. But have we thought about the possible consequences that it may bring to the team? In this episode we explore the possible consequences that dominant team members can trigger. We also discuss a very unusual way to address such situations, one that takes into account the whole team, not just the dominant team member.
About Venetia Foo
Venetia has been on her agile journey since 2007 and has been a witness to the best and to the worst of it. She is passionate about learning and continuous improvement. She uses a variety of skills to empower and enable teams to perform at their best.
It’s hard enough to deliver a small increment of a product, yet we often find ourselves and our teams in positions where they need to deliver a whole product, project or release in 1 go. No change for mistake. And you know what happens: when failure is not an option, failure is the only option!
About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.
Many will say that helping team meeting commitments is how Scrum Masters best do their work. Seann shows us another side of the job: developing teams. Helping them develop their skills, their collaboration, and focus on outcomes, not outputs.
We discuss that knowing “why” is often more important than focusing on the work at hand, and we mention the book by Simon Sinek: Start with Why.
About About Sean Dunn
Sean is an Enterprise Agile Coach with IHS Global. He has been involved with agile development for 8 years as a developer, product owner, and agile coach. Prior to his exposure to agile development Sean spent 13 years in the Canadian Army. In fact, Sean is known to point out that the Army is far more agile than most people think.
That background in the Canadian Army influenced his view of Leadership and the role of Leadership in creating and developing great teams.
You can connect with Sean Dunn on LinkedIn, check out Sean Dunn on the Scrum Alliance or email him at firstname.lastname@example.org.
Check out Sean Dunn’s blog on leadership.
Technology enthusiast. Change artist. Culture hacker. People focused. Helping organizations provide their employees with the most meaningful and fulfilling experience they could have while delivering solutions that change the world. Ebenezer is also a Tech Director at Mannheim.
You can link with Ebenezer Ikonne on LinkedIn, and contact Ebenezer Ikonne on Twitter. You can also read his thoughts on Agile on his blog.