Features
Teams should measure the cost of keeping a feature alive, not only the cost to build it. A feature continues to require work after it ships. Feature planning should account for ongoing maintenance before a feature is accepted. Every new fe…
1 sources - 5 claims
Teams should measure the cost of keeping a feature alive, not only the cost to build it. A feature continues to require work after it ships. Feature planning should account for ongoing maintenance before a feature is accepted. Every new feature imposes a permanent tax on team attention, time, and cognitive capacity. Features that fail to produce value should be removed rather than left in the system.