How Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
summary
Argues that Agile’s fixation on points and velocity sacrifices real product value and urges five changes: form a cross-functional core team (product, UX, tech lead) that owns output, outcome and impact; replace feature-backlog with a learning backlog of riskiest assumptions; treat ideas as bets and validate with prototypes, pilots, A/B tests or live-data experiments; measure outcome (not just shipped scope); examples: CarMax pilots, 60–70% of features rarely used, and studies showing ~80% orgs chasing Agile without measuring impact.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:45Product Ownership in Agile Development
- 1:49Agile Is Eating the World
- 5:07Look To Stop Focusing on Delivering Software Faster
- 11:51Triple Constraint
- 14:04A Client Vendor Pattern
- 21:13Build a Successful Product
- 23:55Technology Trends
- 26:32Core Product Team
- 30:20The Failure Rate of Tech Startups
- 35:09Hypothesis Statements
- 43:44Build Scalable Shippable Software
- 46:02Stupid Zone
- 58:33Product Centric View of Agile Development
related talks
40mAgile is Broken & It’s the Product Manager’s Fault
40mRegain Benefits from Agile Software Development
34mFor effectiveness, Agile was never the answer
49mAgile Manifesto is outdated! We urgently need a Product Manifesto!
29mFrom Agile to Outcome-Driven
34mAgile-battle
49mAgile is a Dirty Word
36mOk, I’ve Burned My Roadmap and My Backlog. Now What? Lean Product Management