Chris Foley: Growing the Product Development community as a Scrum Product Owner 

The relationship between PO, team and stakeholders is critical. We talk about some of the anti-patterns, as well as what would a great community-building PO look like.

The Great Product Owner: Growing the Product Development community as a PO

Product Owners that can take advantage of the team’s ingenuity and creativity are more likely to succeed in their role! This PO would listen to the team’s ideas on what to demo, and act as the bridge between the team and the business stakeholders, effectively creating a “wider” product development team that included not only the team, but the PO and the stakeholders as well! 

The Bad Product Owner: The “over-engineer all the things” PO

When Product Owners try to “control” the team by dictating how they should be working on the stories, and ignoring their ideas they prevent the team from bringing in their creative input and augmenting the PO’s ideas. In this segment, we also talk about the “not enough detail” and the “over-engineer all the things” PO, who does not understand the MVP (Minimum Viable Product) mindset. 

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: 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Chris Foley

Chris is a Principal Systems Design Engineer at Red Hat working in the area of Engineering Improvement. He has over 20 years of experience in software and has filled PO and ScrumMaster roles. The team, to Chris, is the essence of the whole process and the Scrum Masters role is to help optimize that. He uses his experience from the sporting world to draw parallels around how successful teams function.

You can link with Chris Foley on LinkedIn and connect with Chris Foley on Twitter.