Dov Tsal: What to do when Scrum just isn’t a fit for the team?

What are the necessary conditions for us to successfully implement, and benefit from Scrum? That’s a question that we explore in this episode, where Dov shares a story of a team that worked isolated from the rest, and which did not have a real Product Owner. In this episode, we also discuss what we should do when Scrum isn’t the right fit for the conditions around the team. 

About Dov Tsal

Dov Tsal is a versatile agile coach, scrum-master, change-agent, and enabler, helping companies teams, and individuals to make an impact. Dov is also the creator of the #MeetingSpicer, a coaching tool to hack meeting culture. He is also the co-creator of The Agile Tao Podcast about understanding agility through the Taoist prism.

You can link with Dov Tsal on LinkedIn. 

Kyla MacDonald: Failing to change a team, a critical lesson for Scrum Masters

When Kyla worked with her first Agile team, she got lucky. The team was filled with great people, who were curious, and willing to change and learn. Later on, when working with another team, she had the same expectations. However, that team was not like the first. They thought Agile was a waste of time. This setup Kyla for a very important lesson that all Scrum Masters will have to learn, sooner or later. 

About Kyla MacDonald

Kyla imagines a world where the talk at Friday drinks is all about the great things we achieved in the week, what we learned, and what we can try next. As she puts it, people who find satisfaction, meaning, fun, and growth in their work, will naturally be in a better position to find the same in their home life. The thing that excites Kyla the most about agile is how concepts and principles apply to any and every area of your life. Which for her is running, paragliding and life on her hobby farm (they call it a lifestyle block in NZ).

You can link with Kyla MacDonald on LinkedIn and connect with Kyla MacDonald on Twitter. 

Philip Rogers: Helping build a global software development operation with Agile teams

Philip was helping an organization setup an offshore operation by helping a team startup. That caused communication problems as the times the teams could be at work did not have sufficient overlap. But there were many other anti-patterns that came from having 2 teams on opposite sides of the planet. 

In this episode, we talk about how to setup a global software development operation, and share some of the practices that can help, even when teams are globally distributed. 

About Philip Rogers

Phil, is a father of four children and volunteer paleontologist at the Smithsonian National Museum of Natural History. He is also an “agile whisperer” (coach) who has worked with scores of teams in the spirit of continuous learning, continuous improvement, and simply finding creative ways to collaborate and have fun in the workplace.

You can link with Philip Rogers on LinkedIn and connect with Philip Rogers on Twitter.

Evelien Acun-Roos: How leadership sometimes pushes Scrum teams back into Waterfall

Evelien was asked to help an organization transition to Agile using Scrum. There were multiple teams in that organization which Evelien and others started working with. With a mix of training and hands-on support they started working with all the teams. However, later it became clear that leadership in that organization was not aware of what Agile or Scrum meant in practice. Leadership started to ask for the same things, and in the same way that they always had. Effectively pushing the teams back into waterfall!

We discuss what we can do, when starting to work with a new organization, to help leadership understand what changes when we adopt Agile.

About Evelien Acun-Roos

Evelien Acun-Roos is an experienced Agile Trainer at Xebia Academy, Professional Scrum Trainer at and a Certified Trainer for “Training from the Back of the Room”.

You can link with Evelien Acun-Roos on LinkedIn and connect with Evelien Acun-Roos on Twitter.

Wouter Gheysen: How to find the “right” sustainable pace for your Scrum team

One of the challenges for Scrum Masters is to know when the team is already working at their pace. The idea of sustainable pace is that we help the team find and slowly improve their pace, rather than do the “death march” sprints that can destroy the team’s morale and productivity. In this episode, we talk about how we may be able to help the teams we work with find their pace, and how to know when we are pushing them too hard (and too little). 

About Wouter Gheysen

Wouter is a creative generalist with a broad area of interest beyond agility, a focus on people, and working with teams. He is a coach, guide and life long learner with a keen interest in facilitation, design thinking and systemic coaching.

You can link with Wouter Gheysen on LinkedIn and connect with Wouter Gheysen on Twitter. 

Kamal Hans: Beware of the Scrum-mom, a Scrum Master anti-pattern

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website:

