Abstract
Most of the business value of a software product comes from only a small proportion of its features. Product managers face the challenge of identifying the high value features in an application and weeding out the ones of low value from the next releases. What creates this challenge is the fact that customer perceived value is an attribute, dimensions of which are not well-known yet. Currently, software companies try to assess the value of features through interviewing a number of key stakeholders. However, the literature suggests that, this kind of evaluation could be misleading due to stakeholders having different understanding of what value refers to. In this paper, through an exploratory case study, we investigate how usage of features relate to their perceived value and shed light into the factors affecting this relationship. The results show that feature usage metric has a significant potential to estimate value of features.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Boehm, B.: Value-based software engineering. In: Software Engineering Notes (2003)
Mohamed, S.I., Wahba, A.M.: Value estimation for software product management. In: Industrial Engineering and Engineering Management (2008)
Vahaniitty, J.: Key decisions in strategic new product development for small software product businesses. In: Euromicro Conference (2003)
Berry, M., Aurum, A.: Measurement and decision making. In: Value-Based Software Engineering (2006)
Egyed, A., Biffl, S., Heindl, M., Grünbacher, P.: A value-based approach for understanding cost-benefit trade-offs during automated software traceability. In: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering (2005)
Boehm, B.: Value-based software engineering: reinventing. In: ACM SIGSOFT Software Engineering Notes (2003)
Bauer, H.H., Hammerschmidt, M., Braehler, M.: The customer lifetime value concept and its contribution to corporate valuation. In: Yearbook of Marketing and Consumer Research (2003)
Park, Y., Park, G.: A new method for technology valuation in monetary value: procedure and application. In: Technovation (2004)
Barney, S., Aurum, A., Wohlin, C.: A product management challenge: Creating software product value through requirements selection. Journal of Systems Architecture (2008)
Rönkkö, M., Frühwirth, C., Biffl, S.: Integrating value and utility concepts into a value decomposition model for value-based software engineering. In: Bomarius, F., Oivo, M., Jaring, P., Abrahamsson, P. (eds.) PROFES 2009. LNBIP, vol. 32, pp. 362–374. Springer, Heidelberg (2009)
Bullock, J.: Calculating the value of testing: How to present testing as a business process investment. Software Testing and Quality Engineering (2000)
Saaty, T.L., Vargas, L.G.: Models, methods, concepts and applications of the analytic hierarchy process. Springer (2001)
Ahmad, A., Shahzad, A., Padmanabhuni, V.K., Mansoor, A., Joseph, S., Arshad, Z.: Requirements prioritization with respect to Geographically Distributed Stakeholders. In: Computer Science and Automation Engineering (2011)
Karlsson, L., Berander, P., Regnell, B., Wohlin, C.: Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning. In: Empirical Assessment in Software Engineering (2004)
Ulaga, W., Chacour, S.: Measuring customer-perceived value in business markets: a prerequisite for marketing strategy development and implementation. In: Industrial Marketing Management (2001)
Greer, D., Ruhe, G.: Software release planning: An evolutionary and iterative approach. In: Information and Software Technology (2004)
Aurum, A., Wohlin, C.: Aligning requirements with business objectives: A framework for requirements engineering decisions. In: Proceedings of Requirements Engineering Decision Support Workshop (2005)
Park, T., Kim, K.J.: Determination of an optimal set of design requirements using house of quality. Journal of Operations Management (1998)
Woodruff, R.B.: Customer value: the next source for competitive advantage. Journal of the Academy of Marketing Science (1997)
Aurum, A., Wohlin, C.: A value-based approach in requirements engineering: Explaining some of the fundamental concepts. In: Sawyer, P., Heymans, P. (eds.) REFSQ 2007. LNCS, vol. 4542, pp. 109–115. Springer, Heidelberg (2007)
Wohlin, C., Aurum, A.: What is important when deciding to include a software requirement in a project or release? In: International Symposium on Empirical Software Engineering (2005)
Wohlin, C., Aurum, A.: Criteria for selecting software requirements to create product value: An industrial empirical study. In: Value-Based Software Engineering (2006)
Kortge, G.D., Okonkwo, P.A.: Perceived value approach to pricing. In: Industrial Marketing Management (1993)
Doll, W.J., Torkzadeh, G.: Developing a multidimensional measure of system-use in an organizational context. Information and Management (1998)
Burton-Jones, A., Gallivan, M.J.: Toward a deeper understanding of system usage in organizations: A multilevel perspective. Mis Quarterly (2007)
Sun, H.: Understanding User Revisions When Using Information System Features: Adaptive System Use and Triggers. MIS Quarterly-Management Information Systems (2012)
OpenSpan Desktop Analytics, http://www.openspan.com/products/desktop_analytics (last visited on November 27, 2012)
Google Analytics, http://www.google.com/analytics (last visited on November 27, 2012)
Microsoft Spy++, http://msdn.microsoft.com/en-us/library/aa232254v=vs.60.aspx (last visited on November 27, 2012)
Atterer, R., Wnuk, M., Schmidt, A.: Knowing the users every move: user activity tracking for website usability evaluation and implicit interaction. In: Proceedings of the International Conference on World WideWeb (2006)
Eisenbarth, T., Koschke, R., Simon, D.: Locating Features in Source Code. IEEE Computer (2003)
ISO/IEC TR 9126-4, Software engineering – Product quality – Part 4: Quality in use metrics (2004)
Runeson, P., Host, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering (2009)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Marciuska, S., Gencel, C., Abrahamsson, P. (2013). Exploring How Feature Usage Relates to Customer Perceived Value: A Case Study in a Startup Company. In: Herzwurm, G., Margaria, T. (eds) Software Business. From Physical Products to Software Services and Solutions. ICSOB 2013. Lecture Notes in Business Information Processing, vol 150. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-39336-5_16
Download citation
DOI: https://doi.org/10.1007/978-3-642-39336-5_16
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-39335-8
Online ISBN: 978-3-642-39336-5
eBook Packages: Computer ScienceComputer Science (R0)