Slaying the Backlog Beast: A #NoBacklogs Approach to Product Management
summary
Claims that teams hit business results with 1/10th of the investment and time by converting deep backlogs into a physical wall and running rapid experiments. Recommends keeping only two sprints of backlog, using impact mapping, user story mapping, Lean Startup experiments, a business value equation and kill criteria, applying no-estimates practices, deleting obsolete Jira items, and focusing on delivery over paperwork — cites a case that generates 400k+ EUR in two weeks and an example where one person spends 40 hours monthly managing useless backlog cruft.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:29Why this talk matters
- 3:17Requirements evolution
- 6:26The failure of traditional requirements and documentation
- 10:45Project managers trapped
- 12:11Bloated backlogs pain
- 13:58Top 5 backlog problems
- 17:30Software infancy agility
- 19:58Backlogs outdated
- 21:02Better solution goals
- 22:06Value over features
- 23:53Delivery focus
- 25:37Two-sprint backlog rule
- 26:40Prioritization tools
- 28:26Clarity and goals
- 30:13Project management metaphor
- 31:38OKRs and micromanagement
- 32:42Business value equation
- 35:52Agile principles violated
- 37:15Feedback cycles illusion
- 38:39Steps to replace backlogs
- 40:28Call to action
related talks
30mAre You Doing Product Management or Bullshit Management?
47mHoney, I shrunk the backlog
43mApplying Agile out of development
51mMaximim Impact, Minimum Effort
11mLeading Agile Teams to Success: Lessons from the Trenches
26mFrom Backlog to Product
56mHow to Work with the Backlog
45mThe astonishing value of speed