BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

How do we get started with Continuous Delivery? Manuel suggests that we run a Value Stream Mapping session with all the teams involved in the release process to learn about the “current state” of the release process. 

We also review the most common challenges and blocks for teams that are starting to adopt Continuous Delivery. 

Read on to learn about the different motivations businesses have to adopt Continuous Delivery, and Manuel’s 3 steps from bi-weekly release to Continuous Delivery.

Continue reading BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3

Morten’s adoption story starts with a team at eBay Denmark. The team had started working in a more continuous mode, but there was a lot of “release friction” as Morten calls it. You are probably familiar with that friction: it takes a long time to release; the site needed to be “closed” for every release; the team would need to come in at night during the weekend, etc. 

That’s the reality for many teams. No surprise they prefer to release less often. In this segment, we explore that story, and also the steps the team took to go from “high friction” to “no friction”. 

Read more to find out how Dev and Ops are different and why that matters when adopting Continous Delivery.

Continue reading BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3

BONUS: Thierry de Pauw interview – Continuous Delivery for Scrum teams, Part 2

When Thierry got started, the team had troubles with version control, so he helped the team “commit to trunk”, and after that, it was much easier to adopt continuous integration. The build server quickly evolved into a continuous build pipeline. From there it was a small step to continuous delivery. 

Although not all stories are this easy for teams adopting CD, this story provides a striking example of how things that are “hard” for some teams, just become the “natural way” of working for others. What’s preventing your team from working this way? 

Read more to find what was Thierry’s most painful lesson about Continous Delivery adoption as well as all the resources he recommends for those wanting to dive deeper into the topic.

Continue reading BONUS: Thierry de Pauw interview – Continuous Delivery for Scrum teams, Part 2

BONUS: Dave Farley interview – Continuous Delivery for Scrum teams, Part 1

We talk about testing strategy; business benefits of Continuous Delivery; main challenges when adopting Continuous Delivery and resources to help you and your team get started.

Dave got started with Continuous Delivery in a project that sounds pretty much like any large project that is struggling. There were 200 people working on the project, the tests were written after the code, which inevitably led to a nightmare of brittle tests, high coupling between test code and implementation code.

Dave got interested in Extreme Programming and things started changing.

Read on to get access to all the resources Dave lists in the podcast.’

Continue reading BONUS: Dave Farley interview – Continuous Delivery for Scrum teams, Part 1

Reinald Kirchner invited Scrum Masters to a kick-off. What happened next was a surprise…

This story starts with an organization of about 300 software developers that wanted to “get agile”. The organization started by hiring Scrum Masters to help the teams, and the transition. So far, so good. So Reinald invited all the Scrum Masters in the organization to a kick-off for the Agile transition. What happened next was a surprise, and changed Reinald’s view of change management forever. Listen in to learn what was that surprise, and how you can avoid that problem in your own work.

About Reinald Kirchner

Reinald is active in the IT industry for more than 20 years. With agile methods and systemic project management he found his role as coach to inspire individuals and teams to learn, have fun and get better at what they want to do.

You can link with Reinald Kirchner on XING and connect with Reinald Kirchner on Twitter.

Dmytro Balaba: A SAFe adoption case study for Scrum Masters

This story starts when Dmytro faces the requirement to adopt SAFe. How to help teams learn about SAFe (is training sufficient?) and start working differently. The organizational legacy and inertia become obstacles, but the team of Scrum Masters at this organization was able to help the teams learn how to adopt SAFe. Listen in to learn how.

In this episode, we also refer to Lean Change Management by Jason Little, and 7 Rules for Positive, Productive Change: Micro Shifts, Macro Results by Esther Derby.

About Dmytro Balaba

Dmytro calls himself one of the most dedicated Scrum Masters/Agile Coach in the world 🙂 On his right-hand he has a tatoo with golden ratio, Fibonacci sequence. After almost 15 years of work in IT management Dmytro found himself balanced and happy. He’s been a full-time Scrum Master for more than 3 years.

You can link with Dmytro Balaba on LinkedIn and connect with Dmytro Balaba on Twitter.

Andy Grosman: 4-steps to help Scrum teams change

Even when Scrum Masters need to work with teams through a change process, they can be impeded by the organizational structures. In this episode, we talk about the Scrum Master who was part of a separate department but needed to help the team go through a difficult change. The key? 4 steps that Andy shares with us and get us started.

About Andy Grosman

Andy has spent the past decade in various industries from Fortune 500 to small and mid-sized companies including Healthcare, Finance, Training and has a background in sales/marketing. He currently leads a team of Scrum Masters in the digital space as well as coaches teams. He has spoken at regional conferences and Agile Meetups on team-building for Distributed teams, how to blend Agile and personal productivity strategies, and how to influence without Authority. He used to live by the Waterfall but got bit by the Agile bug and now is spreading the Agile Mindset wherever he goes.

You can link with Andy Grosman on LinkedIn and connect with Andy Grosman on Twitter.

Eddy Bruin: Simple serious games that can transform your Agile team in one single session

Retrospectives are a ceremony where we usually facilitate some prepared games or sessions to help the team gel. But is that the only place where we can use these games, and facilitated sessions? In this episode, we talk about Happy Salmon, a game that helped change a team in one session. They way people interacted, and related to each other was totally transformed. It may sound like a simple change, but this “serious game” can transform your team.

Listen in to learn about other serious games that Eddy uses when helping teams change. We also refer to the 2 truths and 1 lie game.

About Eddy Bruin

For many years, Eddy has been using serious games and learning metaphors to help teams and organizations move forward. He is an Agile and Test Coach with the mission to help teams deliver software people actually want to use while also enjoying their work. He helps teams to enable feedback loops continuously and likes to discuss all agile and test topics over a special beer. He loves to go to (un)conferences on serious games (for example Play14, Play4Agile), and also on Agile and Testing.

You can link with Eddy Bruin on LinkedIn and connect with Eddy Bruin on Twitter.

Jim Sammons: Communities of practice for Scrum Masters as a change practice

When working with change, one of the tools we use most often use is the “community of practice” pattern, where people get together and talk about the challenges they are facing, and discuss possible solutions. For Scrum Masters, this is especially important as we are – Jim reminds us – also leaders in our organisations and must set the example that others can follow. What are you doing to be an example of the change you are supposed to help implement?

About Jim Sammons

Jim is currently a Professional Scrum Trainer with and works with an amazing team at Insight as an Agile Coach and trainer for their clients around the world. His time as a Scrum Master was awesome and fueled his passion for agility at all levels.

You can link with Jim Sammons on LinkedIn and connect with Jim Sammons on Twitter.

Martin Lambert: Are you trying to change too much? 

Martin shares a story of an engagement which goal was to help a department adopt Agile. We review his first steps in that change, what he observed when the engagement started. We then discuss some of the tools he helped implement in that organization and how that was done.

In this episode, we refer to the Goal Roadmap by Roman Pichler, and one of the most critical skills for Scrum Masters working with change: to be able to distinguish what can be changed, influenced, and what cannot be changed. Are you trying to change too much?

About Martin Lambert

Martin’s an agile coach, trainer and scrum master. He’s a Northener making a living in the south of England, and finds great energy and sense of purpose from the agile movement during the second act of his career. Loves the hills and being out on a road bike. And to all the European listeners, he says: “sorry for you know what”.

You can link with Martin Lambert on LinkedIn.