14.1 Early Project: Feature-Set Reduction
14.2 Mid-Project: Feature-Creep Control
14.3 Late Project: Feature Cuts
Customer-oriented development: Chapter 10
Designing for change: Chapter 19
Lifecycle planning: Chapter 7
Summary of change board: Chapter 17
Summary of requirements scrubbing: Chapter 32
SOFTWARE DEVELOPERS AND MANAGERS SAY that they understand the need for feature-set control, but industry reports indicate otherwise. Developers, managers, marketers, and end-users continue to stuff so many features into already bloated products that one of the elders of the software industry has publicly pleaded for leaner software products (Wirth 1995).
The most serious feature-set control problem is the ...