Mission Impossible: The Product Owner
summary
Argues the Product Owner role is often impossible because one person must cover skills authority legitimacy time, owning a single backlog and negotiating features within fixed two‑week sprints. Recommends concrete fixes: stop coding, stop line‑managing, hire UX and product marketing, delegate admin, and split strategic and tactical ownership so one person meets customers while the other works with the team. Uses the two‑week sprint cadence, single‑PO single‑backlog constraint, and time spent travelling to customers as specific constraints.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:20Do we set Product Owners up to fail?
- 6:54Scrum says... The Product Owner
- 9:28What do Product Owner do?
- 17:37Once upon a time...
- 18:064 Things
- 22:31Scrum PO skills are only a start
- 24:18Product Owner is NOT a Project Manager
- 25:09Product Owner as Entrepreneur
- 28:10Product Owner or Super Hero?
- 29:424. Time: PO needs to ...
- 32:20Skills - easy!
- 41:24Product Owner refactored
related talks
38mExamining the Product Owner Role
41mProduct Owner & Developer: An Unexpected Journey
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
05mScrumming Solo No Scrum Master or Product Owner
33mAligning Goals & Processes between Engineering & Product
36mOk, I’ve Burned My Roadmap and My Backlog. Now What? Lean Product Management
42mSlaying the Backlog Beast: A #NoBacklogs Approach to Product Management
30mWhat Product Leaders Do