When Moana was asked to help this organization, she found a common anti-pattern: the teams had reverted back to Waterfall after their previous Agile Coach left. This is a very common pattern, and we must learn how to deal with it. In this episode, we explore the context of that organization and also learn about the techniques that Moana employed to help that organization get back on the Agile adoption path.
In this episode, we refer to Lean Coffee, a technique you can use to help teams talk and open up about their situation.
About Moana Pledger
Mo started her career in education and program management before moving into digital delivery. She’s pretty sure she was a servant-leader before she had even heard the term. Her passion is to build healthy teams and foster the all-important relationship between business and team, which allows a safe space for the magic to happen.
A new team was formed, with new responsibilities. Now both that team and the others needed to adapt. How to help teams adopt and adapt to these new ways of releasing software? In this episode, we explore the DevOps change from the client team and provider team perspective.
Chelsie has been working as a Scrum Master in the Greater Boston Area for just over two years. She has experience working with both co-located and distributed teams developing on-premise and SaaS solutions worldwide. She is an avid lover of technology, dogs, and bullet journals, Chelsie loves finding ways to bring Agile outside of the office.
How do we help teams that are not developing software, but still are using Scrum? In this episode, we talk about how different the adoption process is for non-technical teams, and learn about the tool that Ellen developed to help teams adopt Scrum even when not working in a software development role.
About Ellen Santamaria
Ellen is a Scrum Master based in Berlin, and originally from Australia. She completed a Bachelor in Australian and later a Masters in Berlin, Germany where she works.
Ellen is passionate about startups, innovation, social entrepreneurship, new business models, organisational change management, and other topics. She also loves story-based video games, sci-fi, pétanque, and finding new ways of doing things.
Happy New Year Scrummies! 🙂 Today marks the first day of 2020, and we have a great episode for you.
In this episode, Valeria shares a story of a company that wanted to go towards Continuous Delivery and Delivery on Demand. The main challenge was to help the developers and the teams understand the difference in mindset. For that Valeria took up a few questions she would repeatedly ask the team such as: “can we release this right after you finish it”?
What questions do you have for your team when helping them through a change?
Listen in to learn what other questions and techniques Valeria used in that process.
Valeria has worked as a Scrum Master for 4 years. She has experience with both Software development and non-software development Agile teams. When asked what she does for a living, Valeria replies: “I build teams!” And she does it by focusing on building relationships first. As Valeria says: “all my teams will tell you that I like talking about the feelings :-)”
From her early start with Extreme Programming to learning how to integrate testing with Continous Delivery, we explore Leena’s story and describe some of the most important lessons she collected about adopting CD/CI.
Read on to learn what were Leena’s main lessons, as well as the main challenges teams face when adopting CD/CI.
Wouter started his Continuous Delivery journey as an Extreme Programmer in his first years of engineering experience. He shares the story of how, as a team, they sat together with the operations department to learn how they developed their software. Thanks to that, they radically changed their build system to export the kind of packages that operations needed. A brilliant story that also illustrates the adage: “Your first customer is the next step in the process!”
Read more to learn why testing is such a key skill and technical area when adopting Continuous Delivery.
Chris started her Continuous Delivery in a small agency, nurturing a build server that nobody cared for. That gave her an insight that is not very common: taking care of the build server was a very practical way to help and care for the team’s success. It was a practical tool that the team needed, but no one was looking after. It was a concrete way to help people.
Read more to find out how trust plays a key role in Continuous Delivery adoption, and to read Chris’ recipe to get your team started with CD.
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.
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.
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.