Agile Manifesto is outdated! We urgently need a Product Manifesto!
summary
Argues that Agile’s focus on working software drives feature factories and not outcomes, proposes a Product Manifesto with values like solve problems over implement solutions, start with hypotheses not opinions, and empathize with end users. Uses a failed six-sprint training portal that users couldn’t use on planes to show solving the wrong problem, and a Brazilian car marketplace pivot that discontinues the app and builds a dealer frontend to hit a 30% target and instead achieves a 50% engagement lift in three months. Recommends practices like remove backlog items untouched for 3 months.
AI-written summary · about
chapters (4)
related talks
26mManifesto for a Product Mindset in Agile Development
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
01h 01mLeadership Lessons from the Agile Manifesto
30mLeadership Lessons from the Agile Manifesto
34mLeadership Lessons from the Agile Manifesto
26mIs Agile still the answer?
02mon the origins of the Agile manifesto
34mFor effectiveness, Agile was never the answer