Advertisement

Continuous Software Portfolio Performance Management

  • Paul van Vulpen
  • Sjaak Brinkkemper
  • Slinger Jansen
  • Garm Lucassen
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 336)

Abstract

Product portfolio decision making is the process of coming to decisions regarding resource division along multiple software products. This process is part of portfolio management, and is an essential task in managing a software company. However, product portfolio decision making is an implicit process, and product managers are too occupied with tactical and operational decision making to execute strategic decisions regarding portfolio management. Academic research has not yet provided a model to adapt intuitive and opportunistic portfolio decision making to an explicit and data-driven cycle. The goal of this research is to make portfolio decision making explicit by modeling this process in the Dutch software industry. Case studies at 6 small to medium-size software companies in the Netherlands evaluate the initial Software Portfolio Decision Making (SPDM) model. We present the SPDM model after adaptation to the findings in the case studies. Using this model enables software companies to move from an intuitive decision making process towards data-driven explicit decision making.

Keywords

Software product management Portfolio management Strategic decision making 

References

  1. 1.
    Ebert, C.: The impacts of software product management. J. Syst. Softw. 80(6), 850–861 (2007)CrossRefGoogle Scholar
  2. 2.
    Van De Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., Bijlsma, L.: Towards a reference framework for software product management. In: 14th IEEE International Conference Requirements Engineering, pp. 319–322. IEEE (2006)Google Scholar
  3. 3.
    Lehtola, L., Kauppinen, M., Kujala, S.: Linking the business view to requirements engineering: long-term product planning by roadmapping. In: 2005 Proceedings 13th IEEE International Conference on Requirements Engineering, pp. 439-443. IEEE (2005)Google Scholar
  4. 4.
    Weiss, D.M., Lai, C.T.R.: Software Product-line Engineering: A Family-based Software Development Process, vol. 12. Addison-Wesley, Reading (1999)Google Scholar
  5. 5.
    Bosch, J.: Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach. Pearson Education, London (2000)Google Scholar
  6. 6.
    Jansen, S., Popp, K.M., Buxmann, P.: The sun also sets: ending the life of a software product. In: Regnell, B., van de Weerd, I., De Troyer, O. (eds.) ICSOB 2011. LNBIP, vol. 80, pp. 154–167. Springer, Heidelberg (2011).  https://doi.org/10.1007/978-3-642-21544-5_13CrossRefGoogle Scholar
  7. 7.
    Bekkers, W., van de Weerd, I., Spruit, M., Brinkkemper, S.: A framework for process improvement in software product management. In: Riel, A., O’Connor, R., Tichkiewitch, S., Messnarz, R. (eds.) EuroSPI 2010. Communications in Computer and Information Science, vol. 99, pp. 1–12. Springer, Heidelberg (2010).  https://doi.org/10.1007/978-3-642-15666-3_1CrossRefGoogle Scholar
  8. 8.
    Holmström Olsson, H., Bosch, J.: Towards data-driven product development: a multiple case study on post-deployment data usage in software-intensive embedded systems. In: Fitzgerald, B., Conboy, K., Power, K., Valerdi, R., Morgan, L., Stol, K.-J. (eds.) LESS 2013. LNBIP, vol. 167, pp. 152–164. Springer, Heidelberg (2013).  https://doi.org/10.1007/978-3-642-44930-7_10CrossRefGoogle Scholar
  9. 9.
    Bosch, J.: Speed, data, and ecosystems: the future of software engineering. IEEE Softw. 33(1), 82–88 (2016)CrossRefGoogle Scholar
  10. 10.
    McNally, R.C., Durmuolu, S.S., Calantone, R.J.: New product portfolio management decisions: antecedents and consequences. J. Prod. Innov. Manag. 30(2), 245–261 (2013)CrossRefGoogle Scholar
  11. 11.
    Cooper, R.G., Edgett, S.J., Kleinschmidt, E.J.: New product portfolio management: practices and performance. J. Prod. Innov. Manag. 16(4), 333–351 (1999)CrossRefGoogle Scholar
  12. 12.
    Cusumano, M.A.: The Business of Software. Free Press, New York (2004)Google Scholar
  13. 13.
    Yin, R.K.: Case Study Research and Applications Design and Methods. Sage publications, Thousand Oaks (2017)Google Scholar
  14. 14.
    Bechhofer, F., Elliott, B., McCrone, D.: Safety in numbers: on the use of multiple interviewers. Sociology 18(1), 97–100 (1984)CrossRefGoogle Scholar
  15. 15.
    Steenbergen, M.V.: Maturity and effectiveness of enterprise architecture (Doctoral dissertation), Utrecht University, p. 245 (2011)Google Scholar
  16. 16.
    Ward, J., Daniel, E.: Benefits Management: Delivering Value from IS and IT Investments, p. 418. Wiley, Chichester (2006)Google Scholar
  17. 17.
    Ward, J., Murray, P., Daniel, E.: Benefits management best practice guidelines. In: Information Systems Research Center, Cranfield School of Management, Cranfield (2004)Google Scholar
  18. 18.
    Udo-Imeh, P.T., Edet, W.E., Anani, R.B.: Portfolio analysis models: a review. Eur. J. Bus. Manage. 4(18), 101–117 (2012)Google Scholar
  19. 19.
    Linden, A., Fenn, J.: Understanding Gartner’s hype cycles. Strategic Analysis Report N R-20-1971. Gartner, Inc. (2003)Google Scholar
  20. 20.
    Porter, M.E.: The five competitive forces that shape strategy. Harvard Bus. Rev. 86(1), 25–40 (2008)Google Scholar
  21. 21.
    La Pira, F.: Entrepreneurial intuition, an empirical approach. J. Manage. Mark. Res. 6, 1 (2011)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  • Paul van Vulpen
    • 1
  • Sjaak Brinkkemper
    • 1
  • Slinger Jansen
    • 1
  • Garm Lucassen
    • 1
  1. 1.Utrecht UniversityUtrechtThe Netherlands

Personalised recommendations