%0 Conference Paper %1 Fabijan2016 %A Fabijan, Aleksander %A Olsson, Helena Holmström %A Bosch, Jan %B International Conference on Agile Software Development %D 2016 %I Springer %K orchestration product.planning %P 39-52 %R 10.1007/978-3-319-33515-5_4 %T The lack of sharing of customer data in large software organizations: Challenges and implications %U http://link.springer.com/10.1007/978-3-319-33515-5_4 %V 251 %X With continuous deployment of software functionality, a constant flow of new features to products is enabled. Although new functionality has potential to deliver improvements and possibilities that were previously not available, it does not necessary generate business value. On the contrary, with fast and increasing system complexity that is associated with high operational costs, more waste than value risks to be created. Validating how much value a feature actually delivers, project how this value will change over time, and know when to remove the feature from the product are the challenges large software companies increasingly experience today. We propose and study the concept of a software feature lifecycle from a value point of view, i.e. how companies track feature value throughout the feature lifecycle. The contribution of this paper is a model that illustrates how to determine (1) when to add the feature to a product, (2) how to track and (3) project the value of the feature during the lifecycle, and how to (4) identify when a feature is obsolete and should be removed from the product. %@ 9783319335148

@inproceedings{Fabijan2016, abstract = {With continuous deployment of software functionality, a constant flow of new features to products is enabled. Although new functionality has potential to deliver improvements and possibilities that were previously not available, it does not necessary generate business value. On the contrary, with fast and increasing system complexity that is associated with high operational costs, more waste than value risks to be created. Validating how much value a feature actually delivers, project how this value will change over time, and know when to remove the feature from the product are the challenges large software companies increasingly experience today. We propose and study the concept of a software feature lifecycle from a value point of view, i.e. how companies track feature value throughout the feature lifecycle. The contribution of this paper is a model that illustrates how to determine (1) when to add the feature to a product, (2) how to track and (3) project the value of the feature during the lifecycle, and how to (4) identify when a feature is obsolete and should be removed from the product.}, added-at = {2018-08-31T22:18:29.000+0200}, author = {Fabijan, Aleksander and Olsson, Helena Holmström and Bosch, Jan}, biburl = {https://www.bibsonomy.org/bibtex/269017720f9aeac3f4cf91146e6af4adf/andreysaltan}, booktitle = {International Conference on Agile Software Development}, doi = {10.1007/978-3-319-33515-5_4}, interhash = {3bb46670909e6b1cd6f66fee8fb2a41f}, intrahash = {69017720f9aeac3f4cf91146e6af4adf}, isbn = {9783319335148}, issn = {18651348}, keywords = {orchestration product.planning}, month = may, pages = {39-52}, publisher = {Springer}, timestamp = {2018-08-31T23:37:56.000+0200}, title = {The lack of sharing of customer data in large software organizations: Challenges and implications}, url = {http://link.springer.com/10.1007/978-3-319-33515-5_4}, volume = 251, year = 2016 }