Artwork

Content provided by Vivek Khattri. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Vivek Khattri or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

POV on Product Ownership from the Director of Product at Google with Richard Seroter

16:16
 
Share
 

Manage episode 352272183 series 3357843
Content provided by Vivek Khattri. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Vivek Khattri or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Today, we feature the best moments of our conversation with Richard Seroter, Director of Developer Relations and Outbound Product Management at Google Cloud. He discusses what it means to be a product owner and how to work with engineers, end users, and everyone in between.

Richard shares how to exercise leadership as a product owner and work with stakeholders not as a boss but as a member of the team. He also talks about using data points to prioritize feature decisions, instilling self-governance and accountability, and promoting continuous improvement in the team.

HIGHLIGHT QUOTES

A product owner leads through influence - Richard: "A good product owner leads through influence. They don't have direct authority. They don't have a management staff of people. The engineers don't report to them. But you are leading often by showing that you have their back. And, for me again, that was a very underrated aspect that if you're a good product owner, the engineers think you are covering for them in a good way."

Don't procrastinate and always ship at the end of each release - Richard: "I don't think you're going to have a good time if you don't force your team to ship after the end of each release, each sprint, because if you don't ship, what's really easy to do? Let's just roll it into the next one. If you have that failsafe, you're going to use it versus like nope, we ship at the end of each release."

Get to know Richard and what he’s up to:

Connect with Vivek and find out more about what he’s up to:

If you enjoy The Agile Coach and are interested in learning more, you can check us out at the link below:

  continue reading

97 episodes

Artwork
iconShare
 
Manage episode 352272183 series 3357843
Content provided by Vivek Khattri. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Vivek Khattri or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Today, we feature the best moments of our conversation with Richard Seroter, Director of Developer Relations and Outbound Product Management at Google Cloud. He discusses what it means to be a product owner and how to work with engineers, end users, and everyone in between.

Richard shares how to exercise leadership as a product owner and work with stakeholders not as a boss but as a member of the team. He also talks about using data points to prioritize feature decisions, instilling self-governance and accountability, and promoting continuous improvement in the team.

HIGHLIGHT QUOTES

A product owner leads through influence - Richard: "A good product owner leads through influence. They don't have direct authority. They don't have a management staff of people. The engineers don't report to them. But you are leading often by showing that you have their back. And, for me again, that was a very underrated aspect that if you're a good product owner, the engineers think you are covering for them in a good way."

Don't procrastinate and always ship at the end of each release - Richard: "I don't think you're going to have a good time if you don't force your team to ship after the end of each release, each sprint, because if you don't ship, what's really easy to do? Let's just roll it into the next one. If you have that failsafe, you're going to use it versus like nope, we ship at the end of each release."

Get to know Richard and what he’s up to:

Connect with Vivek and find out more about what he’s up to:

If you enjoy The Agile Coach and are interested in learning more, you can check us out at the link below:

  continue reading

97 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide