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 :-)”
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.
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.
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.
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.
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.
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 Scrum.org 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.
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”.
In large organizations, Agile adoption is often a long and complicated process of constant expectation management for both stakeholders and Scrum Masters. In this episode, Dirk shares with us his experience with the Scrum Master Journal, a tool that helps him reflect and survive large scale adoption.
Dirk also has 9 other tools to share with us that will help your Scrum Master journey.
In this episode, we refer to Battle Mapping and some practical tips on how to get help from the other Scrum Masters.
About Dirk Fabricius
Dirk has worked in jobs with IT focus for 20 years. He has had the roles of Project Lead, Developer (Backend), Product Owner and Scrum Master. He’s also been a Teacher in Public Schools for 7 years.