Consumer preference measurement is a quantitative field of study for modeling, collecting and analyzing product decisions by consumers. Discovering how consumers choose products is an important area of marketing research and recognized as a successful partnership between academic theory and practice over the past forty years. Despite preference measurement’s success in consumer products, little guidance is available for its application to software product management. This paper assesses the feasibility of applying advanced preference measurement techniques to software products and suggests a framework for conducting such studies. A summary of the methods is provided to give guidance to software product managers seeking to apply preference measurement to common product decisions. The paper concludes by recommending a technique called ‘maximum difference scaling’ to elicit customer feedback to help measure the importance of new features for software product improvement. / text

This thesis investigates the concept of citizen developers, in which employees in an organisation take on the role of developers and create software using low-code tools. The primary focus of this report is to examine the necessary steps an organisation must take when introducing citizen developers, particularly regarding solution maintenance. The purpose, therefore, is to establish a foundation for utilising the concept of citizen developers in the workplace, bridging the gap between users and developers. Furthermore, this study aims to explore the organisational structure required to incorporate citizen developers and identify the advantages and drawbacks associated with an organisational structure tailored for citizen developers. Citizen developers possess distinct roles and responsibilities within an organisation, making them experts in their respective fields. This expertise renders citizen developers a valuable resource, as they develop solutions to enhance their own work efficiency and effectiveness. A case company has been selected for this study, and interviews have been conducted with multiple employees from the organisation. Through analysis of these interviews and a comprehensive literature review, a governance model has been developed. The governance model delineates the level of responsibility citizen developers should assume, and an evaluation of the model also uncovers potential advantages and drawbacks of introducing citizen developers within an organisation. Ultimately, this thesis aims to contribute to research on the subject of citizen developers, with particular emphasis on solution maintenance.

Context. Successful software product management concerns about developing right software products for right markets at the right time. The product manager, who carries responsibilities of planning, requires but does not always have access to high-quality information for making the best possible planning decisions. The following master thesis concentrates on proposing a solution that supports planning of a software product by means of analytics. Objectives. The aim of the master thesis is to understand potentials of analytics in product planning decisions in a SaaS context. This thesis focuses on SaaS based analytics used for portfolio management, product roadmapping, and release planning and specify how the analytics can be utilized for planning of a software product. Then the study devises an analytics-based method to enable software product planning. Methods. The current study was designed with a mixed methodology approach, which includes the literature review and survey researches as well as case study under the framework of the design science. Literature review was conducted to identify product planning decisions and the measurements that support them. A total of 17 interview based surveys were conducted to investigate the impact of analytics on product planning decisions in product roadmapping context. The result of the interviews ended in an analytics-based planning method provided under the framework of design science. The designed analytics-based method was validated by a case study in order to measure the effectiveness of the solution. Results. The identified product planning decisions were summarized and categorized into a taxonomy of decisions divided by portfolio management, roadmapping, and release planning. The identified SaaS-based measurements were categorized into six categories and made a taxonomy of measurements. The result of the survey illustrated that importance functions of the measurement- categories are not much different for planning-decisions. In the interviews 61.8% of interviewees selected “very important” for “Product”, 58.8% for “Feature”, and 64.7% for “Product healthiness” categories. For “Referral sources” category, 61.8% of responses have valuated as “not important”. Categories of “Technologies and Channels” and “Usage Pattern” have been rated majorly “important” by 47.1% and 32.4% of the corresponding responses. Also the results showed that product use, feature use, users of feature use, response time, product errors, and downtime are the first top measurement- attributes that a product manager prefers to use for product planning. Qualitative results identified “product specification, product maturity and goal” as the effected factors on analytics importance for product planning and in parallel specified strengths and weaknesses of analytical planning from product managers’ perspectives. Analytics-based product planning method was developed with eleven main process steps, using the measurements and measurement scores resulted from the interviews, and finally got validated in a case. The method can support all three assets of product planning (portfolio management, roadmapping, and release planning), however it was validated only for roadmapping decisions in the current study. SaaS-based analytics are enablers for the method, but there might be some other analytics that can assist to take planning decisions as well. Conclusion. The results of the interviews on the roadmapping decisions indicated that different planning decisions consider similar importance for measurement-categories to plan a software product. Statistics about feature use, product use, response time, users, error and downtime have been recognized as the most important measurements for planning. Analytics increase knowledge about product usability and functionality, and also can assist to improve problem handling and client-side technologies. But it has limitations regarding to receiving formed-based customer feedback, handling development technologies and also interpreting some measurements in practice. Immature products are not able to use analytics. To create, remove, or enhance a feature, the data trend provides a wide view of feature desirability in the current or even future time and clarifies how these changes can impact decision making. Prioritizing features can be performed for the features in the same context by comparing their measurement impacts. The analytics-based method covers both reactive and proactive planning.

