Sometimes we need to work with teams that have lost hope. The team might be cynical about future improvements and look at Agile or Scrum skeptically. This was what Dmytro had to face in his team. In this episode, we talk about how to work with a skeptical team, and get them engaged in improving their work. This is a critical lesson for all Scrum Masters, don’t miss it!
About Dmytro Balaba
Dmytro calls himself one of the most dedicated Scrum Masters/Agile Coach in the world 🙂 On his right-hand he has a tatoo with golden ratio, Fibonacci sequence. After almost 15 years of work in IT management Dmytro found himself balanced and happy. He’s been a full-time Scrum Master for more than 3 years.
Sometimes, in our role as Scrum Master we find teams that are not able to adopt Agile right away. The worst that could happen would be for us to send those teams to “Agile detention”. In this episode, we explore what Scrum Masters can do when their teams are just starting their Agile adoption journey, in organizations where Agile is not yet the standard approach to work.
About Andy Grosman
Andy has spent the past decade in various industries from Fortune 500 to small and mid-sized companies including Healthcare, Finance, Training and has a background in sales/marketing. He currently leads a team of Scrum Masters in the digital space as well as coaches teams. He has spoken at regional conferences and Agile Meetups on team-building for Distributed teams, how to blend Agile and personal productivity strategies, and how to influence without Authority. He used to live by the Waterfall but got bit by the Agile bug and now is spreading the Agile Mindset wherever he goes.
When Eddy started his Agile journey he was working as a tester. When he understood the power of the Agile approach, he immediately started telling others about it, and ended up training many of his colleagues in a transition. And through his failure to help the people and teams change, he understood a critical lesson about the role of Scrum Master and change agent. In this episode, we explore that critical lesson, and how Scrum Masters can help their teams change and evolve.
About Eddy Bruin
For many years, Eddy has been using serious games and learning metaphors to help teams and organizations move forward. He is an Agile and Test Coach with the mission to help teams deliver software people actually want to use while also enjoying their work. He helps teams to enable feedback loops continuously and likes to discuss all agile and test topics over a special beer. He loves to go to (un)conferences on serious games (for example Play14, Play4Agile), and also on Agile and Testing.
As we start our journey as Scrum Masters, we are bound to find situations and team dynamics to deal with that we were either not familiar or not responsible for handling before.
Everyone will face one of those situations. In this episode, we talk about one such situation in Jim’s career. There was a pattern of behaviour happening that was destructive to the team, but Jim was unsure how to deal with it. Listen in to learn what he learned from that story, that you can also apply in your team when facing a similar situation.
About Jim Sammons
Jim is currently a Professional Scrum Trainer with Scrum.org and works with an amazing team at Insight as an Agile Coach and trainer for their clients around the world. His time as a Scrum Master was awesome and fueled his passion for agility at all levels.
When we take the role of the Scrum Master, many of us are jumping into a new experience. Something we’ve never done before. Whether you have a background in technology or project management, Scrum Master is likely to be a very different role.
In this episode, we discover through Martin’s story what are the most common anti-patterns that we take up as new Scrum Masters. Have you been too committed to the previous ways of working? Have you tried to teach, when the right stance to take was to listen and ask questions? Don’t despair, we’ve all been there and Martin shares his personal story, as well as what he learned from that about the core of the Scrum Master role.
About Martin Lambert
Martin’s an agile coach, trainer and scrum master. He’s a Northener making a living in the south of England and finds great energy and sense of purpose from the agile movement during the second act of his career. Loves the hills and being out on a road bike. And to all the European listeners, he says: “sorry for you know what”.
What can a Scrum Master do when they are part of Agile adoption in a large organization? In this episode, we explore some of the common problems you should be ready for. Dirk shares with us what he learned and how Scrum Masters can prepare for the predictable problems they will face.
In this episode, we refer to the technique “Battle Mapping (PDF at Scribd)” that can help Scrum Masters understand where to put their focus during a transformation.
About Dirk Fabricius
Dirk has worked in jobs with IT focus for 20 years. He has had the roles of Project Lead, Developer (Backend), Product Owner and Scrum Master. He’s also been a Teacher in Public Schools for 7 years.
When helping teams adopt Scrum, it is important to start with the concrete situation the team is in. In this episode, we discuss how you can help the team decide on their own improvements as a starting point to adopt Scrum and Agile.
Stanislava is not only a serious games facilitator and a team coach, but she also spends a considerable amount of time rock-climbing and hiking, traveling with her partner and son, and drawing zentangles.
When organizations bring people together in a team and then add a “planning” factor on top of them to “steer” them in the right direction, they might be losing the most powerful contribution of a team.
In this episode, we discuss what Susanne learned from a situation where she overplanned things, and did not give the team enough freedom and space to bring in their skills and knowledge. A brilliant reminder that we, as Scrum Masters, must focus on the team, not the work! Let the team focus on the work, while you focus on the team.
About Susanne Taylor
Susanne is a transition coach, which translates to roles as: change management facilitator, organizational development consultant, scrum master, agile coach and community manager. (Often simultaneously.) Susanne has learned to be adaptable and resilient after having lived in Alaska, Japan, Taiwan and now Germany. She is passionate about accompanying people on journeys of transformation. (And she considers herself an introvert.)
Some Agile transformations are doomed to failure. In this episode, we talk about the signs that indicate when Agile is not likely to be adopted in an organization.
We also talk about the importance for Scrum Masters to work at different levels of the organization, not only at the team level.
About Izis Filipaldi
Izis’ mission is to help people to improve their knowledge and professional value inside organizations, applying the agile way of working. She has been working as an Agile Coach for more than 7 years, helping people to deliver products, developing an environment free of judgments where they can fail fast and learn faster. Continuous improvement of: people knowledge, product delivery, and work environment, are her 3 main focus on work. And she loves what she does!
Nick was working with a team that had just lost their Product Owner. The new Product Owner had a conflict of interest and was changing priorities mid-sprint. This is a common anti-pattern that many teams face.
In this episode, we talk through Nick’s efforts to help the Product Owner understand the consequences of his behavior. It’s never an easy situation to be in, but we must be ready.
Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at:bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Nick Stewart
Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through the pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.