Jeff is the author of Actionable Agile tools (available on Amazon, and direct from the author at bit.ly/aatbook).
Jeff and János share the story of a DevOps transformation at Meltwater, where they both work. We start by discussing the big differences between an Agile and a DevOps transformation.
The big difference between Agile and DevOps transformations
As they describe it, a DevOps transformation is more about the technical aspects of software development. While in an Agile transformation we may look at processes, and team composition, the DevOps transformation that Jeff and János describe was focused on removing the hand-overs, and building the technical infrastructure necessary for that to happen. Their goal was to create, and support cross functional teams that would be able to implement, deploy and operate their software in production.
This week Jurgen is with us to talk about his latest project: unFIX.work. Jurgen starts this episode by sharing a little known fact about his name, and his personality. We then discuss the role of “change” in Agile adoption. We discuss different types of change (Kaizen, Kaikaku) and why scaling frameworks should take into account both types.
Jurgen Appelo is an entrepreneur, an author, and keynote speaker who applies Agile to his life and his businesses. He’s also prolific writer on all topics business and agile. He wrote Management 3.0, How to Change the World, Managing for Happiness and his latest book about entrepreneurship and product development: Startup, Scale up, Screw up.
Jeff is also the author of Actionable Agile tools (available on Amazon, and direct from the author at bit.ly/aatbook).
Why does Management resist Agile change?
This is the first question of the episode and one that Scott and Jeff have worked together on for years. Scott shares how his past as a developer has helped him understand the role of management in an Agile organization.
We also talk about how to understand the reaction of managers when employees come to them with gripes, or ideas for changes to implement. We tend to think that when managers don’t do what we ask, they haven’t listened to us. Is that really so?
There are many ways to look at success. Daniel chooses to look at it from the learning point of view. He wants to see teams learn, and run experiments. He mentions the book Lean Change Management by Jason Little as an inspiration for the experiment mindset. As Daniel puts it: being fast is good, but being able to change direction quickly is much better.
About Daniel Hommel
Daniel is a ScrumMaster and Agile Coach with a strong background in Software Engineering. His first touch point with Agility was starting to use the Extreme Programming practices in 2007. After some years of working more on the technical side in recent years his interest has shifted to facilitation, coaching, guiding continuous improvement and working with people in general. You can connect with Daniel Hommel on Twitter.
We can sometimes overwhelm the teams we work with by introducing too many methods. Anton explains how he likes to introduce methods to the team, by running experiments with the team to see if the method fits the team, and solves the problem they want to tackle. He also gives a critical advice on one of the most common anti-patterns for Scrum Masters: wanting to help too much.