Balancing Technical Prowess with Product Ownership with Erica Menendez and Phillip Lisenba

Agile Coaches' Corner

AgileThought and Dan Neumann at AgileThought에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 AgileThought and Dan Neumann at AgileThought 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

2y ago 29:33

MP3•에피소드 홈

저장한 시리즈 ("피드 비활성화" status)

When? This feed was archived on September 27, 2025 20:13 (26d ago). Last successful fetch was on November 28, 2024 15:27 (11M ago)

Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

This week, Dan Neumann is joined by Erica Menendez and Phillip Lisenba to explore the Product Owner’s accountabilities, especially when they are filled by a highly technical professional, and how this can impact the Team’s work in positive and negative ways. They share their own Agile experiences dealing with mature Product Owners and what the Agile and the Scrum framework proposes for these cases.

Key Takeaways

Challenges and opportunities of dealing with a highly technical Product Owner:

The Product Owner’s relationship with the Team will determine the extent of the accountabilities on each side.
A strong Scrum Master can help balance the Team out due to the collaboration of a technical Product Owner who has brought a lot to the table and helped the Team create a solution. The Team and Product Owner working in a psychologically safe environment grow together in constant intercommunication.
A mature Product Owner helps maintain the balance.
A very technical Product Owner can be highly prescriptive and fall into the mistake of making highly predictive sprint plans, and, as a result, developers turn more into coders.
The Product Owner has to be able to transfer some of their knowledge to the Team since they won’t always be there to help them.

The Scrum Guide remarks that the Product Owner is the “what” person, and the Team is the “how.”

The entire Scrum Team is accountable for creating a valuable, helpful increment every sprint. The Product Owner is responsible for a backlog that optimizes value, and there could be a dysfunction if the Product Owner is disconnected and can’t contribute as a partner for a valuable sprint plan.
When the Product Owner and the Team can communicate directly, they can take advantage of everyone’s skills; that way, they can leverage everything the Team brings.
Everything depends on relationships and communication.

Mentioned in this Episode:

Listen to Podcast Ep 197. Approaching Vacations with an Agile Perspective

Get SAFe certified!

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!

332 에피소드

#Agile #Software Development #Business #AgileThought #Dan Neumann at AgileThought #Agile Coach #Tech