Context: At the core of choosing what features and level of quality to realize, and thus offer a market or customer, rests on the ability to take decisions. Decision-making is complicated by the diverse understanding of issues such as priority, consequence of realization, and interpretations of strategy as pertaining to the short-term and long-term development of software intensive products. The complexity is further compounded by the amount of decision support material that has to be taken into account, and the sheer volume of possible alternatives that have to be triaged and prioritized; thousands or even tens of thousands of requirements can be the reality facing a company. There is a need to develop the functionality that is strategically most significant, while satisfying customers and being competitive, time efficient, cost effective, and risk minimizing. In order to achieve a balance between these factors, all the stakeholders, within an organization, need to agree on the strategic aspects and value considerations to be considered, and their corresponding relative importance. Objective: The objective of this thesis is to provide enhanced decision support for product managers faced with decision-making challenges. This involves, but is not limited to, enhancing the alignment between the product and portfolio management with respect to product strategies, and enabling the use of value as a basis for product management and development related decisions. Method: A number of empirical studies, set in industry, have been performed. The research methods used span from systematic mapping, and systematic reviews to case studies, all aligned to identify possibilities for improvement, devise solutions, and incrementally evaluate said solutions. Close collaboration with industry partners was at the core of the research presented in this thesis. Result: The MASS method presented in this thesis can be used to evaluate strategic alignment and identify possible root causes for misalignment. To strengthen strategic alignment, the Software Value Map and corresponding decision support material, proposed in the thesis, can be used by product managers for making effective and efficient strategic decisions in relation to portfolios, products and process improvement, following a systematic and aligned process. Conclusions: The area of software product management, in the context of market-driven software intensive product development, is a field with unique challenges. The specifics of the solutions are based on industry case studies performed to gauge state-of-the-art, as well as identify the main challenges. The decision support developed takes the form of maps and frameworks that support software product management on product and portfolio level decisions, strategic alignment, value-based requirements selection, and value-based process improvement.

Business success in software industry is about deploying a product to the right market, with the right features, in the right time with a good quality. Many development projects exceed the budget, is not completed within schedule or do not reach business objectives. One key role managing the business of the product is the software product manager. The software product manager role is though seldom clearly described, competence needed is not always clear and education to become a product manager is today only offered by separate courses provided by some few private initiatives. This thesis uses a qualitative descriptive approach, the purpose with this thesis is to produce further knowledge around the software product manager role. The clarification and structure of the software product manager role is limited in academia; therefore, this research will be combined with an exploratory approach to be able to verify the empirical findings. The thesis also includes observations and data collection from actual job applications to further define the requested competences of a software product manager. This thesis has found that domain competence is the top most important competence for a software product manager. To be able to make success in the role communication skills and analytic skills are most important. The right soft skills are as important as the educated competences. The thesis conclude that the product manager role is wide and it is important to be surrounded with colleagues that support the role were there are lacking of competence in technology, business or market expertise. A successful product manager build network among people, cross-functional teams, around the product and establish an effective way to communicate with those groups. Findings suggest that software companies define the responsibilities and expectations of the product manager role. As important is to support the product manager with the input data needed to be able to perform the product manager activities. By defining the responsibilities and securing the input data needed, the product manager will have a higher probability to produce a result with an impact.

