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.