When we start as Scrum Masters, there’s a lot of things we don’t know yet. Not only are we not able to see the anti-patterns, but we also don’t know how to react to the problems we face. Scrum has in itself a set of patterns that help us when we are starting out, but sometimes we need more than that. In this episode we explore the story of when Leonardo was just starting as a Scrum Master. The anti-patterns he saw, and the steps he took after he learned some hard lessons.
About Leonardo Bittencourt
Currently Leonardo is a Scrum Master at Equifax Ireland. Focused on building high performance teams through Agile and/or Lean adoption, he is an enthusiastic about Lean and Agile mindset in the Software Development industry as the transformation agent to create great working environment as well as products that matters.
Some of us are lucky to have a good experience with our first try at using Scrum. Some, even more lucky, can get great results during the first 2, 3, 5 or more times they help a team adopt Scrum. But, whether we like it or not, eventually we will face a time when Scrum just doesn’t work as we expect. What do do then? Listen in to learn what Ryan went through in just such a situation and what he did to recover from that.
About Ryan McCann
Ryan is a former waiter, car detailer, line worker, cemetery worker, intern, financial analyst, tech support rep, team lead, QA manager, Scrum Master and Product Owner. Current husband, father, school board member, community volunteer and agile coach. He believes in building trust and social capital, which is not easy for any of us (himself included)…Ryan does his best everyday to help teams make this happen.
In a high stakes project, like the one Natalie describes, it is tempting to start focusing on the schedule from the start and spend time trying to predict how long things will take. But is that the best us of our time and talents as Scrum Masters? Listen in to learn what Natalie learned about making projects a success that require very little focus on duration or effort estimation.
In this episode we discuss the book NoEstimates, How to measure project progress without estimates.
About Natalie Cervantes
Natalie is a Certified Scrum Master and Agile Coach with over 12 years experience working with both veteran and new agile teams. Her experience spans everything from mobile and embedded systems to enterprise scale website projects with a client base that includes Microsoft, Amazon, Coca-Cola and many others.
Working with a team that is under pressure from someone high-up in the organization is never easy. How about if that person is also changing their mind regularly? And interrupting the team with new ideas all the time? In this episode we explore such a situation. The VP is constantly asking the team for new things, interrupting their work, and requesting everything in very short timeframes. How can we help as Scrum Masters? Ask the right questions. Listen in to learn about how to ask the right questions.
About Tanner Wortham
www.SpikesAndStories.com. He’s helped many organizations in their journey toward agility. He’s been accused that his military training would mold him into a rigid, unmoving Scrum Master, but nothing could be further from the truth. What civilians call agile, the Corps calls leading Marines, and it’s through his experiences as a Marine that he derives most of his insight as a Scrum Master.
There are plenty of available frameworks, processes, models and other “processed” Agile packages. So many that the distracted Scrum Master can be forgiven for thinking that one of those will work for his team. Unfortunately that’s not the case. Listen to this episode, where Miguel explains how he came to the realization that Agile adoption is just the start of the Agile journey, and what you can do about it as a Scrum Master.
About Miguel Santos
Miguel is a Brazilian living in Germany and currently Scrum Master for two teams at NewStore. He believes that there is no single methodology (agile or not) to lead projects and teams to success. Because of that, he would like Scrum Masters to be less biased when working with their teams.
As team members, Scrum Masters, employers, managers we tend to keep a lot of information confidential. But can we really function well as teams when the default behavior is to hide information? In this episode we explore the consequences of hiding information from the team or your colleagues.
Richard is a speaker, trainer, coach, and author focused on high-performance teams. Richard is the author of The Core Protocols: A Guide to Greatness. He leads clients in building great teams that get great results using the Core Protocols, Agile, and Open Space Technology. Richard created and teaches the class Agile Software Development at Harvard University. Learn more and subscribe to Richard’s newsletter at www.kasperowski.com.
Many Scrum Masters transition from a Project Management position. This transition is not easy. It requires a change in stance (towards facilitation, instead of management) which is not always easy to achieve. In this episode, we talk with Krisztina about one of the common anti-patterns that new Scrum Masters face: they lead the conversation. Listen in to learn about how Krisztina detected and later changed that pattern to one that works much better for the team and delivers better results in the end.
About Krisztina Sajgo-Kalo
Krisztina is a Senior IT manager with experience in several aspects of IT management on different levels as well as methodologies used. Originally from Hungary, she has worked in many countries. First as a tester, then a project manager, test manager, and many other roles.
As new Scrum Masters, we are sometimes overwhelmed with all the things that require our attention. It’s ok! You are not alone. When we start looking at the problems the teams are facing it is easy to be driven to act immediately. After all, many of us have been there before. However, there’s an issue with this. First is that we don’t know what the team has already tried. They can tell us their view. So we must first listen. Second, and most important, we don’t know what will actually work. So let’s experiment. In this episode, Viyoma shares how she helped a team learn how to experiment and solved a serious blocker with the team’s help.
About Viyoma Sachdeva
Viyoma has over 11 years of experience in Software and Product development across different domains and phases of software development cycle. She is a certified Scrum Master and Product Owner and has worked in an Agile delivery model for the last 6 years. Her experience includes many different domains like Marketing, manufacturing, retail and Public sector and she has worked in a patent of Epidemic disease predictions.
Viyoma believes that the Agile mindset and practices are keys to solve complex problems.
The story that Susan has to share with us starts off, as usual, a team, struggling. What happened next? Susan acted in a way that made her understand what psychological safety means in practice. No mumbo jumbo, no buzzwords. What it means for you! Listen in and share the journey with Susan. You’ll learn a lot!
About Susan McIntosh
Susan McIntosh is an agile coach and scrum master, especially interested in training and agile transformations – both fast and slow. She finds analogies to improving workplace culture in her experience in theater, teaching, cooking, and parenting. Susan is an active participant in the agile community in Denver, Colorado.
Product Owner is a critical role in Scrum. When it is missing there’s many things that don’t work. Prioritization, answering questions about the product quickly, you name it. But what is a Scrum Master to do? Listen in and explore with us the many anti-patterns that emerge when the Product Owner is missing in a Scrum team.
Sebastian works as a dedicated Scrum Master for two delivery teams at Fidor Solutions in Munich. The team members are from 10 different countries and spread into 3 different locations in Germany, Spain and Ukraine. Fidor enables clients to become digital banks based on their ecosystem. Sebastian also works with the wider organization to help them transform with lean and agile.