Context. Software Product Management (SPM) is an activity done by software product managers to develop products from the very first idea till the product is release to the market and providing service to customers. SPM helps software product managers to successfully maintain their product throughout product lifecycle till it is disposed of from the market. In this thesis we have studied about SPM both from the state of knowledge and state of practice to understand the different activities being followed by software product managers and concepts in those activities. Objectives. The study identifies the practices followed in SPM, both from the literature and industrial practitioners. The study also unravels the order in which they implement SPM activities. We have focused on what activities need to be focused by junior software product manager when implementing SPM and based on the inputs from software practitioners a preliminary framework was designed. Methods. Literature review was conducted to identify what are the different practices in SPM. To cover the literature related to SPM different international databases like Compendex, Inspec, IEEE Xplore, ACM Digital Library, Wiley Inter Science, Scopus, Science Direct, and Business Source Premier are selected. Articles from databases are selected between the years 1995-2011. Text books related to SPM, conference proceedings and grey literature are also used. Interviews and Survey are conducted with practitioners to identify how SPM is being implemented in organizations. We have also focused on what activities need to be implemented in SPM by junior software product managers after they take up their job. Results. Totally 133 different practices are identified related to SPM and are grouped in to their respective activities. Based on the findings a preliminary framework was designed for junior software product managers where they need to implement 22 concepts and these concepts are grouped into their respective activities which are Requirements Management, Release Planning, Product Planning, Product Roadmapping and Marketing. Conclusions. We conclude that the SPM frameworks identified through literature relate to each other and use similar activities. We also conclude that the frameworks identified from literature cover almost all of the activities implemented by software product managers during SPM when empirical research was conducted. The frameworks identified from literature don’t give a clear picture about what activities need to be focused by junior software product managers when implementing SPM. To overcome this, a preliminary framework was designed for junior software product managers based on the empirical evidence identified from interviews and survey. Moreover we conclude that a curriculum needs to be designed for SPM which clearly teaches junior software product managers regarding the activities and concepts involved in SPM and focusing more on the activities which need to be implemented by junior software product managers.

Das Software Product Line Engineering (SPLE) ist ein ganzheitlicher Ansatz zur Entwicklung und Vermarktung von Software-Produktlinien auf Basis von Software-Systemfamilien. Eine in frühen Phasen des SPLE durchzuführende Aktivität ist das Scoping, bei dem die zu realisierenden Produkte mit den zwischen ihnen bestehenden Wiederverwendungspotentialen identifiziert werden. Bei der Durchführung des Scopings steht der Produkt-Manager vor dem Problem einen Ausgleich zwischen den Bedürfnissen der Kunden und dem Aufwand der Entwicklung zu finden. Durch die bestehenden Wiederverwendungspotentiale bei Software-Systemfamilien wird die Entscheidung zusätzlich erschwert. Aufgrund der bestehenden Komplexität der Entscheidung, wird in Literatur und Praxis eine Unterstützung in Form einer statistisch-mathematischen Optimierung gefordert. Dieser Forderung nimmt sich die vorliegende Arbeit an. In ihr werden mit der Konstruktion eines Modells gewinnbeeinflussender Faktoren, einer Methode zur wertbasierten Portfolio-Optimierung und eines Prototyps zur Unterstützung der wertbasierten Portfolio-Optimierung und der anschließenden Evaluation dieser Artefakte zwei Fragen adressiert. Erstens wird geprüft, ob die Optimierung von Produkt-Portfolios bei Software-Produktlinien mit statistisch-mathematischen Verfahren unterstützt werden kann. Zweitens wird geprüft, ob die statistisch-mathematische Optimierung von Produkt-Portfolios eine akzeptierte Unterstützung von Software-Anbietern sein kann. Die Arbeit ordnet sich mit ihren Fragen in die Forschung zum Produkt-Management bei Software-Produktlinien ein und trägt die vorgenannten Artefakte bei.

