Software Product Management (SPM) framework by Inge Van

 

Software Product Management

This chapter is the foundation of this thesis. It explains the core concepts, central themes, and definitions which build up the background of this thesis project. This chapter aims at elaborating the context of the thesis by introducing the Software Product Management (SPM) framework by Inge Van de Weerd (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006) and some Software Product Management definitions used in this thesis. The chapter starts with a question: What is Product Management? which answers what does Product Management actually mean. It is then followed by some definitions of Software Product Management which represent different viewpoints for the Software Product Management. A descriptive section of Software Product Management framework will then be explained which will contain the detailed description of all the activities of a Product Manager in Software as a Service industry as suggested by Inge Van de Weerd et al (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006). The Software Product Management activities represent the very basics of the Product Management discipline, and prioritizing them in this thesis will contribute to the Software Product Management foundations helping Product Managers around the globe.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

 

.1 What is Product Management?

Do you remember the Xerox-9200 photocopier? Or Nokia 2110? Or Myspace? They were all great products, success stories of their times. But now, they are all history, replaced by new products and technologies. The lifecycle of a product begins with an idea. But new ideas are immediately met with competition from others to get attention and only the promising ones survive to the product development stage. Even then, lots of things can go wrong. Some products are impossible to understand with all other options or they take too long to develop. If they make it through development, it is time to take them to the market. But wait! Did anyone bother to do any marketing or research market needs? Just because the product has successfully launched and has gained exposure doesn’t mean it’s in the clear. If the product is not continuously improved and managed, competitors will quickly knock it out of the market. So, everything from the ideas to commercial innovations require good Product Management.

Product Management is in-charge of constantly evaluating new market opportunity, timing and planning specific feature for maximum value, seeing to it that the successful Product Marketing is used to clearly communicate the value to the target buyers and nurturing the product’s unique lifecycle so that all investments receive their returns. On the top of this, great product managers provide winning strategy guiding every step towards success. Companies with an edge are those who follow this simple floor plan.

 

.2 Software Product Management Definitions

Software Product Management is a subject widely covering and bringing together technical and business point of views in Software Product Development. Software Product Management can also be considered from the point of view of value based software engineering as every product aims at providing additive values to the customer (Boehm, 2003) (Barney, Aurum, & Wohlin, 2008) (Ojala, 2008) (Strasunskas & Hakkarainen, 2012). However, the value concept delivered by software products is not easy to understand on common grounds and are arguable. In automotive sector, software holds a very small part out of the whole product, and therefore it is more likely to be considered as a cost center component rather than a value adding component (Biffl, Aurum, Boehm, Erdogmus, & Grünbacher, 2005). Even for the best of software products, there could be a significant contrast in the value that it provides to a customer. Some users may see performance of the software product as of significant value while some may prefer usability and reliability of a software product, and others might say customizability of the software is most important for business needs. (Dver, 2003) (Ojala, 2008) (Sunder, Mayuram, & Kannan, 2008). So, we can see that it is not easy to clearly define the perceived and the real values of a software product. They are comprised of various value aspects which should be equally considered in the software development phase of both pure software and software-intensive products (Khurum, Gorschek, & Wilson, 2012).

Haines defines Software Product Management as “business management at the product, product line, or product portfolio level” (Haines, 2008). Ebert defines Software Product Management as “the discipline and role, which governs a product (or solution, or service) from its inception to the market or customer delivery in order to generate biggest possible value to the business” (Ebert C. , 2007). Gabriel Steinhardt defines Software Product Management as “an occupational domain that is based on general management techniques that are focused on product planning and product marketing activities” (Steinhardt, 2010). Being an expert in Product Management for high-tech industries, Gabriel Steinhardt has slight difference in understanding of Product Management that Haines and Ebert. He considers Product Management as the most important strategic function in any industry. In the light of Steinhardt’s definition, — believes that the role of a Product Manager has emerged in industries specializing in software products and seems to be more of strategic value, though a bit complex to execute. The responsibility of a Product Manager comprises of portfolio management, product road-mapping, requirements management, and release planning (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006). This is in a context where many internal and external stakeholders are involved.

 

.3 Software Product Management Reference Framework

Why Reference Framework?

Currently, there are many Product Management Frameworks for Software which are followed by several companies. While some describe Product Management processes no matter what the business area is, e.g., Pragmatic Marketing (Pragmatic Marketing, 2017), others, like Software Product Management Reference Framework (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006), Software Product Management Processes (Ebert C. , 2009) and ISPMA Software Product Management Framework 1.1 (ISPMA, 2012) have been developed based on several studies and keen observations of software products. Though, these frameworks have several activities which are quite similar, but each framework has a completely different structure and use different nomenclature to represent similar activities. Table provides the key activities of the above-mentioned Software Product Management frameworks.

