How to defeat feature gluttony
summary
Feature gluttony makes products slow, brittle and expensive: one client ships with 1,053 backlog items, UIs cram too many controls, and production sometimes crashes after “just one more” feature. Remedies are concrete: group ideas on a product tree or mind map, pick work inside a time box, score each idea for business value versus technical risk and list alternatives, measure usage before removing features, and require automated tests so deletions and refactors are safe.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:46About me
- 5:14What is feature gluttony
- 7:08Examples of feature gluttony
- 9:35How feature gluttony affects our product
- 11:26Feature gluttony is like a clock
- 13:58Backlog
- 15:17Purge
- 16:16Documentation
- 18:18API
- 19:03Estimate
- 24:56Basic Respect
- 25:08How to start
- 25:26Roadmap
- 37:20Business
- 41:11Estimates
- 53:20Wrap up
- 55:56Questions
related talks
37mHow to Lose Your Feature Bloat?
31mBalancing New Features While Maintaining Quality
52mBeyond Features
41mFeature Flags: A Boon or a Brake for a Team
26mFeatures Versus Futures
45mSoftware's Seven Deadly Wastes
47mContinuous Deprovement will eat your product for breakfast
26mThe Rise and Fall of Feature Teams