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.
There are many possible approaches to help change stick in an organization. In this episode, we explore how a community of practice can help spread knowledge and support Agile adoption.
In this episode we also talk about communities of practice outside the organization were we work. In Paulo’s case, Agile Philippines was one of those communities that helped him. Do you have one near you?
About Paulo Rodriguez
Paulo has worked in the IT industry for 15 years. He started as a web developer for a local bank. His Agile journey began in 2015 and he’s been a Scrum Master for 3 years. Paulo is also a Certified Professional Scrum Master from Scrum.org (PSM I).
As Scrum Masters we focus a lot of our time and attention on the work with the teams we support. Ultimately, however, the managers of those teams have a great influence on what the teams do, how they act and how they apply Agile in their day-to-day work.
In this episode we explore the role of the manager in an Agile transformation and talk about how the Scrum Master must take into account how the managers influence the teams, and address that influence directly.
About Claudia Toscano
Claudia is an Agile Coach and Scrum Master since 2014, she in charge of the Agile Transformation at EPM with a team of 5 other people. Agile and being Mom are the things she enjoys the most.
We often work within environments where the “vanilla” Agile approaches are insufficient. In this episode we explore what happens when more traditional organizations are adopting Agile. We talk about the role of the Product Owner in traditional organizations and the critical role that the Scrum Master plays in supporting the Product Owner.
In this episode we discuss the importance of Pilot projects in traditional organizations and what we can do to make sure they succeed.
About Darryl Sherborne
Darryl is an IT professional specialising in Kaizen (continuous improvement), Agile delivery and coaching, Lean Thinking implementations and more recently applications of DevOps and Data Science. Darryl can also be found singing in rock/pop choirs, and watching or reading anything in the realm of Sci-Fi / Marvel.
One of the aspects of change is the processing of information. As Scrum Masters we can help the teams, and organizations we work with process information better, and visualize that in the context of the shared goals. In this episode we talk about how to use the available data to foster a positive dialog, and trigger change in our organizations.
About Joanna Koprowicz
Joanna is an Agile Enthusiast with a burning passion to help organizations work smart not hard. She is one of the co-organizers of Agile-Lean Ireland Community. Currently she works as a ScrumMaster in Dublin.
In this episode Max shares with us the often seen anti-pattern when change gets stuck when middle-management is involved. We explore the reasons for that, and discuss what we can do – as Scrum Masters – to help middle-management understand, adapt and continue the change process.
Maximilian worked as a Scrum Master for several years and believes that the way to look at the role is to always have in mind the following quote: “Keep moving forward” – his favorite quote, and what he tries to do every day. “One step at a time!”