In this episode, Daniel tells us the story of when the Product Owner took a “leader” role, and hid information from the stakeholders. The Product Owner promised many things to management to ensure funding for the project. This is a common anti-pattern in project organizations, but it can have serious consequences in an Agile environment because of the additional transparency that Agile and Scrum bring to the process.
In this episode, we talk about how Daniel and the team handled the difficult and delicate situation they were facing.
Daniel has been a Scrum Master since 2014 on a Scrum pilot at BMW. Since 2016 focusing on organizational change management, for example, facilitating communities of practices for Scrum adoption at BMW. Recently he started working as a Scrum Master and Agile Coach at Autonomous Driving BMW, who decided in 2017 to restructure according to the LeSS framework.
When Scrum Masters come to work with a team they must make a critical decision. Are they there to help the team, in their own terms, or to “bring in” Scrum or improvements? There’s a critical difference between these alternative approaches.
In this episode, we discuss how Scrum Masters can fail when they come to the team to “bring in” Scrum. Listen in to learn how that looks like, and how to detect that anti-pattern before it is too late.
David Denham works as a Scrum Master in Workday in Dublin and is one of the leaders of the Agile-Lean Ireland community and co-organiser of the ALI conference. He previously worked as a UX lead and believes in the power of Product delivery teams being involved in Product Discovery, through practicing Design Sprints. He practices failure every single day by attempting to use his agile coaching skills with his 2 small daughters!
The Scrum Master’s role is primarily a role that serves the team. Without that presence, the teams suffer, and in this episode, we explore what might happen when the Scrum Master – eager to help the organization – focuses on the context, rather than the team.
About David Sabine
David is a Scrum trainer and an advisor to software development organizations. He is in demand among Canada’s largest enterprises including Scotiabank, Sun Life Financial, and Canada’s Federal Government. He formerly worked with DigitalOcean and Myplanet.com, among others. He’s been helping people with the ways they use Scrum since 2007.
As Scrum Masters, we face many of the patterns of the old methodologies. In this episode with Silvana Wasitova, we explore the up-front planning, all-in commitment approach and how that affects agile teams. We also discuss how a Scrum Master can help such teams.
About Silvana Wasitova
Silvana Wasitova, Enterprise Agile Coach, helps teams and companies achieve better results through applying and living Agile values and principles. Scrum practitioner since 2005. Silvana lives and breathes the agile value of “People over Process”, and brings that to the forefront of her coaching work with teams and companies, while focused on the client’s audacious goals and desired results. Silvana has aided multinational enterprise Agile transformations in United States, UK, Germany, Czech Republic, Slovakia, Indonesia and Switzerland with clients including Yahoo, Nestle, Skype, Microsoft, financial enterprises as well as startups.
When we come into work with a team, the first thing we must be aware of is the type and number of stakeholders that we will be dealing with.
In this episode, Paulo presents a story of a team that he was supposed to help, but the stakeholders started messing up with the team, making his work, as Scrum Master, much harder.
Listen in to learn about how to deal with particularly intrusive team managers. Something that we will all need to face, sooner or later.
About Paulo Rebelo
Paulo Rebelo helps companies to improve using agile and lean principles like Scrum, XP, and Kanban. He currently works at Blackhawk Network in the U.S., helping teams succeed by building great products. His background is a developer, Scrum Master, product owner, project manager, and coach. Paulo is a CSP, CSPO and a CSM from the Scrum Alliance and PMP from the PMI.
As projects progress, it is common that the pressure rises. Every day we work with teams that suffer many pressures, from stakeholders, from other teams, and from themselves because of the commitments they want to honor.
In this episode, we talk about a hidden tragedy: the team burnout. Listen in to learn how Liz detected and faced that tragedy.
About Elizabeth Christensen
Elizabeth Christensen shares tales from the not-so-cutting-edge, bringing Scrum to Marketing. She is currently developing scrum practices for a marketing team. With a background in business management & team leadership, this self-proclaimed scrappy new Scrum Master finds her way in a never-before-experienced opportunity.
Kyle’s background as a developer has informed his view of how teams can achieve the level of collaboration needed to be successful in an Agile environment. Having read Kent Beck’s Extreme Programming Explained book, he started to work with developers, helping them improve their ways of working. But that wasn’t enough. In this episode, we explore what is beyond the team that can make or break an Agile transition.
About Kyle Aretae
Kyle has been programming since ’81. Teaching since ’91. Practicing Agile (Extreme Programming – XP) since 2000. Kyle is always interested first in better ways to understand things and systems. Especially interested in Complex (CAS/VUCA) Systems like building software or the economy at large.
“We don’t leave our human-selves at the door once we come into work!” – this is how Faye starts this episode. The question is: as a Scrum Master, what does it mean for me? Faye’s journey to the Scrum Master role gives us some insights into the wide-spread consequences of that phrase. It also links directly to the story of failure that Faye has to share with us. It is a story of how a team member started bullying other team members. Listen in to learn to detect bullying signs early on.
About Faye Thompson
Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.
Management was micro-managing the team. Ilya, the Scrum Master, tried to protect the team. The stress levels were high… This is a very common story in the software industry. When deadlines loom, the whole dynamic changes. As Scrum Masters, we must be ready for that moment. Listen in to learn about how Ilya handled the situation, and what you can apply in your own situation when the time comes.
Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.
As we work with multiple teams, it is inevitable that we will meet a team member that is against Scrum in all possible ways. They’ll ask: why do we need to have a Sprint Review? Why do we need to have a retrospective every Sprint? How do we, as Scrum Masters, deal with such team members? Listen in as Peter shares his experience with such a team member, and how he focused on helping the team, despite the negative comments from one team member.
About Peter Zylka
Peter is a freelancing Scrum Master who really loves what he does.
Peter is passionate about Agility and loves supporting teams and organizations on their way into the agile world. As a Scrum Master his goal is to enable each individual in the team to perform the best possible way and to actually understand what a team really is all about.
He starts every day with the goal to make the people around him better.