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.
Are you working on an “agile bubble”? Agile bubbles emerge in organizations, where one or more teams are allowed to use Agile, but all other teams are stuck in Waterfall. How do we help organizations that have these Agile Bubbles?
In this episode, we talk about the Cynefin Framework and how visualization helps groups understand how they can change.
Stanislava is not only a serious games facilitator and a team coach, but she also spends a considerable amount of time rock-climbing and hiking, traveling with her partner and son, and drawing zentangles.
This organization was proud of their achievements. However, their culture was not allowing them to collaborate, and move the organization to the next stage. That move was critical for them to survive a changing market.
In this episode, we discuss a non-conventional way to approach organizational change, and how that helped this particular organization. Listen in, to learn about why that approach worked and how you can apply that approach in your Scrum team.
About Susanne Taylor
Susanne is a transition coach, which translates to roles as: change management facilitator, organizational development consultant, scrum master, agile coach and community manager. (Often simultaneously.) Susanne has learned to be adaptable and resilient after having lived in Alaska, Japan, Taiwan and now Germany. She is passionate about accompanying people on journeys of transformation. (And she considers herself an introvert.)
Scaling the use of Scrum in any organization is not easy. In this episode, we discuss Izis approach to that challenge from the Scrum Master perspective. Scrum Masters in larger organizations end up having to work with multiple teams. We explore an approach that may help Scrum Masters serve more teams, while amplifying their impact.
About Izis Filipaldi
Izis’ mission is to help people to improve their knowledge and professional value inside organizations, applying the agile way of working. She has been working as an Agile Coach for more than 7 years, helping people to deliver products, developing an environment free of judgments where they can fail fast and learn faster. Continuous improvement of: people knowledge, product delivery, and work environment, are her 3 main focus on work. And she loves what she does!
Nick shares the process a team went through to move from Scrum to Kanban. Their initial goal was not to move to Kanban, but through small steps and focusing on improving they found themselves using Kanban even without trying.
Do you wish all change process would be this simple? Listen in to learn what steps Nick went through with the team.
About Nick Stewart
Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.
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).
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!