This episode is about the story of changing an airport company to use Agile. This provides a great background to talk about the essence of Agile, and the management practices that go with it. We discuss how to avoid the “buzzword” resistance to change, and how to engage a team that has never heard of Scrum before.
About Joost Mulders
Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.
Many Scrum Teams will, at some point, go through the process of improving how they run the QA process. Many start with the QA at the end of the Sprint, and then bump into the hard wall that is the timeboxed end of the Sprint. The consequences are many, from stories that spill over to the next sprint, to stressed out testers. In this episode, we walk through a change process that took a team from testing everything at the of the Sprint to testing much earlier and reducing the stress on the testers.
About Remy Fletcher
Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.
In this episode, we explore the story of a team that was starting to adopt Agile. We discuss the successes, and also the need to accept Work-In-Process (WIP) limits before the team can succeed.
We discuss a possible set of steps you can follow to introduce WIP limits to your team.
About Micah Stamper
Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master.
Rahul and Markus, another Scrum Master were helping the QA team move from QA at the end to a more involved QA approach, where QA engineers were to be involved earlier in the process. As you’d expect, this was not an easy change. How did they pull it off? They started by thinking that change happens as a result of new actions as described by John Shook and helped the QA’s and the teams experiment with new approaches. In this episode, we also talk about the importance of accepting that not everybody can accept certain changes, and how that affects your change management efforts.
Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback.
He is also the host of a podcast about Agile, called the Agile Atelier.
As more and more companies adopt OKR (Objectives – Key Results) as a management practice, it is critical that Scrum Masters understand how that tool is used in their organization. In this episode, we discuss how OKR’s can totally derail a company, and how Scrum Masters can join the process and help it improve. This is especially important because OKR’s – when effectively used – will have a large influence on the teams we work with.
About Ines Stuppacher
Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people.
When an organization starts adopting Agile, the temptation is to organize a “transformation” and to focus on the change process. In this episode, we explore what happens when we focus on small changes, grass-roots change.
How we can slowly get more and more teams on-board, and ultimately avoid a large and difficult transformation.
About Ben Clark
Ben’s career has spanned from working assembly at Ford Motor Co, IT consulting, DSL Internet provider using wireless building-to-building antennas, systems administration and engineering, data center floor work, DevOps, cloud engineering, cloud architecture, scrum master, people-leader, and agile coach.
Of the many types of changes we need to go through, scaling up the use of Scrum may be one of the most common at the moment. When we go from one team using Scrum, to many teams collaborating and using Scrum together many things change.
In this episode, we talk about some of the challenges that scaling up Scrum brings, and how we – Scrum Masters – can prepare for those, so that we can help both the teams and the organization benefit from Scrum in larger projects.
About Dragana Hadzic
Dragana is an agile enthusiast who believes communication is critical for success in everything, including software projects. A Scrum Master and an Agile Coach with broad experience in IT industry and different leadership roles. Passionate about everything that brings positive energy and enables people to achieve great results.
It is a scary change, when Scrum Masters must go from focusing on the team to focusing on the organization. However, this is something that most Scrum Masters will have to face in their career.
In this episode with Isaac Garcia, we learn about the circles of influence that help us understand what we can influence (and what we can’t); we discuss Causal Loop Diagram, a tool to understand organizational dynamics that affect our teams; and the ideas behind “flow”, a way to view organizations that focuses on allowing the teams to find their performance levels.
For more on Causal Loop Diagrams and their use for Scrum Masters, check this episode with Antti Tevanlina where we explore how you can use CLD’s to understand the causes of the problems affecting the team.
About Isaac Garcia
Isaac is a passionate Agilist who builds teams with heart and walks their journey together. His driving goal in life is to invest in and impact world changers. He has a lot to learn but is enjoying the discovery in the journey.
It’s common to hear the “build a guiding coalition for change” mantra. It is part of a famous change management model (The Kotter 8-step change model), and a practical tip that we all can benefit from. However, how is that done in practice? In this episode, we talk about an Agile transformation at a large, distributed organization and how Gilson and others were able to build that guiding coalition for change.
Gilson has worked with Scrum for over ten years, first as a software engineer, then taking in both roles of Scrum Master and Developer and currently 100% dedicated as Scrum Master. As a Scrum Master, he truly believes in empowered and self-organizing teams and works inside and outside of the team to achieve it.
There’s often a misconception in certain organizations that Agile is just shorter waterfall projects. That’s very far from reality. In this episode, we talk about how David’s team showed – by example – the power of an agile way of working, and how that inspired other teams to change.
About David Gentry
David Gentry is an Agile Coach and Scrum Master. He has served in a variety of other roles in his career including developer, data analyst, business analyst, quality analyst, and project manager. In his free time, he can be found playing bass guitar and interpreting how groove applies to life and agility.