Product Ownership is a Team Sport
summary
Argues that a single Product Owner cannot cover product management, UX, domain expertise, compliance and stakeholder alignment for anything but tiny “Cinderella” projects, so product ownership becomes a team role with a Value Facilitator coordinating specialists. Uses the Octopus model (eight tentacles) and Dunbar’s 150 limit, runs Buy a Feature exercises and value S‑curve thinking to attach numerical value to backlog items, shows an internet‑banking mobile feature parsed into 35 stories and implemented first as SMS, and gives a real example where moving desks cuts a six‑day cycle to 1.5 days.
AI-written summary · about
chapters (12)
- 0:00Product ownership as team sport
- 3:23Traditional PO role broken
- 9:53Modern projects complexity myth
- 15:14Octopus model for team complexity
- 27:05Value facilitator PO role
- 33:49Large backlogs diamond mining
- 45:49Track value not velocity
- 55:07Solving right problem challenge
- 1:01:11Early initiative tools
- 1:12:11Vision goals trade-offs
- 1:23:06Cost-benefit strategic alignment
- 1:28:46Conclusion and key takeaways for product ownership
related talks
54mPM vs PO - Who Does What?
26mThe PO as a Catalyst for Change
15mHow the relationship between Product Owners + Designers can impact HCD
53m10 Lessons for Product Leaders
48mWelcome to The Team
41mProduct Management, the Future of Agility?
18mOn Product, Empathy and Creating a User Centric Culture
36mProductized: How to transform your project into a product company