Das Software Product Line Engineering (SPLE) ist ein ganzheitlicher Ansatz zur Entwicklung und Vermarktung von Software-Produktlinien auf Basis von Software-Systemfamilien. Eine in frühen Phasen des SPLE durchzuführende Aktivität ist das Scoping, bei dem die zu realisierenden Produkte mit den zwischen ihnen bestehenden Wiederverwendungspotentialen identifiziert werden. Bei der Durchführung des Scopings steht der Produkt-Manager vor dem Problem einen Ausgleich zwischen den Bedürfnissen der Kunden und dem Aufwand der Entwicklung zu finden. Durch die bestehenden Wiederverwendungspotentiale bei Software-Systemfamilien wird die Entscheidung zusätzlich erschwert. Aufgrund der bestehenden Komplexität der Entscheidung, wird in Literatur und Praxis eine Unterstützung in Form einer statistisch-mathematischen Optimierung gefordert. Dieser Forderung nimmt sich die vorliegende Arbeit an. In ihr werden mit der Konstruktion eines Modells gewinnbeeinflussender Faktoren, einer Methode zur wertbasierten Portfolio-Optimierung und eines Prototyps zur Unterstützung der wertbasierten Portfolio-Optimierung und der anschließenden Evaluation dieser Artefakte zwei Fragen adressiert. Erstens wird geprüft, ob die Optimierung von Produkt-Portfolios bei Software-Produktlinien mit statistisch-mathematischen Verfahren unterstützt werden kann. Zweitens wird geprüft, ob die statistisch-mathematische Optimierung von Produkt-Portfolios eine akzeptierte Unterstützung von Software-Anbietern sein kann. Die Arbeit ordnet sich mit ihren Fragen in die Forschung zum Produkt-Management bei Software-Produktlinien ein und trägt die vorgenannten Artefakte bei.:Abbildungsverzeichnis ix Tabellenverzeichnis xi Abkürzungsverzeichnis xii Symbolverzeichnis xiv 1 Einleitung 1 1.1 Stand der Forschung 3 1.2 Forschungsbedarf 5 1.3 Forschungskonzept 7 1.4 Verwendete Methoden und Notationen 9 1.4.1 Method Engineering 10 1.4.2 Software & Systems Process Engineering Meta-Model 12 1.4.3 Merkmaldiagramme 14 1.5 Aufbau der Arbeit 16 I Modell 17 2 Software-Ökonomie 18 2.1 Unternehmen und ihre Produkte 20 2.1.1 Eigenschaften von Software-Produkten 23 2.1.2 Vom Software-System zum Geschäftsmodell 24 2.1.3 Kosten 28 2.1.4 Erlös 31 2.2 Kunden 35 2.2.1 Nutzen und Wertvorstellung 35 2.2.2 Zahlungsbereitschaft 35 2.2.3 Kundenmodell 37 2.3 Konkurrenz und Markt 38 2.3.1 Konkurrenzmodell 38 2.3.2 Ökonomische Besonderheiten von Software-Produkten 39 2.3.3 Struktur von Software-Märkten 40 2.4 Preis 41 2.4.1 Preisbeeinflussende Faktoren 42 2.4.2 Verfahren der Preisbildung 42 2.4.3 Preismodell 44 2.5 Produkt- und Preisdifferenzierung 44 2.5.1 Typen der Preisdifferenzierung 46 2.5.2 Preisdifferenzierung mit Selbstselektion 47 2.5.3 Gewinnoptimalität 48 2.6 Zusammenfassung 49 3 Software-Produktlinien 50 3.1 Prozesse des Software Product Line Engineerings 53 3.1.1 Domain Engineering 54 3.1.2 Anwendungsentwicklung 56 3.1.3 Management 57 3.1.4 Scoping 58 3.2 Methoden des Software Product Line Engineerings 60 3.3 Szenarios des Einsatzes von Software-Systemfamilien 62 3.4 Angereicherte Software-Produktlinien 64 3.5 Kostenmodell bei Software-Systemfamilien 65 3.6 Modell gewinnbeeinflussender Faktoren 68 3.6.1 Interne Einflüsse 68 3.6.2 Externe Einflüsse 70 3.7 Zusammenfassung 71 I I Vorgehen 72 4 Methode zur wertbasierten Portfolio-Optimierung 73 4.1 Die Methode im Überblick 74 4.2 Kundenanalyse 76 4.2.1 Techniken 77 4.2.2 Einsatz 83 4.2.3 Zusammenfassung 88 4.3 Kostenanalyse 89 4.3.1 Techniken 91 4.3.2 Einsatz 94 4.3.3 Zusammenfassung 97 4.4 Konkurrenzanalyse 98 4.5 Optimierung und weitere Schritte 100 4.6 Zusammenfassung 101 5 Merkmalbasierte Generierung adaptiver Conjoint-Studien 102 5.1 Meta-Modelle 103 5.1.1 Merkmalmodelle 103 5.1.2 ACA-PE-Konfigurationen 105 5.2 Abbildung von Merkmalmodellen auf ACA-PE 106 5.2.1 Erste Überlegungen 106 5.2.2 Stufen 107 5.3 Illustrierendes Beispiel 111 5.4 Zusammenfassung 113 6 Wertbasierte Portfolio-Optimierung 114 6.1 Technische Vorbemerkungen 115 6.2 Verwandte Arbeiten 117 6.2.1 Analytische Arbeiten 117 6.2.2 Praktische Arbeiten 118 6.2.3 Besondere Ansätze 121 6.2.4 Schlussfolgerung 122 6.3 Entwurfsproblem bei Software-Produkt-Portfolios 123 6.3.1 Notationsmittel 123 6.3.2 Mathematisches Programm 125 6.4 Lösungsprozedur 126 6.4.1 Finden des optimalen Software-Produkt-Portfolios 127 6.4.2 Identifikation wichtiger Systeme 129 6.5 Illustrierendes Beispiel 129 6.6 Erweiterung 132 6.7 Zusammenfassung 133 I I I Umsetzung 134 7 Software-Prototyp zur wertbasierten Portfolio-Optimierung 135 7.1 Anforderungen 136 7.1.1 Funktional 136 7.1.2 Nicht-funktional 140 7.2 Technologiestudie 140 7.3 Entwurf 143 7.4 Implementierung 146 7.4.1 Spezifikationseditor 146 7.4.2 ACA-PE-Editor 151 7.4.3 Anwendungskern 152 7.5 Test 157 7.6 Zusammenfassung 157 8 Evaluation 158 8.1 Demonstration 158 8.2 Ergebnisgüte und Skalierbarkeit 162 8.2.1 Theoretisches Testdaten-Modell 163 8.2.2 Testtreiber und Testdatengenerator 166 8.2.3 Auswertung 167 8.3 Akzeptanz 174 8.3.1 Untersuchungsdesign 174 8.3.2 Auswertung 175 8.4 Zusammenfassung 176 9 Zusammenfassung und Ausblick 177 IV Anhang 181 Glossar 182 Literaturverzeichnis 184 A Befragungen 206 A.1 Befragung zur praktischen Relevanz der Portfolio-Optimierung 206 A.2 Experteninterview zur Akzeptanz 208 B Herleitungen 214 B.1 Struktur von Software-Märkten 214 B.2 Gewinnoptimalität der Preisdifferenzierung mit Selbstselektion 219 B.3 Preis-Subproblem für den Simplex-Algorithmus 227 B.4 Beispiel analytisch bestimmter Testdaten 228 C Modelle und Ausgaben des Prototyps 229 Wissenschaftlicher und persönlicher Werdegang 232 Selbstständigkeitserklärung 233