Susannah Chambers: Involving the team, an asset for great Scrum Product Owners

The way the PO involves the team in their work and decisions can make or break the collaboration between team and PO. In this episode, we talk about two contrasting approaches, and why the effective involvement of the team in the work of the PO is so important.

The Great Product Owner: User Experience focused PO

This particular Product Owner was very much focused on user experience, and that helped the team also focus on that aspect of their work. During meetings with the team, the PO constantly brought up the value they were trying to “drive” for the customer. 

In this segment, we refer to an approach Susannah calls “Metrics and Chill”. Listen in to learn what that is about.

The Bad Product Owner: The PO that would have conversations without the team

Product Owners can help, or hinder the teams’ work. In this segment, we talk about a PO that would turn all blame on the team, and would have conversations with stakeholders without the team knowing about it, or being informed. This inevitably led to bad surprises that the team wasn’t ready for, and then was blamed for. Listen to these anti-patterns to learn to detect them before it is too late!

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 Susannah Chambers

Susannah seeks joy and empowers teams to articulate how they add value. She is a Certified ScrumMaster and Agile Team Coach for 3 software development teams for a major retailer. Susannah is also a Personal Agility Recognized Ambassador for the Personal Agility Institute and she helps people identify what really matters.

You can link with Susannah Chambers on LinkedIn and connect with Susannah Chambers on Twitter.

Leave a Reply

Your email address will not be published. Required fields are marked *