Isaac Garcia: Why Scrum Masters must learn to accept what you can’t influence

When Isaac joined this team, he encountered a team that had failed to deliver and was low on motivation. Isaac focused on helping the team find their motivation, organized a kick-off to get the team to come together around a goal, and a common vision, only to see management remove people from an already overwhelmed team… What should a Scrum Master do when that happens? We discuss that, and critical lessons learned about what we can influence (or not) as Scrum Masters. 

In this episode, we refer to the circles of influence, a tool to help Scrum Masters focus on what they can influence and accept what they can’t.

Featured Book for the Week: The Phoenix Project

In The Phoenix Project, Gene Kim, Kevin Behr and George Spafford chronicle the story of a company that is on the brink. They walk the reader through the process of understanding what is holding the organization back, and what the hero of the story will learn to help turn the company around.

For Isaac, this is a book that teaches important techniques and helps Scrum Masters make a difference in their place of work.

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.

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 build a guiding coalition for change

It’s common to hear the “build a guiding coalition for change” mantra. It is part of a famous change management model (The Kotter 8-step change model), and a practical tip that we all can benefit from. However, how is that done in practice? In this episode, we talk about an Agile transformation at a large, distributed organization and how Gilson and others were able to build that guiding coalition for change. 

In this episode, we also refer to the book Radical Candor by Kim Scott.

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.

Gilson Souza: How Scrum Masters counter the “sub-team” anti-pattern

We often talk about cross-functional teams on the podcast. We talk about the advantages when it comes to flow, and getting things done quicker. However, there are pitfalls we should be aware of. One of the pitfalls is when the team members in a team start to “cluster” and become like sub-teams inside the team. As Scrum Master, we must be aware of this possible anti-pattern and ready to tackle it quickly. Listen in to learn how Gilson detected and countered the sub-team anti-pattern.

Featured Book for the Week: Coaching Agile Teams by Lyssa Adkins

In Coaching Agile Teams by Lyssa Adkins, Gilson found an out-of-the-box explanation for the Scrum Master role that helped him get out of the traditional task-driven, project manager-like role that many Scrum Masters still take. 

In this segment, we also mention the book Inspired: How To Create Products Customers Love by Marty Cagan

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

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 team manager that was also a Product Owner, a Product Owner role Anti-Pattern

This week we share simple, yet effective Product Owner patterns and discuss the anti-pattern that can emerge when the PO is also the team manager.

The Great Product Owner: simple patterns with a great impact

Great Product Owners have a strong identification with the product. They can say “no” to certain ideas, but above all, they see themselves as much more than owners of a list we call Product Backlog. 

These are just some of the good patterns great Product Owners exhibit, but there are more. Listen in to find out what are the other good patterns David has found in highly effective Product Owners. 

The Bad Product Owner: The Product Owner that was also the team manager

Many of the Product Owner anti-patterns come from the role they play in the organization. In this segment, we talk about the Product Owner that was also a team manager, and how those two roles can become a source for problems when they are held by the same person.

In this segment, we refer to Product Mastery, by Geoff Watts. Geoff has been on the podcast before to talk about great Scrum Masters and Product Owners. We also refer to the book by Bob Galen: Scrum Product Ownership: Balancing Value from the Inside Out.

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 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.

David Gentry: how the Starfish Agile Retrospective leads quickly to actions for the team 

Is your team more like a Golf team or a Hockey team? That’s one of the questions David asks himself when assessing his impact as a Scrum Master. Checking the Scrum Guide, for a list of responsibilities may also be a good way to get started assessing your success as a Scrum Master, but don’t forget to adapt to the local reality, a core idea of Agile that also applies to the Scrum Master work. 

Featured Retrospective Format for the Week: The Starfish Retrospective

The Starfish retrospective is a format that David finds leads more often to concrete actions, the final goal of a retrospective. In this segment, we also talk about the importance of having many formats in your toolbox, so that the retrospectives don’t get boring and stop delivering results. 

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.

David Gentry: in an Agile transformation, lead by example

There’s often a misconception in certain organizations that Agile is just shorter waterfall projects. That’s very far from reality. In this episode, we talk about how David’s team showed – by example – the power of an agile way of working, and how that inspired other teams to change.

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

David Gentry: How the lack of feedback can destroy a Scrum team’s work

When everything is going well, and there’s little to no feedback, the experiment Scrum Master should be a skeptic. Feedback is the fuel for great Agile teams. in this episode, we talk about the big problems that can emerge when the team forgets to collect feedback during development. 

Featured Book for the Week: The people’s Scrum 

In The People’s Scrum by Tobias Mayer, David found a book that helped him reflect on the role of the Scrum Master, and change some of these ideas. 

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

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.