As Scrum Masters we are often confronted with challenges and problems that the teams suffer on a daily basis. These challenges are only the start of the change process. In this episode, Liz explores the ways in which we can support the teams in effecting changes they perceive as necessary. We talk about the role of retrospectives in the change process and also the importance of arguing for the change with data and evidence to gain stakeholder support.
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 own journey when learning about change led him to understand the importance of focusing on the organizational aspects, not just the team he was working with. In this episode, we explore several different change models and end up with a set of tips that Kyle has learned over time work for organizational, not just team-level, change.
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.
There are many tools out there to support a change process. So many in fact, that we often forget the humble Retrospective. The most important tool in our Scrum Master toolbox: reflect and adjust, inspect and adapt – the core cycle of change.
In this episode, we explore how the Agile Retrospective can become the engine of self-driven team change.
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.
When teams start with Scrum, there’s the temptation to define and implement many changes at the same time. After all, there’s a lot of new practices to take in. However, Ilya’s suggestion is different. Listen in to learn about the idea of “one change at a time”, and how you may be able to apply it in your context.
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.
When a team has left Scrum to adopt another method, but is stuck, going back to Scrum may be a good approach. As they go back to something familiar they can regain their self-confidence. In this episode we explore such a story, and how Peter structured his approach to this change process, that he divides into 3 main steps.
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.