Sebastian Reverso: Drawing people to change, instead of pushing change onto them

When introducing change to an organization, the way we present ideas and involve people become key aspects to our success. In this episode, we talk about how introducing ideas in different ways may have radically different results. We identify some approaches that have worked well, and we talk about the concept of “baby steps”, or relentless movement towards a direction. Finally, we discuss how to involve the team members directly in that process. As Scrum Masters we don’t need to tell the team what to do, they know. If they understand why the change is necessary, they can come up with the right steps.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Jaime Bartol: Introducing Scrum to a marketing team

In this episode, we discuss how Scrum Masters can introduce Scrum to non-software teams. Specifically, we share the story of a marketing team, and how Scrum was introduced. 

We discuss the differences between Scrum for Software and Scrum for non-software teams. We share tips on how to introduce Scrum to non-software teams. Finally, we review how Agile principles can help Scrum Masters find the right practices for non-software teams.

About Jaime Bartol

Jaime has been a ScrumMaster/Agile Coach for 6 years with experience in large organizations as well as startup teams! She has worked with frontend and data engineering teams and even brought Agile to awesome marketing teams! Jaime’s passion is about teams and using Agile/Scrum fundamentals to elevate efficiency, productivity, and joy!

You can link with Jaime Bartol on LinkedIn.

Rachel Martz: The steps to adopt Lean Product Development

In this episode, we discover the approach that Rachel has found when she needs to help an organization adopt Lean Product Development. It’s not an easy process, but Rachel breaks it down for us. Through her experience, we learn a path that may help us when we help the organization we work with.

About Rachel Martz

Rachel has been in digital product development for over 20 years, having performed every role imaginable. She entered the agile space 13 years ago, doing hands-on product strategy and development modernization. 

Rachel is in the data and analytics industry at the moment and loves being a Scrum Master because it’s the most impactful role she can have for helping improve people’s lives.

You can link with Rachel Martz on LinkedIn

Angeliki Hertzfeldt: How to help Scrum teams continuously improve

The role of Scrum Masters is to help the team improve. Those improvements are changes that we also need to help the team understand and implement. In this episode, we talk about what Scrum Masters can do to help the teams continuously improve and change.

About Angeliki Hertzfeldt

Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.

You can link with Angeliki Hertzfeldt on LinkedIn and connect with Angeliki Hertzfeldt on Twitter

Joost Mulders: Adopting Agile in an airport company, the non-IT Agile adoption story

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.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Remy Fletcher: Moving from testing at the end of the Sprint to continuous testing

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.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter.

Micah Stamper: How to introduce WIP limits to a Scrum team

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.

You can link with Micah Stamper on LinkedIn and connect with Micah Stamper on Twitter

Rahul Bhattacharya: a new change management model by John Shook

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.

In this episode, we also mention Test-Driven Development and the concept of Pi-Shaped Skills.

About Rahul Bhattacharya

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.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.

Ines Stuppacher: How Scrum Masters can help deploy OKR’s in their organizations

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.

You can link with Ines Stuppacher on LinkedIn or XING and connect with Ines Stuppacher on Twitter.

Ben Clark: Agile adoption with a grass-roots strategy

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.

Ben is now an Agile Coach. 

You can link with Ben Clark on LinkedIn and connect with Ben Clark on Twitter.