How to defeat feature gluttony?
summary
Argues that piling features slows UX and code, so teams prune aggressively: build a product tree to keep ideas high‑level, score items with love vs roy (business value vs risk), and keep only ~2 sprints of ready work. Measure real usage under the hood, hide-and-measure for months (accountants found a hidden report after half a year), rely on automated tests, delete huge backlogs or start fresh, split huge 21‑point stories, and merge duplicate features so the app gets faster.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:28What Would Happen if We Remove Unused Features
- 15:26Priorities
- 15:48Documentation
- 20:56Identifying the Vision
- 31:04Business Value
- 41:19Why It's Dangerous To Have Too Many Stuff
- 44:50Showing Alternatives
related talks
33mHow Minimalism Helps Build High-Quality Products
01h 01mFixing the Ultimate Legacy System: You
29mThe Undeniable Virtue of Doing Less
05mHow To Get Nothing Done
50mThe Effective Developer - Work Smarter, Not Harder
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
21mNeed for speed - Moving fast as a software engineer
31mProduct excellence and developer productivity fireside chat