Rahul Bhattacharya: Be flexible to avoid Scrum rejection by the team

In this episode, we learn about Rahul’s unusual route to being a Scrum Master, and how the initial focus on velocity led Rahul astray from what really affects a Scrum team’s performance.  

We then explore how beginner Scrum Masters can learn to focus on the right aspects from the start and to be flexible enough so that the team does not reject the adoption of Scrum.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.

Ines Stuppacher: How to help Team Lead and Product Owner collaborate

Scrum teams don’t exist in a vacuum, and in engineering-focused organizations, usually, the team leads are also engineers. This can cause problems when they need to collaborate with Product Owners. In this episode, we talk about such a team, and how Ines helped the team, the team lead and PO find better ways to collaborate.

About Ines Stuppacher

Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people.

You can link with Ines Stuppacher on LinkedIn or XING and connect with Ines Stuppacher on Twitter.

Ben Clark: How we can help Scrum teams get, and write better User Stories

Sometimes teams struggle to get their backlog healthy. When that happens, it is easy to complain about the PO. That won’t fix the problem. 

In this episode, we talk about how you can work with the teams to improve the quality of their stories, with our without a Product Owner in the room. 

In this episode, we refer to Model Storming, a technique to help teams explore several options for implementing stories. We also refer to Lucid Chart, a collaborative online tool for teams. 

We also discuss how, working on the “solution” may help clarify the acceptance criteria for the stories that are not clearly defined. 

About Ben Clark

Ben’s career has spanned from working assembly at Ford Motor Co, IT consulting, DSL Internet provider using wireless building-to-building antennas, systems administration and engineering, data center floor work, DevOps, cloud engineering, cloud architecture, scrum master, people-leader, and agile coach.

Ben is now an Agile Coach. 

You can link with Ben Clark on LinkedIn and connect with Ben Clark on Twitter.

Dragana Hadzic: How can we help Scrum teams in a large waterfall organization?

Scrum Masters need to sometimes face the Agile islands in the middle of large organizations. How can we react to that? How to address the team, and the stakeholders? How to do planning? There are many questions that Scrum Masters must answer differently when working with “island” Agile teams. 

In this episode, we explore how Scrum Masters can work with isolated Agile teams without having the teams to go back to waterfall. 

About Dragana Hadzic

Dragana is an agile enthusiast who believes communication is critical for success in everything, including software projects. A Scrum Master and an Agile Coach with broad experience in IT industry and different leadership roles. Passionate about everything that brings positive energy and enables people to achieve great results.

You can link with Dragana Hadzic on LinkedIn and connect with Dragana Hadzic on Twitter.

Isaac Garcia: what to do when the Scrum team just isn’t up to the task?

As Scrum Master, we are constantly paying attention to the team’s performance, and what can be done to help them progress. However, in some cases, the problems are beyond the Scrum Master’s reach. In this episode, we talk about the case when the Scrum Master must face the fact that the team just isn’t up to the task they have. What should a Scrum Master do in those cases? Listen in to learn about such a case, and the hard lesson Isaac learned about helping teams and their organizations when the team just aren’t up to the task.

In this episode, we refer to the book Coaching Agile Teams, by Lyssa Adkins.

About Isaac Garcia

Isaac is a passionate Agilist who builds teams with heart and walks their journey together. His driving goal in life is to invest in and impact world changers. He has a lot to learn but is enjoying the discovery in the journey.

You can link with Isaac Garcia on LinkedIn and connect with Isaac Garcia on Twitter

Gilson Souza: How to help Scrum teams understand what Scrum is really about

As Scrum Masters start their journey they only have the description of Scrum. However, even when a team we work with “does” all of the Scrum ceremonies, they may be something more important. In this episode, we analyze the case of a team that was “doing” scrum, but when Gilson left, they went back to the previous way of working. As Scrum Masters, we need to learn from those failures. We explore possible causes for this anti-pattern, and tips on how to help teams understand what Scrum really is about. 

About Gilson Souza

Gilson has worked with Scrum for over ten years, first as a software engineer, then taking in both roles of Scrum Master and Developer and currently 100% dedicated as Scrum Master. As a Scrum Master, he truly believes in empowered and self-organizing teams and works inside and outside of the team to achieve it.

You can link with Gilson Souza on LinkedIn and connect with Gilson Souza on Twitter.

David Gentry: The project management anti-pattern Scrum Masters fall into

Having a project management background is a good experience for Scrum Masters, however, it can also be a problem. In this episode, we talk about the possible anti-patterns that come with a project management background and how to avoid them in your role as a Scrum Master. 

About David Gentry

David Gentry is an Agile Coach and Scrum Master. He has served in a variety of other roles in his career including developer, data analyst, business analyst, quality analyst, and project manager. In his free time, he can be found playing bass guitar and interpreting how groove applies to life and agility. 

You can link with David Gentry on LinkedIn and connect with David Gentry on Twitter.

Long Suciu explains how a new Product Owner can derail a great team

Having helped a team reach a high-level of performance, it is easy to think that the team will continue to perform for a long time. In this episode, we explore how a team change (a new Product Owner) can reverse a positive trend, and impact the team’s performance. Listen in to learn why that happened, and how you can prevent it from happening to your team.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

Katy Cabral & Joseph Contreras: On the Scrum Master’s difficulty to step back, and let the team lead

When we want to help the teams we work with, sometimes we go too far. In this episode, we share a story of a Scrum Master that did just that, only to find out that it is critical that the teams take ownership over the solutions they choose to implement. No matter how much experience we have, as Scrum Masters, it is ultimately the team that needs to improve and live with their choices.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

You can link with Katy Cabral on LinkedIn.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

You can link with Joseph Contreras on LinkedIn.

Nick Vitsinsky on the Scrum Master’s failure to motivate the team

Scrum Masters work with teams every day. The way teams feel about the work they do is extremely important for them to be engaged and motivated. However, sometimes we overlook that and fail. In this very personal story by Nick, we learn about what happens when Scrum Masters overlook and even ignore the motivation and engagement of the team.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.