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.