Skip to main content
Log in

Roadmapping problems in practice: value creation from the perspective of the customers

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

Roadmapping has been recognized as a critical activity for adding business value to a software product. The marketing literature has placed increasing emphasis on customer value and that value is created in customers’ everyday activities. This paper presents an action research study on the roadmapping problems of two software product companies. The key findings were that customer knowledge was fragmented across different functions of the companies and that roadmapping neglected service development. To solve these problems, the analysis of customer value and customers’ processes was integrated into roadmapping. Facilitated workshops with cross-functional teams were used to analyze the customers’ processes in their entirety and to create a holistic view to roadmapping. The lessons learned offer practical means for software companies to shift their focus from the prioritization of software features to the analysis of customers’ processes and the prioritization of customers’ activities. That shift can promote value for customers and uncover new service business opportunities. Accordingly, this paper provides a six-step approach to adopt the value-creation logic from the customers’ perspective into the existing roadmapping process of a company.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10

Similar content being viewed by others

References

  1. Kappel T (2001) Perspectives on roadmaps: how organizations talk about the future. J Prod Innov Manag 18:39–50

    Article  MathSciNet  Google Scholar 

  2. Albright RE, Kappel T (2003) Roadmapping in the corporation. IEEE Eng Manag Rev 3:32–40

    Article  Google Scholar 

  3. Lehtola L, Kauppinen M, Vähäniitty J, Komssi M (2009) Linking business and requirements engineering: is solution planning a missing activity in software product companies? Requir Eng 14:113–128

    Article  Google Scholar 

  4. Lehtola L, Kauppinen M, Kujala S (2005) Linking business view to requirements engineering: long-term product planning by roadmapping. In: 13th International conference on requirements engineering RE’05, pp 439–446

  5. Kauppinen M, Savolainen J, Lehtola L, Komssi M, Töhönen H, Davis A (2009) From feature development to customer value creation. In: 17th International requirements engineering conference RE’09, pp 275–280

  6. Gorschek T, Wohlin C (2006) Requirements abstraction model. Requir Eng 11:79–101

    Article  Google Scholar 

  7. Wohlin A, Aurum A (2006) Criteria for selecting software requirements to create product value: an industrial empirical study. In: Biffl S, Aurum A, Boehm B, Erdogmus H, Grünbacher P (eds) Value-based software engineering. Springer, Berlin, pp 179–200

    Chapter  Google Scholar 

  8. Barney S, Aurum A, Wohlin C (2008) A product management challenge: creating software product value through requirements selection. J Syst Archit 54:576–593

    Article  Google Scholar 

  9. Aurum A, Wohlin C (2007) A value-based approach in requirements engineering: explaining some of the fundamental concepts. In: 13th International working conference on requirements engineering: foundation for software quality REFSQ 2007, pp 109–115

  10. Normann R, Ramirez R (1993) From value chain to value constellation. Harv Bus Rev 71:65–77

    Google Scholar 

  11. Grönroos C (2008) Service logic revisited: who creates value? And who co-creates? Eur Bus Rev 20:298–314

    Article  Google Scholar 

  12. Vargo SL, Lusch RF (2008) Service-dominant logic: continuing the evolution. J Acad Mark Sci 36:1–10

    Article  Google Scholar 

  13. Grönroos C (2010) A service perspective on business relationships: the value creation, interaction and marketing interface. Ind Mark Manag 40:240–247

    Article  Google Scholar 

  14. Komssi M, Kauppinen M, Töhönen H, Lehtola L, Davis AM (2011) Integrating analysis of customers’ processes into roadmapping: the value-creation perspective. In: 19th International requirements engineering conference RE’11, pp 57–66

  15. Payne A, Holt S (2001) Diagnosing customer value: integrating the value process and relationship marketing. Br J Manag 12:159–182

    Article  Google Scholar 

  16. Woodruff R (1997) Customer value: the next source for competitive advantage. J Acad Mark Sci 25:139–153

    Article  Google Scholar 

  17. Woodall T (2003) Conceptualizing ‘value for the customer’: an attributional, structural and dispositional analysis. Acad Mark Sci Rev 12:1–42

    Google Scholar 

  18. Smith J, Colgate M (2007) Customer value creation: a practical framework. J Mark Theory Pract 15:7–23

    Article  Google Scholar 

  19. Ravald A, Grönroos C (1996) The value concept and relationship marketing. Eur J Mark 30:19–30

    Article  Google Scholar 

  20. Holbrook M (1999) Introduction to consumer value. In: Holbrook MB (ed) Consumer value: a framework for analysis and research. Routledge, London, pp 1–28

    Chapter  Google Scholar 

  21. Zeithaml A (1988) Consumer perceptions of price, quality, and value: a means-end model and synthesis of evidence. J Mark 52:2–22

    Article  Google Scholar 

  22. Ulaga W, Eggert A (2006) Value-based differentiation in business relationships: gaining and sustaining key supplier status. J Mark 70:119–136

    Article  Google Scholar 

  23. Huber F, Herrmann A, Morgan RE (2001) Gaining competitive advantage through customer value oriented management. J Consumer Mark 18:41–53

    Article  Google Scholar 

  24. Karlsson L, Regnell B, Thelin T (2006) Case studies in process improvement through retrospective analysis of release planning decisions. Int J Softw Eng Knowl Eng 16:885–915

    Article  Google Scholar 

  25. Robertson S, Robertson J (2006) Mastering the requirements process, 2nd edn. Addison-Wesley, Boston

    Google Scholar 

  26. Reicheld FF (1994) Loyalty and the renaissance of marketing. Mark Manag 2:10–22

    Google Scholar 

  27. Kim S, In HP, Baik J, Kazman R, Kwangsin H (2008) VIRE: sailing a blue ocean with value-innovative requirements. IEEE Softw 25:80–87

    Article  Google Scholar 

  28. Bolton RN, Drew JH (1991) A multistage model of customers’ assessments of service quality and value. J Consumer Res 17:375–384

    Article  Google Scholar 

  29. Pura M (2005) Linking perceived value and loyalty in location-based mobile services. Manag Serv Qual 15:509–538

    Article  Google Scholar 

  30. Holbrook MB (2006) Consumption experience, customer value, and subjective personal introspection: an illustrative photographic essay. J Bus Res 59:714–725

    Article  Google Scholar 

  31. Khalifa AS (2004) Customer value: a review of recent literature and an integrative configuration. Manag Decis 42:645–666

    Article  Google Scholar 

  32. Slater SF (1997) Developing a customer value-based theory of the firm. J Acad Mark Sci 25:162–167

    Article  Google Scholar 

  33. Mc Elroy J, Ruhe G (2010) When-to-release decisions for features with time-dependent value functions. Requir Eng 15:337–358

    Article  Google Scholar 

  34. Mohamed ASI, El-Maddad IA, Wahba CAM (2008) Criteria-based requirements prioritization for software product management. In: International conference on software engineering research and practice SERP 2008, pp 587–593

  35. Payne AF, Storbacka K, Frow P (2008) Managing the co-creation of value. J Acad Mark Sci 36:83–96

    Article  Google Scholar 

  36. Grönroos C (2007) Service management and marketing: customer management in service competition, 3rd edn. Wiley, New York

    Google Scholar 

  37. Kettinger WJ, Teng JTC, Guha S (1997) Business process change: a study of methodologies, techniques, and tools. MIS Q 21:55–98

    Article  Google Scholar 

  38. Biazzo S (2002) Process mapping techniques and organisational analysis. Bus Process Manag J 8:42–52

    Article  Google Scholar 

  39. Patrício L, Fisk RP, Cunha JF (2008) Designing multi-interface service experiences: the service experience blueprint. J Serv Res 10:318–334

    Article  Google Scholar 

  40. MacMillan I, McGrath R (1997) Discovering new points of differentiation. Harv Bus Rev 75:133–145

    Google Scholar 

  41. Chaffee EE (1985) Three models of strategy. Acad Manag Rev 10(1):89–98

    Google Scholar 

  42. Seddon PB, Lewis GP, Freeman P, Shanks G (2004) The case for viewing business models as abstractions of strategy. Commun Assoc Inf Syst 13:427–442

    Google Scholar 

  43. Porter ME (1996) What is strategy? Harv Bus Rev 74:61–78

    Google Scholar 

  44. Porter ME (2001) Strategy and the internet. Harv Bus Rev 79:63–78

    Google Scholar 

  45. Kaplan RS, Norton DP (2004) Having trouble with your strategy? Then map it. Harv Bus Rev 78:167–276

    Google Scholar 

  46. Mullins J (2008) The new business road test: what entrepreneurs and executives should do before writing a business plan, 2nd edn. McGraw Hill, New York

    Google Scholar 

  47. Porter M (1985) Competitive advantage: creating and sustaining superior performance. Free Press, New York

    Google Scholar 

  48. Phaal R, Farrukh CJP, Probert DF (2004) Technology roadmapping—a planning framework for evolution and revolution. Technol Forecast Soc Chang 71:5–26

    Article  Google Scholar 

  49. Suomalainen T, Salo O, Abrahamsson P, Similä J (2011) Software product roadmapping in a volatile business environment. J Syst Softw 84:958–975

    Article  Google Scholar 

  50. van de Weerd I, Brinkkemper S, Nieuwenhuis R, Versendaal J, Bijlsma L (2006) Towards a reference framework for software product management. In: 14th International requirements engineering conference RE’11, pp 319–322

  51. Pohl K, Böckle G, Linden Fvd (2005) Software product line engineering: foundations, principles, and techniques. Springer, Berlin

    Book  Google Scholar 

  52. Clements P, Northrop L (2002) Software product lines. Practices and patterns. SEI series in software engineering. Addison-Wesley, Boston

    Google Scholar 

  53. Phaal R, Farrukh CJP, Mitchell R, Probert DR (2003) Starting up roadmapping fast. Res Technol Manag 46:52–58

    Google Scholar 

  54. Yoon B, Phaal R, Probert D (2008) Morphology analysis for technology roadmapping: application of text mining. R&D Manag 38:51–68

    Article  Google Scholar 

  55. Myers MD (2009) Qualitative research in business & management. Sage, London

    Google Scholar 

  56. Avison D, Lau F, Myers MD, Nielsen PA (1999) Action research. Commun ACM 42:94–97

    Article  Google Scholar 

  57. Potts C (1993) Software-engineering research revisited. IEEE Softw 10:19–28

    Article  Google Scholar 

  58. Gummesson E (2000) Qualitative methods in management research, 2nd edn. Sage, London

    Google Scholar 

  59. Komssi M, Kauppinen M, Heiskari J, Ropponen M, Transforming a software product company into a service business: case study at F-Secure. In: 33rd Annual international computer software and application conference, COMPSAC 2009, pp 61–66

  60. Strauss JD, Radnor M (2004) Roadmapping for dynamic and uncertain environments. Res Tech Manag 47:51–57

    Google Scholar 

  61. Gold N, Mohan A, Knight C, Munro M (2004) Understanding service-oriented software. IEEE Softw 21:71–77

    Article  Google Scholar 

  62. Ryals LJ, Holt S (2007) Creating and capturing value in KAM relationships. J Strateg Mark 15:403–420

    Article  Google Scholar 

  63. Vähäniitty J, Rautiainen K, Lassenius C (2010) Small software organizations need explicit portfolio management. IBM J Res Dev 54:1-1–1-12

    Article  Google Scholar 

  64. Karlsson J, Ryan K (1997) A cost-value approach for prioritizing requirements. IEEE Softw 20:52–55

    Google Scholar 

  65. Komssi M, Kauppinen M, Ropponen M, Palomäki P (2011) Transformations of a solution strategy: a case study. In: 2nd International conference on software business ICSOB 2011, pp 140–153

  66. Kaindl H, Brinkkemper S, Bubenko JA Jr, Farbey B, Greenspan SJ, Heitmeyer CL, Leite JSCP, Mead NR, Mylopoulos J, Siddiqi J (2002) Requirements engineering and technology transfer: obstacles, incentives and improvement agenda. Requir Eng 7:113–123

    Article  Google Scholar 

  67. Kauppinen M, Kujala S, Aaltio T, Lehtola L (2002) Introducing requirements engineering: how to make a cultural change happen in practice. In: Proceedings of IEEE joint international requirements engineering conference (RE’ 02), pp 43–51

  68. Carroll JM (2002) Scenarios and design cognition. In: Proceedings of IEEE joint international requirements engineering conference (RE’ 02), pp 3–5

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Marko Komssi.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Komssi, M., Kauppinen, M., Töhönen, H. et al. Roadmapping problems in practice: value creation from the perspective of the customers. Requirements Eng 20, 45–69 (2015). https://doi.org/10.1007/s00766-013-0186-3

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-013-0186-3

Keywords

Navigation