Skip to main content
SpringerLink
Log in

Software Product Management

  • Chapter
  • First Online:
Software for People

Part of the book series: Management for Professionals ((MANAGPROF))

Abstract

Software organizations evolve and maintain software solutions with more than a single development project. The delta specifications and artifacts that result from each project make reuse difficult and challenge a company’s ability to innovate. Software product management is a growing discipline for understanding how to productize and align software with company strategy, how to evolve software, and how to coordinate product stakeholders. With product focus, in addition to project focus, planning accuracy can be improved, time-to-market reduced, product quality enhanced, and economic success sustained. This chapter provides an overview on software product management and discusses what today is known about this discipline.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  • Albright, R. E., & Kappel, T. A. (2003). Roadmapping in the corporation. IEEE Engineering Management Review, 31(3), 31–40.

    Article  Google Scholar 

  • Alspaugh, T. A., Scacchi, W., et al. (2010). Software licenses in context: The challenge of heterogeneously-licensed systems. Journal of the Association for Information Systems, 11(11), 730–755.

    Google Scholar 

  • Anderson, E. W., & Sullivan, M. W. (1993). Antecedents and consequences of customer satisfaction. Marketing Science, 12(2), 125–143.

    Article  Google Scholar 

  • Anderson, C. R., & Zeithaml, C. P. (1984). Stage of the product lifecycle, business strategy, and business performance. Academy of Management Journal, 27(1), 5–24.

    Article  Google Scholar 

  • Artz, P., van de Weed, I., et al. (2010). Productization: Transforming from developing customer-specific software to product software. 1st international conference on software business, Jyväskylä.

    Google Scholar 

  • Aurum, A., & Wohlin, C. (2003). The fundamental nature of requirements engineering activities as a decision-making process. Information and Software Technology, 45, 945–954.

    Article  Google Scholar 

  • Ballintijn, G. (2005). A case study of the release management of a health-care information system. IEEE international conference on software maintenance (ICSM 2005, Industry Track), Budapest, Hungary.

    Google Scholar 

  • Basili, V. R., & Boehm, B. (2001). COTS-based systems top 10 list. Computer, 34(5), 91–95.

    Article  Google Scholar 

  • Bekkers, W., van de Weed, I., et al. (2010). A framework for process improvement in software product management. European systems & software process improvement and innovation (EuroSPI 2010), Grenoble, France.

    Google Scholar 

  • Benlian, A., & Hess, T. (2010). The risks of sourcing software as a service – An empirical analysis of adopters and non-adopters. 18th European conference on information systems (ECIS 2010), Pretoria, South Africa.

    Google Scholar 

  • Berander, P., & Andrews, A. (2005). Requirements prioritization. In A. Aurum & C. Wohlin (Eds.), Engineering and managing software requirements. Berlin: Springer.

    Google Scholar 

  • Bersoff, E. (1984). Elements of software configuration management. IEEE Transactions on Software Engineering, 10(1), 79–87.

    Article  Google Scholar 

  • Boatwright, P., & Cagan, J. (2010). Build to love: Creating products that captivate customers. San Francisco, CA: Berrett Koehler.

    Google Scholar 

  • Boehm, B., & Abts, C. (1999). COTS integration: Plug and pray? Computer, 32(1), 135–138.

    Article  Google Scholar 

  • Bosch, J. (2009). From software product lines to software ecosystems. 13th international software product line conference (SPLC 2009), San Francisco.

    Google Scholar 

  • Brownsword, L., Oberndorf, T., et al. (2000). Developing new processes for COTS-based systems. IEEE Software, 17(4), 48–55.

    Article  Google Scholar 

  • Broy, M., Krüger, I. H., et al. (2007). Engineering automotive software. Proceedings of the IEEE, 95(2), 356–373.

    Article  Google Scholar 

  • Brugger, R. (2009). Der IT business case. Heidelberg: Springer.

    Book  Google Scholar 

  • Bruton, N. (2002). How to manage the IT helpdesk. Routledge: Chapman & Hall.

    Google Scholar 

  • Buttle, F. (2008). Customer relationship management. Routledge: Taylor & Francis.

    Google Scholar 

  • Buyya, R., Yeo, C. S., et al. (2009). Cloud computing and emerging IT platforms: Vision, hype, and reality for delivering computing as the 5th utility. Future Generation Computer Systems, 25(6), 599–616.

    Article  Google Scholar 

  • Cannon, D., & Wheeldon, D. (2011). ITIL service operation. The Stationery Office.

    Google Scholar 

  • Cabinet Office. (2011). ITIL service strategy. The Stationery Office.

    Google Scholar 

  • Cagan, M. (2008). Inspired: How to create products customers love. SVPG Press, Sunnyvale, CA, USA.

    Google Scholar 

  • Calvin, R. J. (2004). Sales management. McGraw-Hill Professional, New York, NY, USA

    Google Scholar 

  • Carlshamre, P., Sandahl, K., et al. (2001). An industrial survey of requirements interdependencies in software product release planning. 5th IEEE international symposium on requirements engineering, Toronto.

    Google Scholar 

  • Carmel, E., & Becker, S. (1995). A process model for packaged software development. IEEE Transactions on Engineering Management, 42(1), 50–61.

    Article  Google Scholar 

  • Carr, M. J., Konda, S. L., et al. (1993). Taxonomy-based risk identification. Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, Carnegie Mellon University.

    Google Scholar 

  • Chesbrough, H. W. (2003). The era of open innovation. MIT Sloan Management Review, 44(3), 35–41.

    Google Scholar 

  • Choudhary, V. (2007). Software as a service: Implications for investment in software development. 40th Hawaii international conference on system sciences (HICSS’07), Hawaii.

    Google Scholar 

  • Classen, A., Heymans, P., et al. (2008). What’s in a feature: A requirements engineering perspective. 11th international conference on fundamental approaches to software engineering, Budapest, Hungary.

    Google Scholar 

  • Clements, P., & Northrop, L. (2001). Software product lines: Practices and patterns. Boston, MA: Addison-Wesley Professional.

    Google Scholar 

  • CMMI Product Team. (2010). CMMI for development. Version 1.3, Carnegie Mellon University.

    Google Scholar 

  • Cockburn, A. (2001). Writing effective use cases. Boston: Addison-Wesley Professional.

    Google Scholar 

  • Cohn, M. (2004). User stories applied. Pearson Education, Boston, MA, USA.

    Google Scholar 

  • Condon, D. (2002). Software product management. Aspatore Books, Eagan, MN, USA.

    Google Scholar 

  • Cooper, R. (2001). Winning at new products: Accelerating the process from idea to launch. B&T.

    Google Scholar 

  • Cooper, R. G., Edgett, S. J., et al. (1999). New product portfolio management: Practices and performance. Journal of Product Innovation Management, 16(4), 333–351.

    Article  Google Scholar 

  • Cusumano, M. (2004). The business of software. New York: Free Press.

    Google Scholar 

  • Davis, A. (2005). Just enough requirements management. New York: Dorset House Publishing.

    Google Scholar 

  • De Haes, S., & Van Grembergen W. (2004). IT governance and its mechanisms. Information Systems Control Journal 1. See: http://www.isaca.org/Journal/Past-Issues/2004/Volume-1/Pages/IT-Governance-and-Its-Mechanisms.aspx

  • Denne, M., & Cleland-Huang, J. (2003). Software by numbers: Low-risk, high-return development. Upper Saddle River, NJ: Prentice-Hall.

    Google Scholar 

  • Dver, A. (2007). Software product management essentials. Tampa, FL: Anclote Press.

    Google Scholar 

  • Ebert, C. (2006). The impacts of software product management. Journal of Systems and Software, 80, 850–861.

    Article  Google Scholar 

  • Ebert, C. (2009). Software product management. Crosstalk, 22(1), 15–19.

    Google Scholar 

  • Ebert, C., & Salecker, J. (2009). Embedded software – Technologies and trends. IEEE Software, 26(3), 14–18.

    Article  Google Scholar 

  • Ebert, C., & Dumke, R. (2007). Software measurement: Establish – extract – evaluate – execute. Berlin: Springer.

    Google Scholar 

  • Edwards, K., & Grinter, R. (2001). At home with ubiquitous computing: Seven challenges. Atlanta: Ubiquitous Computing (UBICOMP).

    Google Scholar 

  • El Emam, K. (2005). The ROI from software quality. Boston, MA: Auerbach Publications.

    Book  Google Scholar 

  • Fenn, J., & Raskino, M. (2011). Understanding Gartner’s hype cycles. Gartner.

    Google Scholar 

  • Flammia, G., & McCandless, M. (1997). From software to service: The transformation of shrink-wrapped software on the internet. IEEE Expert, 12(2), 4–6.

    Article  Google Scholar 

  • Fricker, S., Gorschek, T., et al. (2010). Handshaking with implementation proposals: Negotiating requirements understanding. IEEE Software, 27(2), 72–80.

    Article  Google Scholar 

  • Fricker, S., & Schumacher, S. (2012). Release planning with feature trees: Industrial case. Requirements engineering: Foundations for software quality (RefsQ 2012), Essen, Germany.

    Google Scholar 

  • Galen, R. (2004). Software endgames: Eliminating defects, controlling changes, and the countdown to on-time delivery. New York: Dorset House.

    Google Scholar 

  • Garcia, R., & Calantone, R. (2002). A critical look at technological innovation typology and innovativeness terminology: A literature review. The Journal of Product Innovation Management, 19(2), 110–132.

    Article  Google Scholar 

  • German, D. M., Weber, J. H., et al. (2010). Lawful software engineering. FSE/SDP workshop on the future of software engineering (FoSER 2010), Santa Fe, New Mexico.

    Google Scholar 

  • GNU. (2007). GNU General Public License. GNU. http://www.gnu.org/licenses/gpl-3.0

  • Goffin, K., & New, C. (2001). Customer support and new product development – An exploratory study. International Journal of Operations & Production Management, 21(3), 275–301.

    Article  Google Scholar 

  • Gold, A. H., Malhotra, A., et al. (2001). Knowledge management: An organizational capabilities perspective. Journal of Management Information Systems, 18(1), 185–214.

    Google Scholar 

  • Gold, N., Mohan, A., et al. (2004). Understanding service-oriented software. IEEE Software, 21(2), 71–77.

    Article  Google Scholar 

  • Gorchels, L. (2006). The product manager’s handbook. New York: McGraw-Hill.

    Google Scholar 

  • Gorschek, T., & Wohlin, C. (2006). Requirements abstraction model. Requirements Engineering, 11(1), 79–101.

    Article  Google Scholar 

  • Gorschek, T., Fricker, S., et al. (2010). A lightweight innovation process for software-intensive product development. IEEE Software, 27(1), 37–45.

    Article  Google Scholar 

  • Griffin, A., & Hauser, J. (1996). Integrating R&D and marketing: A review and analysis of the literature. Journal of Product Innovation Management, 13, 191–215.

    Article  Google Scholar 

  • Haines, S. (2009). The product manager’s desk reference. New York: McGraw-Hill.

    Google Scholar 

  • Hauser, J., & Clausing, D. (1988). The house of quality. Harvard Business Review, 66(3), 63–73.

    Google Scholar 

  • Hayes, B. (2008). Cloud computing. Communications of the ACM, 51(7), 9–11.

    Article  Google Scholar 

  • Helferich, A., Schmid, K., et al. (2006). Product management for software product lines: An unsolved problem? Communications of the ACM, 49(12), 66–67.

    Article  Google Scholar 

  • Henderson, B. D. (1979). Henderson on corporate strategy. Abt Books, Cambridge, MA, USA.

    Google Scholar 

  • Humble, J., & Farley, D. (2010). Continuous delivery: Reliable software releases through build, test, and deployment automation. Amsterdam: Addison-Wesley Longman.

    Google Scholar 

  • Hyland, P., & Beckett, R. (1994). Engendering an innovative culture and maintaining operational balance. Journal of Small Business and Enterprise Development, 12(3), 336–352.

    Article  Google Scholar 

  • Iansiti, M., & Levien, R. (2004). The keystone advantage. Boston: Harvard Business School Press.

    Google Scholar 

  • IEEE. (1990). IEEE Standard Glossary of Software Engineering Terminology 610.12-1990.

    Google Scholar 

  • ISPMA, International Software Product Management Association. (2012). Software product management body of knowledge (SPMBoK). Retrieved July 1, 2012, from http://ispma.org/spmbok/

  • Jaccheri, L., & Torchiano, M. (2002). Classifying COTS products. 7th European conference on software quality (ECSQ 2002), Helsinki, Finland.

    Google Scholar 

  • Jansen, S., Brinkkemper, S., et al. (2007). Providing transparency in the business of software: A modeling technique for software supply networks. Virtual Enterprises and Collaborative Networks.

    Google Scholar 

  • Jansen, S., & Brinkkemper S. (2006). Ten misconceptions about product software release management explained using update cost/value functions. 1st international workshop on software product management (IWSPM’06), Minneapolis, MS, USA.

    Google Scholar 

  • Johnson, M. D., & Gustafsson, A. (2000). Improving customer satisfaction, loyalty, and profit: An integrated measurement and management system. New York: Wiley.

    Google Scholar 

  • Jones, C. (2008). Applied software measurement: Global analysis of productivity and quality. New York: McGraw Hill.

    Google Scholar 

  • Kaplan, R. S., & Norton, D. P. (1992). The balanced scorecard: Measures that drive performance. Harvard Business Review, 70(1), 172–180.

    Google Scholar 

  • Karlsson, L., Dahlstedt, Å., et al. (2007). Requirements engineering challenges in market-driven software development – An interview study with practitioners. Information and Software Technology, 49, 588–604.

    Article  Google Scholar 

  • Kaulio, M. A. (1998). Customer, consumer and user involvement in product development: A framework and a review of selected methods. Total Quality Management, 9(1), 141–149.

    Article  Google Scholar 

  • Khurum, M., Gorschek, T., et al. (2011). A homogeneous and consolidated view of software value. Decision support for product management of software intensive products. M. Khurum, Blekinge Institute of Technology, Doctoral Dissertations Series (Vol. 12), 2011.

    Google Scholar 

  • Kilpi, T. (1997). Product management challenge to software change process: Preliminary results from three SMEs experiment. Software Process Improvement and Practice, 3(3), 165–175.

    Article  Google Scholar 

  • Kim, J. & Park, Y. (2010). Identifying a new service opportunity from potential needs: User-centric service map. IEEE international conference on industrial engineering and engineering management (IEEM 2010), Macao.

    Google Scholar 

  • Kitchenham, B., & Pfleeger, S. L. (1996). Software quality: The elusive target. IEEE Software, 13(1), 12–21.

    Article  Google Scholar 

  • Kittlaus, H.-B., & Clough, P. (2009). Software product management and pricing. New York: Springer.

    Google Scholar 

  • Konig, S. J. (2009). Finance as a stakeholder in product management. Third international workshop on software product management (IWSPM 2009), Atlanta, GA.

    Google Scholar 

  • Kotler, P., Armstrong, G. (2011). Principles of marketing. Pearson Prentice Hall. Upper Saddle River, NJ, USA.

    Google Scholar 

  • Krishna, S., Sahay, S., et al. (2004). Managing cross-cultural issues in global software outsourcing. Communications of the ACM, 47(4), 62–66.

    Article  Google Scholar 

  • Kuczmarski, T. D. (2000). Measuring your return on innovation. Marketing Management, 9(1), 24–32.

    Google Scholar 

  • Lawley, B. (2007). Expert product management. HappyAbout.info.

    Google Scholar 

  • Lee, E. (2000). What’s ahead for embedded software? Computer, 33(9), 18–26.

    Article  Google Scholar 

  • Lehman, M. M. (1980). Programs, life cycles, and laws of software evolution. Proceedings of the IEEE, 68(9), 1060–1076.

    Article  Google Scholar 

  • Lehmann, D., & Winer, R. (2005). Product management. Burr Ridge, IL: McGraw-Hill.

    Google Scholar 

  • Lehtola, L., & Kauppinen, M. (2006). Suitability of requirements prioritization methods for market-driven software product development. Software Process Improvement and Practice, 11, 7–19.

    Article  Google Scholar 

  • Lehtola, L., Kauppinen, M., et al. (2005). Linking the business view to requirements engineering: Long-term product planning by roadmapping. 13th IEEE international conference on requirements engineering (RE’05), Paris, France.

    Google Scholar 

  • Lerner, J., & Tirole, J. (2002). Some simple economics of open source. The Journal of Industrial Economics, 50(2), 197–234.

    Google Scholar 

  • Lynn, G. S., & Akgün, A. E. (2001). Project visioning: Its components and impact on new product success. Journal of Product Innovation Management, 18(6), 374–387.

    Article  Google Scholar 

  • Mangold, W. G., & Faulds, D. J. (2009). Social media: The new hybrid element of the promotion mix. Business Horizons, 52(4), 357–365.

    Article  Google Scholar 

  • Martin, R. C., & Meinik, G. (2008). Tests and requirements, requirements and tests: A möbius strip. IEEE Software, 25(1), 54–59.

    Article  Google Scholar 

  • McGrath, M. E. (2001). Product strategy for high technology companies: Accelerating your business to web speed. New York: McGraw-Hill.

    Google Scholar 

  • Messerschmitt, D., & Szyperski, C. (2003). Software ecosystem: Understanding an indispensable technology and industry. London: The MIT Press.

    Google Scholar 

  • Meyer, M., Zarnekow, R., et al. (2003). IT-governance: Begriff, Status quo und Bedeutung. Wirtschaftsinformatik, 45(4), 445–448.

    Article  Google Scholar 

  • Miller, K. D. (1992). A framework for integrated risk management in international business. Journal of International Business Studies, 23(2), 311–331.

    Article  Google Scholar 

  • Miller, R. (2010). Apps: Exploring the next content frontier. EContent, 33(5), 18–22.

    Google Scholar 

  • Nagle, T. T., & Hogan, J. E. (2006). The strategy and tactics of pricing: A guide to growing more profitably. Upper Saddle River: Pearson Prentice Hall.

    Google Scholar 

  • Open Source Initiative. (2012). Open source licenses by category. Retrieved February 12, 2012, from http://www.opensource.org/licenses/category

  • Pech, E. (2006). Making innovation happen. Annual Review of Communications, 59, 169–172.

    Google Scholar 

  • Phaal, R., & Muller, G. (2009). An architectural framework for roadmapping: Towards visual strategy. Technological Forecasting & Social Chane, 76(1), 39–49.

    Article  Google Scholar 

  • Phaal, R., Farrukh, C., et al. (2003). Technology roadmapping – A planning framework for evolution and revolution. Technological Forecasting and Social Change, 71, 5–26.

    Article  Google Scholar 

  • Phaal, R., Farrukh, C., et al. (2007). Strategic roadmapping: A workshop-based approach for identifying and exploring strategic issues and opportunities. Engineering Management Journal, 19(1), 3–12.

    Google Scholar 

  • Phippen, A., Sheppard, L., et al. (2004). A practical evaluation of web analytics. Internet Research, 14(4), 284–293.

    Article  Google Scholar 

  • Pichler, R. (2010). Agile product management with scrum. Addison-Wesley Pearson Education, Boston, MA, USA.

    Google Scholar 

  • Piercy, N., & Giles, W. (1989). Making SWOT analysis work. Marketing Intelligence & Planning, 7(5/6), 5–7.

    Article  Google Scholar 

  • Pohl, K., Böckle, G., et al. (2005). Software product line engineering: Foundations, principles and techniques. Berlin: Springer.

    Google Scholar 

  • Pohl, K., & Rupp, C. (2011). Requirements engineering fundamentals: A study guide for the certified professional for requirements engineering exam – Foundation level – IREB compliant. Rocky Nook Computing.

    Google Scholar 

  • Popp, K. M., & Meyer, R. (2010). Profit from software ecosystems. Books on Demand.

    Google Scholar 

  • Porter, M. E. (1980). Competitive strategy. New York: Free Press.

    Google Scholar 

  • Porter, M. (1998). Competitive advantage: Creating and sustaining superior performance. New York: Free Press.

    Google Scholar 

  • Potts, C., Takahashi, K., et al. (1994). Inquiry-based requirements analysis. IEEE Software, 11(2), 21–32.

    Article  Google Scholar 

  • Pragmatic Marketing. (2012). Pragmatic marketing framework. Retrieved February 26, 2012, from http://www.pragmaticmarketing.com/pragmatic-marketing-framework

  • Project Management Institute. (2004). A guide to the project management body of knowledge. PMBOK Guide. ANSI/PMI 99-001-2004.

    Google Scholar 

  • Pruitt, J., & Grudin, J. (2003). Personas: Practice and theory. 2003 conference on designing for user experience (DUX’03), New York.

    Google Scholar 

  • Raijlich, V. T., & Bennet, K. H. (2000). A staged model for the software life cycle. Computer, 33(7), 66–71.

    Article  Google Scholar 

  • Regnell, B., & Brinkkemper, S. (2005). Market-driven requirements engineering for software products. In A. Aurum & C. Wohlin (Eds.), Engineering and managing software requirements (pp. 287–308). Berlin: Springer.

    Chapter  Google Scholar 

  • Regnell, B., Svensson, R. B., et al. (2008). Supporting roadmapping of quality requirements. IEEE Software, 25(2), 42–47.

    Article  Google Scholar 

  • Reifer, D. J. (2002). Making the software business case: Improvement by the numbers. New York: Addison-Wesley.

    Google Scholar 

  • Rhoton, J. (2010). Cloud computing explained: Implementation handbook for enterprises. Recursive Press, Kent, United Kingdom

    Google Scholar 

  • Roussos, G., Marsh, A. J., et al. (2005). Enabling pervasive computing with smart phones. Pervasive Computing, 4(2), 20–27.

    Article  Google Scholar 

  • Ruffin, M., & Ebert, C. (2004). Using open source software in product development: A primer. IEEE Software, 21(1), 82–86.

    Article  Google Scholar 

  • Rus, I., & Lindvall, M. (2002). Knowledge management in software engineering. IEEE Software, 19(3), 26–38.

    Article  Google Scholar 

  • Schmidt, M. (2002). The business case guide. Boston: Solution Matrix.

    Google Scholar 

  • Shapiro, C. (1989). The theory of business strategy. The RAND Journal of Economics, 20(1), 125–137.

    Article  Google Scholar 

  • Sneed, H., Hasitschka, M., et al. (2005). Software-Produktmanagement: Wartung und Weiterentwicklung bestehender Anwendungssysteme, dpunkt.verlag.

    Google Scholar 

  • Spalding, G., & Case, G. (2007). ITIL continual service improvement. The Stationery Office.

    Google Scholar 

  • Steinhardt, G. (2012). PTMK action model. Retrieved February 26, 2012, from http://www.blackblot.com/pmtk-action-model/

  • Svahnberg, M., Gorschek, T., et al. (2009). A systematic review on strategic release planning models. Information and Software Technology, 52, 237–248.

    Article  Google Scholar 

  • Teece, D. J., Pisano, G., et al. (1997). Dynamic capabilities and strategic management. Strategic Management Journal, 18(7), 509–533.

    Article  Google Scholar 

  • Tessarolo, P. (2007). Is integration enough for fast product development? An empirical investigation of the contextual effects of product vision. Journal of Product Innovation Management, 24(1), 69–82.

    Article  Google Scholar 

  • Trott, P. (2011). Innovation management and new product development. London: Prentice Hall Financial Times.

    Google Scholar 

  • Turner, M., Budgen, D., et al. (2003). Turning software into a service. Computer, 36(10), 38–44.

    Article  Google Scholar 

  • Vähäniitty, J., Lassenius, C., et al. (2002). An approach to product roadmapping in small software product businesses. 7th international conference on software quality (ECSQ 2002), Helsinki, Finland, Portland, Oregon, USA.

    Google Scholar 

  • van de Weerd, I., Brinkkemper, S., et al. (2006). On the creation of a reference framework for software product management: Validation and tool support. International workshop on software product management, Minneapolis.

    Google Scholar 

  • van de Weerd, Inge, S. B., et al. (2006). Towards a reference framework for software product management. 14th IEEE international requirements engineering conference (RE’06). Minneapolis: IEEE Computer Society.

    Google Scholar 

  • van der Hoek, A., & Wolf, A. (2003). Software release management for component-based software. Software: Practice and Experience, 33(1), 77–98.

    Article  Google Scholar 

  • Variant, H. (2000). Buying, sharing and renting information goods. The Journal of Industrial Economics, 48(4), 473–488.

    Google Scholar 

  • Wallin, C., Ekdahl, F., et al. (2002). Integrating business and software development models. IEEE Software, 19(6), 28–33.

    Article  Google Scholar 

  • Ward, J. L., & Peppard, J. (2002). Strategic planning for information systems. Chichester: Wiley.

    Google Scholar 

  • Wernerfelt, B. (1984). A resource-based view of the firm. Strategic Management Journal, 5(2), 171–180.

    Article  Google Scholar 

  • Wohlin, C., & Aurum, A. (2005). What is important when deciding to include a software requirement into a project or release. International symposium on empirical software engineering (ISESE 2005), Noosa Heads, Australia.

    Google Scholar 

  • Wu, F. F., Moslehi, K., et al. (2005). Power system control centers: Past, present, and future. Proceedings of the IEEE, 93(11), 1890–1908.

    Article  Google Scholar 

  • Xu, L., & Brinkkemper, S. (2007). Concepts of product software. European Journal of Information Systems, 16(5), 531–541.

    Article  Google Scholar 

  • Yourseff, L., Butrico, M., et al. (2008). Toward a unified ontology of cloud computing. Grid computing environments workshop (GCE’08), Santa Barbara.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Blekinge Institute of Technology - School of Computing, Karlskrona, Sweden

    Samuel A. Fricker

Authors
  1. Samuel A. Fricker
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Samuel A. Fricker .

Editor information

Editors and Affiliations

  1. , Chair of Information Systems IV, University of Mannheim, L 15 1-6, Mannheim, 68131, Germany

    Alexander Maedche

  2. , Chair of Information Systems IV, University of Mannheim, L 15 1-6, Mannheim, 68131, Germany

    Achim Botzenhardt

  3. CAS Software AG, Wilhelm-Schickard-Str. 12, Karlsruhe, 76131, Germany

    Ludwig Neer

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Fricker, S.A. (2012). Software Product Management. In: Maedche, A., Botzenhardt, A., Neer, L. (eds) Software for People. Management for Professionals. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-31371-4_4

Download citation

Publish with us

Policies and ethics

Search

Navigation