The Reference Software Product Management framework by Inge van de Weerd (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006) is chosen for this thesis because it provides a very composite combination of different software product management practices based on the studies and observations of mainly large software organizations. The framework divides all the Product Management activities in four main process fields: Portfolio Management, Product Roadmapping, Requirements Management, and Release Planning. All the activities are shown with their respective inputs and outputs within the framework. This framework also stands strong for the analysis according to me as compared to other frameworks shown in Table as it has been developed by the researchers unlike consultants in other cases. Additionally, there are many other activities like finance (Konig, 2009), defect management (Katchow & Van de Weerd, 2009) and software configuration management (Kilpi, 1997b) about which researchers and practitioners argue. The reference framework makes one thing very clear, that Software Product Management activities includes almost all the possible activities in an organization. A Product Manager actively works (i.e., collaborates, orchestrates and communicates) with many departments in organization which includes development, marketing, sales and support. It, therefore, becomes very important to understand that what activities solely belong to the Product Management and what activities could be passed on to other departments.

Reference SPM framework (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006)

Pragmatic Marketing Framework (Pragmatic Marketing, 2017)

Software product management processes (Ebert C. , 2009)

ISPMA Software Product Management Framework 1.1 (ISPMA, 2012)

Portfolio Management
partnering and contracting,market trend identification,product lifecycle management,product line identification

Market
market problems,win/loss analysis,distinctive competencies,competitive landscape,asset assessment

SWOT/portfolio analysis,positioning and value proposition,strategic planning and management,business case,product and technology roadmapping,voice of customer understanding,phase/gate process,project management,product definition and requirements,supplier management,engineering management,risk management,marketing planning,product launch,service and support management,service, partner, sales management,customer relationship management,marketing mix optimization

Core SPM
market analysis,product analysis,positioning and product definition,delivery model and service strategy,sourcing,business case and costing,pricing,ecosystem management,legal and IRP management,performance and risk management,product lifecycle management,roadmapping,release planning,product requirements engineering,

Product Roadmapping
theme identification,core asset identification,roadmap construction

Focus
market definition,distribution strategy,product portfolio,product roadmap

Requirements Management
requirements gathering,requirements identification,requirements organizing

Business
business plan,pricing,buy, build or partner,product profitability,innovation

Release Planning
requirements prioritization,requirements selection,release definition,release validation,launch preparation,scope change management

Planning
positioning,buying process,buyer personas,user personas,requirements,use scenarios,stakeholder communication

Participation
corporate strategy,portfolio management,innovation management,resource management

Programs
marketing plan,customer acquisition,customer retention,program effectiveness,launch plan,thought leadership,lead generation,referrals & references

Orchestration
engineering management,project management,project requirements engineering,quality management,market planning,customer analysis,opportunity management,marketing mix optimization,product launches,operational marketing,sales planning,channel preparation,customer relationship management,operational distribution,service planning and preparation,service positioning,technical support,marketing support,sales support

Readiness
sales process,collateral,sales tools,channel training

Support
presentations & demos,”special” calls,event support,channel support

Figure… represents the structure of Reference Framework for Software Product Management by Inge Van de Weerd, S. Brinkkemper, R. Nieuwenhuis, J. Versendaal and L. Bijlsma.

Figure : Reference Framework for Software Product Management (Van de Weerd, Brinkkemper, Nieuwenhuis, Versendaal, & Bijlsma, 2006)

 

 

 

Portfolio Management

 

Product portfolio management is an activity which is very closely linked with development of almost all kinds of products, including Software Products. It is a requisite for organizations in deciding what existing products do they have, what new products could be introduced by looking at the market trends and the what strategy could be followed for their product development. Product portfolio management is also responsible for taking decisions for product lifecycle, and establishing partnerships and contracts. It aims at developing a portfolio of products that is in line with customer requirements, thus leading to increase in sales, and at the same time regulates the number of products offered, thus reducing the costs and the risk of new products “cannibalizing” old products’ sales, i.e., customers buying the new product instead of an existing one (Helferich, Herzwurm, & Schockert, 2006). In an advanced stage, Product portfolio management includes planning for several generations, taking technology S-curves and technology roadmaps into account (Ulrich & Eppinger, 2000).

Portfolio management in Reference framework also positions Product Line management which could be defined as a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way (Clements & Northrop, 2001). There are many case studies that show how introduction of product line organizations improves performance (Bosch, 1991), (Brownsword & Clements, 1996), (Thiel, Ferber, Fischer, Hein, & Schlick, 2001). There has been some research done for supporting the product lines with the help of tools as proposed by Laqua (Laqua, 2002). According to him a product line content and knowledge base should be on the top of arbitrary configuration management system. Product Lifecycle Management, according to the Siemens Product Lifecycle Management Software Inc. (Product Lifecycle Management (PLM) Software, 2017), is an information management system that integrates data, processes and business systems in an extended enterprise. It is a strategic business approach which not only includes just the technologies, but also provides a consistent set of business solutions. The information should ideally be managed throughout the entire lifecycle of a product efficiently and cost-effectively from ideation, design and development through service and disposal. As an information strategy, Product Lifecycle Management helps building a coherent data structure by consolidating systems. As an enterprise strategy, Product Lifecycle Management promotes and enables global organizations to work as a single team to design, develop, support and retire products, while capturing best practices and lessons learned along the way. Product Lifecycle Management empowers any business to make unified, information-driven decisions at every stage in the product lifecycle (Product Lifecycle Management (PLM) Software, 2017).

 

