With continuous deployment of softwarefunctionality, a constant flow of new features to products isenabled. Although new functionality has potential to deliverimprovements and possibilities that were previously notavailable, it does not necessary generate business value. On thecontrary, with fast and increasing system complexity that isassociated with high operational costs, more waste than valuerisks to be created. Validating how much value a feature actuallydelivers, project how this value will change over time, and knowwhen to remove the feature from the product are the challengeslarge software companies increasingly experience today. Wepropose and study the concept of a software feature lifecyclefrom a value point of view, i.e. how companies track featurevalue throughout the feature lifecycle. The contribution of thispaper is a model that illustrates how to determine (1) when toadd the feature to a product, (2) how to track and (3) project thevalue of the feature during the lifecycle, and how to (4) identifywhen a feature is obsolete and should be removed from theproduct.
['Aleksander Fabijan', 'Helena Holmström Olsson', 'Jan Bosch']
Time to Say 'Good Bye': Feature Lifecycle