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.

Mili Shrivastava explains how Scrum Masters can help teams finish more stories in a Sprint

Often, teams get too eager to deliver. So eager, they end up planning too much for one Sprint. What usually follows, is that teams leave a lot of stories unfinished at the end of the Sprint, which in turn affects the next Sprint.

In this episode, we explore how Scrum Masters can progressively get the teams to understand what creates that anti-pattern and how to overcome it so that teams start finishing more, if not all, the stories during the Sprint.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn.

Jassy (Jan-Simon Wurst): the challenges with moving from developer to Scrum Master

When we move from a developer role to a Scrum Master role, many things change. In this episode, we talk about our relationship with our colleagues (the good and the bad), as well as the critical aspect of learning to ask for feedback from the team.

About Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

Bradley Pohl: how to help PO and team collaborate better

The relationship between Product Owner and the team is critical. So critical that if it does not work, it has the potential to derail the whole effort. In this episode, we talk about how to identify possible problems in collaboration between the team and PO, and how to help teams and PO’s collaborate.

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 Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

Jeremy Willets: Component teams make you slow, are you paying attention?

How we set up teams has a direct impact on their ability to deliver. As Scrum Masters, we should pay attention to the early signs that something is going wrong. In this episode, we discuss the “platform team” anti-pattern, the dependencies that it causes and how we can raise the issue early enough to have an impact.

In this episode, we refer to the Marshmallow experiment blog post by Marcus Hammarberg, a great illustration that quick iteration with the result in mind can be much more effective and efficient for Scrum teams.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.