Miguel Santos: in Agile there’s NO one-size-fits-all solution

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.

You can link with Miguel Santos on LinkedIn and connect with Miguel Santos on Twitter.


Richard Kasperowski on why hiding information creates conflict

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.

In this episode we refer to the original eXtreme Programming Explained book, by Kent Beck and Cynthia Andres.

About Richard Kasperowski

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

You can link with Richard Kasperowski on LinkedIn and connect with Richard Kasperowski on Twitter.

Krisztina Sajgo-Kalo on a Project Management anti-pattern: leading the conversation

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.

You can link with Krisztina Sajgo-Kalo on LinkedIn.

Viyoma Sachdeva’s tip for new Scrum Masters: Experiment to learn what works!

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.

You can link with Viyoma Sachdeva on LinkedIn and connect with Viyoma Sachdeva on Twitter.

Susan McIntosh on what psychological safety means IN PRACTICE, no buzzwords

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.

You can link with Susan McIntosh on LinkedIn and connect with Susan McIntosh on Twitter.


Sebastian Hitzler and the case of the missing Product Owner

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.

In this episode, we refer to the Oikosofy Story Mapping Workshop facilitation guide.

About Sebastian Hitzler

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.

You can link with Sebastian Hitzler on LinkedIn and connect with Sebastian Hitzler on XING.

Barry Overeem from Project Management to Scrum Master

There are many paths to the Scrum Master role. One that is quite common in the IT industry is that of moving from Project Management to being a Scrum Master. As you’d expect there are quite big differences. In this episode, we talk about those differences and what Project Managers must take into account when changing their role to Scrum Master.

In this episode, we talk about a paper that Barry authored where he describes the 8 stances of a Scrum Master. A good list to have in mind, especially when transitioning from Project Management to Scrum Master.

If you are on your journey from Project Management to Scrum Master you might be interested in this episode with Danilo Tambone who made that transition himself!

About Barry Overeem

Barry, the learning facilitator as he calls his blog, considers himself a 100% Scrum Master. It’s such a comprehensive and interesting role that he gives it his full focus and keeps learning and discovering new aspects every day!

You can link with Barry Overeem on LinkedIn and connect with Barry Overeem on Twitter.

You can also check the many resources that Barry Overeem shares on his website!

Joe Anderson on the role of Courage as a Scrum value

In a big agile transformation, there are many stakeholders, many expectations that affect our work as Scrum Masters or Agile Coaches. In those environments, Courage becomes a critical value for us. Joe explains his story of failure and the role that Courage can take in helping you avoid the anti-pattern that Joe describes in this episode.


About Joe Anderson

Joe is a Scrum Master at a small travel technology company with a passion for bringing out the best in people and building deep relationships. He works hard to foster an environment of safety, fun and learning with a focus on relentless improvement.

You can link with Joe Anderson on LinkedIn and connect with Joe Anderson on Twitter.

Arif Bobat on why sometimes you need to get fired as a Scrum Master

Working with a team that had very little going for them, Arif tried his best. He tried to raise awareness of the problem, he tried to help the team improve, he raised obstacles to management. Was that enough? Listen in as Arif describes his journey in an impossible situation, and explains why – sometimes – you need to get fired as a Scrum Master otherwise you are not doing your job!

In this episode, we discuss the GROW model of coaching.

About Arif Bobat

Arif is an experienced Scrum Master with a passion for enabling teams to achieve their potential, Arif loves challenging situations. In the last 5 years, he has been made redundant twice and fired twice. He is not afraid of speaking up when he sees anti-patterns and/or a lack of willingness to change behaviors.

You can link with Arif Bobat on LinkedIn and connect with Arif Bobat on Twitter.

Donald Ewart reminds us: you need to be setup to be Agile!

We sometimes face situations where the teams are not ready to be Agile. In this episode we discuss such a story and talk about what we need to have in place to even get started with Agile. This is a great reminder that we should not try to make all teams Agile or all projects Agile. First we need to discuss and agree on the conditions we need to get started on our Agile journey.

In this episode we talk about the book Agile Project Management with Scrum by Ken Schwaber.

About Donald Ewart

For more than 10 years, Don has been a scrum master and coach working in different sectors in London and across the UK as an independent consultant.

With a background of 10+ years in several development roles for web and finance systems, Donald has a good technical knowledge of modern development techniques, and can quickly build rapport and respect with development teams, understanding their issues and helping them to find the right solutions.

You can link with Donald Ewart on LinkedIn and connect with Donald Ewart on Twitter. You can also find out more about Donald’s work in his website.