Scrum Masters can be change catalysts, and often they become an active part of Agile adoption at their organization. However, even motivated, energetic Scrum Master can burn out. Change is a long process, and it can’t keep going if only you are working on it. In this episode, we talk about the importance of creating a “guiding coalition” to ensure that change takes hold and progresses in an organization.
About Eduardo Ribeiro
Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.
He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.
One rainy Monday, a developer runs a script. The whole database is wiped out, and there are no backups. What can we learn from this story? Scrum Masters must help teams prepare, and sometimes recover, from disasters. This is such a story. We also discuss how we can prepare our teams to avoid catastrophic failures.
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
Prioritization is not a simple, or easy task for Product Owners and teams. Sometimes, the teams focus on what they want to work on, sometimes on what is easy to do, but those are prioritization anti-patterns.
As Scrum Masters, we must assess the prioritization practices of our teams. When necessary, we must help them adopt new approaches to prioritization. Henrique shares one of those times with us.
About Henrique Centieiro
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
QA teams are isolated in many organizations. When Scrum Masters work with those teams, the first challenge is to help them see beyond their silo, and create a definition of success that includes working and collaborating with other teams.
In this episode, we talk about a QA team, and how they were able to transition to a more collaborative way of working, which – for the first time – included other teams.
About Ajeet Singh
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.
When Scrum Masters help teams go through a change process there are few things more important than helping teams “take over”. In this episode, we explore the consequences of not helping the teams take over the change process, and also discuss approaches and tools Scrum Masters can use to help teams hold themselves accountable.
About Tilman Rumland
Tilman Rumland is an agile coach, expert speaker, and productivity enthusiast. He just released his new workshop series: “getting shit done that really matters to you”. As a scrum master, he implemented agile structures to agrilution, a small scale vertical farming startup, ranked on the Forbes TOP 100 innovative German Startups. (www.agrilution.com)
Helping an organization adopt Agile is like facing a house, with people inside, and getting an invitation to get it and lead the people in the house. Not an easy task for Scrum Masters. In this episode, we explore that metaphor and talk about the tools and approaches we can use when we are the outsiders, that need to bring change into the organizations and teams we work with.
About Raluca Mitan
Raluca calls herself a recovering Project Manager that discovered Agile and somehow the “good, the bad and the ugly” received distinctive names.
She loves her job and practices Accelerated Learning to achieve her Goals (to become a Scrum Master Trainer for Scrum Alliance, to write a book, acknowledged as an Inventor, share her ideas to the world and with her daughters).
And maybe someday to be a Bonus Podcast guest on the Scrum Master Toolbox Podcast :).
Doug has been an agilist since before it was cool, as his first agility client can attest. He is currently the Director of Agile Development & Coaching at Wisconsin-based Flexion inc., leading agile teams that serve both private and public sector clients. His current hobby is thinking beyond agility, to antifragility.
When teams that are new to Scrum start adopting a new way of working, there’s a window of opportunity to help them. When they are still new and recognize that they need help. In this episode, we review the story of a team that had a difficult project ahead, and how Anja and the rest of the organization went about finding a way to help the team.
A reminder that teams sometimes ask for help, and that’s the right time to help them!
About Anja Bonatto-Minella
Working with agile and scrum only since for a year Anja still considers herself a scrum-beginner. Before starting at her currrent job which brought her into the world of agile, she studied physics and then worked in research for several years.
When it comes to changes, in agile environments there’s one change that many of us need to be directly involved with. That’s the move from functional teams, to multi-skilled, T-shaped, cross-functional teams.
In this episode we talk about how Scrum Masters can enable, and support that change. From how to introduce the idea, to how to get started, and ultimately how to enable the self-organization of teams that ensures team’s commitment to the change.
Jen and Jamie (sweet and salty as they call themselves) are passionate about people, relationships, leadership, accountability, common sense, and getting sh*t done! Ultimate dream job would be to coach individuals, teams, and organizations in discovering and cultivating potential and doing things better by identifying people’s strengths, passions, and skill sets, along with effective processes and strategy to build a strong, healthy culture.
Nisha likes to start with a plan. But her approach is very adaptive. It is not about following the plan, but about kick-starting the change.
Listen in to learn how she addresses teams and involves them in the change process.
About Nisha Balwatkar
Nisha started her career as a programmer for the love of logical reasoning and technology and soon found herself trapped in the mismanagement of software teams affecting the work and efforts put in by the teams. She always had a feeling she could fix it and eventually moved to be a scrum master. She enjoys helping out teams and see the joy of success by identifying and fixing small things.