References
 
Barney, S., Aurum, A., & Wohlin, C. (2008). A Product Management Challenge: Creating Software Product Value Through Requirements Selection. Journal of Systems Architecture, vol. 54, no. 6, pp. 576-593.
Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., & Grünbacher, P. (2005). Value-Based Software Engineering. 2006th ed. Springer.
Boehm, B. (2003). Value-Based Software Engineering: Reinventing. ACM Software Engineering Notes, 28(3), pp. 3-6.
Bosch, J. (1991). Product-Line Architectures in Industry: A Case Study. ICSE Proceedings, (pp. 544-554). Los Angeles, CA.
Brownsword, L., & Clements, P. (1996). A Case Study in Successful Product Line Development. Technical Report CMU/SEI-96-TR-016, Carnegie Mellon University.
Clements, P. C., & Northrop, L. M. (2001). Software Product Lines: Practices and Patterns. Addison-Wesley Professional.
Dver, A. (2003). Software Product Management Essentials. Meghan Kiffer Pr.
Ebert, C. (2007). The Impactsof Software Product Management. Journal of Systems & Software, vol. 80(no. 6), pp. 850-861.
Ebert, C. (2009). Software Product Management. Crosstalk, vol. 22, no. 1, pp. 15-19.
Haines, S. (2008). The Product Manager’s Desk Reference. McGraw-Hill.
Helferich, A., Herzwurm, G., & Schockert, S. (2006, January). The use of Quality-Function Deployment (QFD) for customer-focused Product Development. Customer Interaction and Customer Integration, pp. 217-231. Berlin.
ISPMA. (2012). International Software Product Management Association (ISPMA). Retrieved from http://ispma.org
Katchow, R., & Van de Weerd, I. (2009). On the Integration of Software Product Management with Software Defect Management in Distributed Environments. International Workshop on Software Product Management, (pp. 167-172).
Khurum, M., Gorschek, T., & Wilson, M. (2012). The software value map – an exhaustive collection of value aspects for development of software intensive products. Journal of Software: Evolution and Process, in print.
Kilpi, T. (1997b). New Challenges for Version Control and Configuration Management: A Framework and Evaluation. First Euromicro Conference on Software Maintenance and Reengineering (pp. 33-41). EUROMICRO’97.
Konig, S. (2009). Finance as a Stakeholder in Product Management. International Workshop on Software Product Management (IWSPM), (pp. 15-22).
Laqua, R. (2002). Concepts for a Product Line Knowledge Base and Variability. Proceedings of NetObjectDays 2002, (pp. 30-39).
Ojala, P. (2008). Experiences of Implementing a Value-Based Approach to Software Process and Product Assessment. World Scientific and Engineering Academy and Society (WSEAS), pp. 34-39. Stevens Point, Wisconsin, USA.
Pragmatic Marketing. (2017). Retrieved from Pragmatic Marketing: https://www.pragmaticmarketing.com/framework
Product Lifecycle Management (PLM) Software. (2017, December 21). (Siemens Product Lifecycle Management Software Inc.) Retrieved from Siemens PLM Software: https://www.plm.automation.siemens.com/global/en/our-story/glossary/product-lifecycle-management-plm-software/12506
Steinhardt, G. (2010). The Product Manager’s Toolkit: Methodologies, Processess and Tasks in High-Tech Product Management. Springer.
Strasunskas, D., & Hakkarainen, S. (2012). Domain Model-Driven Software Engineering: A Method for Discovery of Dependency Links. Information and Software Technology, vol. 54, no. 11, pp. 1239-1249.
Sunder, K., Mayuram, S. K., & Kannan, S. (2008, 11 06). Drivers of Customer Satisfaction for Software Products: Implications for Design and Service Support. Management Sciences, vol. 41, no. 9 (Sep., 1995), pp. 1456-1470. Pittsburgh, Pennsylvania, United States of America: INFORMS (Institute for Operations Research and the Management Sciences). Retrieved from http://www.jstor.org/stable/2633041
Thiel, S., Ferber, S., Fischer, T., Hein, A., & Schlick, M. (2001). A Case study in Applying a Product Line Approach for Car Periphery Supervision Systems. Proceedings of In-Vehicle Software, SAE 2001 World Congress SP-1587, (pp. 43-55). Detroit, Michigan, USA.
Ulrich, K., & Eppinger, S. (2000). Product design development. 2nd ed. Boston: Irwin McGraw-Hill.
Van de Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., & Bijlsma, L. (2006, January). A Reference Framework for Software Product Management. Towards a reference framework for Software Product Management.
Vlaanderen, K., Van de Weerd, I., & Brinkkemper, S. (2010). Improving Software Product Management Processes: a detailed view of the Product Software Knowledge Infrastructure.
 

 

x

Hi!
I'm Mack!

Would you like to get a custom essay? How about receiving a customized one?

Check it out