Working through an Agile adoption change in our organizations is always a difficult process, as not everyone will feel the same excitement about the adoption of Agile or Scrum. In this organization, the company had put up posters about Agile, but Wilson quickly realized that the Agile mindset was missing in the teams he worked with. This realization started a process of going through the change and Agile adoption process in a deliberate manner, and Wilson describes the process they adopted for that deliberate change management process.
Wilson is a pragmatic Scrum Master, he has over 15 years in Software development and has worked in different roles, from Support Analyst, Developer to tech lead. Wilson is from Portugal, with Indian origins and currently living and working in the UK with his wife and two daughters.
Jeremia and the team started to work with the c-level team to define a Vision and Mission that would clarify the purpose at his company. With that work, they were able to define a North Star, and start using OKR’s (Objectives and Key Results). He describes for us the process, and the lessons learned introducing OKR’s to focus the company on their purpose.
About Jeremia Riedel
Jeremia is an Agile Coach that describes himself as an Explorer, Enthusiast and Challenger.
There’s a big contrast between some of the Agile values and principles, and the approach that we see implemented when Project Management is the ruling approach to delivering software. Agile and Scrum require that leaders (including Scrum Masters) learn about servant leadership, instead of looking at teams as “school children” that must be managed, and controlled.
In this episode, we talk about the key differences we must be aware between the “old” approach to software development (based on project management ideas), and what Agile is all about.
Gurucharan Padki comes with 18 years of experience in the IT industry, of which he has spent more than a decade in the Agile world delivering products, programs and projects with focus on engineering and quality . He has played the role of product owner, scrum master and agile coach in multiple organizations across India and the world driving transformations.
Bent was working in a company that was facing serious economic challenges. This was not a case of Agile adoption, this was a case of changing to survive! Because of the economic challenges, the CEO decided to layoff some staff, and ask for Agile adoption immediately in all the teams. Bent helped the new teams start to work in a hardware business, with an Agile mindset and approach. This led to amazing improvements, and the company survived. Listen in to learn what was the approach, and steps the company took to the adoption of Agile in this crisis.
About Bent Myllerup
Bent Myllerup is a management consultant, organisational change agent and agile transformation coach with 20 years of personal experience in management and leadership. He holds a Master in Management Development (MMD) from Copenhagen Business School and a Bachelor in Science of Electronic Engineering. He was the first European Certified Scrum Coach and he is also a Certified Scrum Trainer.
As Yousef puts it: “Everything is a change process”. In an Agile transformation, there can be many dynamics at play, so we need to pay attention to finding out what is going on at all times. In this episode, we investigate how we can bring an Agile mindset to change, and learn what are the key change dynamics we need to work with.
About Yousef T. Fahoum
When starting out as a ScrumMaster and BA years ago Yousef passionately followed the ScrumMaster Podcast. Yousef is a SAFe Enterprise Coach at Elabor8 with experience implementing Agile and SAFe at some of the largest and most recognized brand leaders across industry domains in the U.S. and Australia.
While working with an organization in their Agile transition, Julie and colleagues recommended that they start with Kanban. Kanban would bring minimal disruption to the teams, and enable them to learn what Agile would mean in their context. However, there was a lot more to do before the teams were able to run a Kanban flow and start learning what Agile meant for them. In this episode, we explore not only how to introduce Kanban, but also what to consider when bringing Agile to a group of teams that are new to Agile.
About Julie Wyman
Julie Wyman has been working with Agile teams for over a decade and is continuously learning with and from them. She’s based just outside Washington, D.C., but has had the pleasure of supporting teams distributed across the globe and even experienced her own Agile takeaways all the way in Antarctica.
This is the story of a large bank that was going through an Agile transformation. The transformation was not going very well, and Jeroen worked with his colleagues to start a community. To kick start that process, they organized an open space event, to help the most interested people share what they were passionate about.
Steen shares the story of a transition from Waterfall to Agile. He describes an approach to change that starts with some small changes, and slowly increases the things under change with the aim to make the process feel more like a natural evolution. Listen in to learn about the process and the lessons that Steen learned along the way.
In this organization, the iteration reviews were not producing the needed impact. So Luís and the other Scrum Masters did an investigation to find out what was actually going on. They discovered several anti-patterns that we must also pay attention to as Scrum Masters. However, what they learned led them to focus on changing the culture underlying the reviews. Listen in to learn how they were able to define, and change the culture around iteration reviews.
About Luís Santos Silva
Luís is not your typical Agile Coach as he doesn’t have an IT background. He worked his way from a contact center up to Lean and Agile Coach and is now a Agile Coach team lead at OutSystems.
When Bevan started working with this organization, he heard the CEO say that the development was too slow. So the change started with a clear mandate, which Bevan and the team took on and started working with. They used tools like Value Stream Mapping, and went through a process to involve the teams in defining and ultimately overcoming their slowness. In this episode, we refer to Clean Language and Systemic Modelling by Caitlin Walker.
About Bevan Williams
Bevan is an Agile Coach & Trainer at Think Agile. His career has been driven by his passion of creating inclusive environments where people can be at their best.