When Scrum Masters want to help their teams, they put a lot of focus on working with the teams, but sometimes that may be the wrong thing to do. How do we know that? In this episode, we talk about when the Scrum Master does “too much” and creates a dependency from the team towards the Scrum Master, as well as what can happen when teams are no longer able to take ownership of their ways of working. 

About Kamal Hans

Kamal Hans believes people are capable of incredible things if they have the support they need. He is at his best when he gets to connect people with each other and their vision, create a structure of support, build a system to achieve their goals to accomplish bigger things than themselves. As an Agile Coach and disciplined facilitator, he has worked with global organizations like Ericsson, and Bose to name a few. 

You can link with Kamal Hans on LinkedIn and connect with Kamal Hans on Twitter

Nagesh Sharma: Critical conditions necessary for Scrum teams to succeed

This was a dedicated team that wanted to succeed. However, the conditions were not in place for them to succeed. These conditions we talk about in the episode, are a great checklist for Scrum Masters who want to assess the conditions for success in their team. Through the story that Nagesh shares, we explore what we – Scrum Masters – can pay attention to, so that we help our teams put the right things in place to be able to deliver successfully. 

About Nagesh Sharma

Nagesh is a Professional Scrum Trainer by, He is Co-Founder & CEO of Flowsphere India. His mission drives him in increasing the joy and accomplishment people feel with agile ways of working. Nagesh is a Management 3.0 & collaboration Superpowers Facilitator. Trained more than 3000 people across the globe and an active speaker at various international conferences.

You can link with Nagesh Sharma on LinkedIn and connect with Nagesh Sharma on Twitter.

Rob Cooper: How to help teams that are stuck between Waterfall and Scrum

This team was stuck halfway between Waterfall and Scrum. The team was working in Sprints, but they had a 13-week development cycle, followed by a 13-week testing cycle. The separation of testing from development caused several issues, and the company tried to remedy that by asking developers to test in an attempt to speed up the testing cycle. However, things didn’t go according to plan. Listen in, to learn about what happens when organizations separate testing from development, and what we – Scrum Masters – can do to help teams that are in that position. 

About Rob Cooper

Rob is a Lead Agile Coach at Sainsbury’s, focusing on how the whole business uses Agility. Rob is an experienced Agile Coach at Enterprise, leadership, and team levels. In this career, he worked with change in organizations using a range of frameworks, including Scrum, Kanban, SAFe & LeSS approaches. He’s experienced in program & Project Management and has helped multiple teams transition from waterfall to Agile. 

You can link with Rob Cooper on LinkedIn.

Susannah Chambers: How to Scrum Master two teams, and survive!

This story starts with Susannah working with two teams, in her role as a Scrum Master. This lead to her feeling torn between the two teams that she wanted to help. Multitasking and having to attend multiple ceremonies made her feel stressed and unsure about the best way to help the teams. How can a Scrum Master overcome the challenges of this situation and help the teams? Listen in to learn the important lessons Susannah took from this situation.

About Susannah Chambers

Susannah seeks joy and empowers teams to articulate how they add value. She is a Certified ScrumMaster and Agile Team Coach for 3 software development teams for a major retailer. Susannah is also a Personal Agility Recognized Ambassador for the Personal Agility Institute and she helps people identify what really matters.

You can link with Susannah Chambers on LinkedIn and connect with Susannah Chambers on Twitter.

Serge Huybrechts: The right way to bring up blockers and problems to leadership

When Scrum Masters find blockers or problems in teams, and even in organizations, they need to think what’s the right approach to share those insights. The approach we select must be fit to the organization and the prevailing culture. In this story, we hear how Serge found a “tabu” that, when brought up, caused the organization to block it, and effectively invalidate the work Serge had done. 

About Serge Huybrechts

Serge is a Scrum Master, Agile coach, and trainer with a long background in IT Service Management. He considers himself a guide for continuous improvement where Agile, Scrum, and Kanban are the vehicles. Serge loves Agile because of its focus on people and learning resonates with him. 

He also calls himself a bulimic reader and very passionate about music.

You can link with Serge Huybrechts on LinkedIn.