When a change process starts it is easy to be tempted to “drive” that change in the organization. However, that’s not always a good option. In this episode, we discuss the possible negative side effects of “driving” change into a team or organization.
How can Scrum Masters get out of the “drive” change anti-pattern? In this episode, we discuss how management can play a major role in helping move to a pull-mode change process and what the role of the Scrum Master is in that type of change.
Listen in to learn about concrete tools and practices that help the Scrum Masters go from “teacher” to “moderator” in the change process.
About Daniel Heinen
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.
David started working with a group of teams that were component-focused and started seeing the usual anti-patterns. The “concept to cash” cycle was too slow. How do you help an organization get out of the component-focused organization and switch to a more outcome-oriented organization?
In this episode, we explore one approach that David put in practice, and how that may help your organization recognize what they are missing by sticking to the silo-prone component-based organization.
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!
When we are involved in large organization transformations there can be a sense of overwhelm. That the organization and the different groups are too large to grasp. So how do you survive a large transformation process? In this episode, we explore some of the practices that David learned through his own story when involved with a transformation in a large organization.
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, one of the key ingredients for our work to succeed is “permission”. Permission to do our work with the teams. Permission to help the team find new ways of working.
In this episode, Silvana shares the story of a team, how they were reluctant to give her permission at first, and how Silvana handled it, to the point where permission was finally granted.
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.
As Paulo started helping this company in their Agile adoption he noticed that, even if the company was “doing” Scrum, they were missing some critical aspects.
Listen in to learn how Paulo helped this company find a better way to adopt Scrum, using the Scrum Values as the anchor to the change.
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 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.