Pub Date : 2019-01-01DOI: 10.1007/978-3-030-19871-8_9
Timo Wagenblatt
{"title":"Organizational Maturity","authors":"Timo Wagenblatt","doi":"10.1007/978-3-030-19871-8_9","DOIUrl":"https://doi.org/10.1007/978-3-030-19871-8_9","url":null,"abstract":"","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"58 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"2019-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"84569973","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Product development organizations often distribute the responsibilities for requirements engineering over several roles. The collaboration of product management, concerned with market needs, and product development, concerned with the technological aspects of a product, is well established. Such shared responsibility provides advantages in the utilization of specific knowledge, skills, and resources. However, the collaboration leads to increased demands on coordination. Novel concepts and models need to be investigated to support such collaborative requirements engineering. In this paper we focus on requirements communication from product management to a development team by proposing and evaluating the model of goal-oriented requirements communication. The model explains how efficiency and effectiveness of requirements communication can be increased and allows the utilization of established requirements engineering knowledge in a new way to address the task of requirements communication.
{"title":"Goal-Oriented Requirements Communication in New Product Development","authors":"Samuel Fricker, T. Gorschek, M. Glinz","doi":"10.1109/IWSPM.2008.2","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.2","url":null,"abstract":"Product development organizations often distribute the responsibilities for requirements engineering over several roles. The collaboration of product management, concerned with market needs, and product development, concerned with the technological aspects of a product, is well established. Such shared responsibility provides advantages in the utilization of specific knowledge, skills, and resources. However, the collaboration leads to increased demands on coordination. Novel concepts and models need to be investigated to support such collaborative requirements engineering. In this paper we focus on requirements communication from product management to a development team by proposing and evaluating the model of goal-oriented requirements communication. The model explains how efficiency and effectiveness of requirements communication can be increased and allows the utilization of established requirements engineering knowledge in a new way to address the task of requirements communication.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"54 1","pages":"27-34"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80422628","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Richard Berntsson-Svensson, Thomas Olsson, B. Regnell
In market-driven product development and release planning, it is important to market success to find the right balance among competing quality requirements. To address this issue, a conceptual model that incorporates quality as a dimension in addition to the cost and value dimensions used in prioritisation approaches for functional requirements has been developed. In this paper, we present an industrial evaluation of the model. The results indicate that the quality performance model provides helpful information about quality requirements in release planning. All subjects stated that the most difficult estimations may be more accurate by using the quality performance model.
{"title":"Introducing Support for Release Planning of Quality Requirements — An Industrial Evaluation of the QUPER Model","authors":"Richard Berntsson-Svensson, Thomas Olsson, B. Regnell","doi":"10.1109/IWSPM.2008.4","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.4","url":null,"abstract":"In market-driven product development and release planning, it is important to market success to find the right balance among competing quality requirements. To address this issue, a conceptual model that incorporates quality as a dimension in addition to the cost and value dimensions used in prioritisation approaches for functional requirements has been developed. In this paper, we present an industrial evaluation of the model. The results indicate that the quality performance model provides helpful information about quality requirements in release planning. All subjects stated that the most difficult estimations may be more accurate by using the quality performance model.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"6 1 1","pages":"18-26"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"86418363","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
New Lanchester theory links business objectives to market share using a quantitative model. It can be effectively used for deciding which new features to add to software products for winning a business. This paper introduces the new Lanchester theory and explains its use for effectively prioritizing requirements. It explains the theory for requirement experts and shows how the new Lanchester theory relates to quality function deployment, the six sigma way of managing requirements.
{"title":"New Lanchester Theory for Requirements Prioritization","authors":"Thomas Fehlmann","doi":"10.1109/IWSPM.2008.6","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.6","url":null,"abstract":"New Lanchester theory links business objectives to market share using a quantitative model. It can be effectively used for deciding which new features to add to software products for winning a business. This paper introduces the new Lanchester theory and explains its use for effectively prioritizing requirements. It explains the theory for requirement experts and shows how the new Lanchester theory relates to quality function deployment, the six sigma way of managing requirements.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"273 1","pages":"35-40"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"74220279","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Nina Dzamashvili-Fogelström, T. Gorschek, Mikael Svahnberg
The need of understanding and supporting requirements engineering decisions in market-driven product development is motivated by the complexity and economical impact of these decisions. While being a key for success, correct and timely decisions are dependent on the availability and the quality of decision material (requirements, business cases, cost-value estimations etc). This paper presents a needs-oriented framework (NORM) for identifying and assuring the creation of appropriate decision material for RE decisions. NORM is based on analysis of the applied RE process and characteristics of separate RE decisions, focusing mainly on pre-project activities. The framework is developed in close cooperation with industry with the intention to ensure that resources are spent on producing just-the-necessary information at the right time and to be able to monitor and control this production effort.
{"title":"Needs Oriented Framework for Producing Requirements Decision Material - NORM","authors":"Nina Dzamashvili-Fogelström, T. Gorschek, Mikael Svahnberg","doi":"10.1109/IWSPM.2008.5","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.5","url":null,"abstract":"The need of understanding and supporting requirements engineering decisions in market-driven product development is motivated by the complexity and economical impact of these decisions. While being a key for success, correct and timely decisions are dependent on the availability and the quality of decision material (requirements, business cases, cost-value estimations etc). This paper presents a needs-oriented framework (NORM) for identifying and assuring the creation of appropriate decision material for RE decisions. NORM is based on analysis of the applied RE process and characteristics of separate RE decisions, focusing mainly on pre-project activities. The framework is developed in close cooperation with industry with the intention to ensure that resources are spent on producing just-the-necessary information at the right time and to be able to monitor and control this production effort.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"6201 1","pages":"9-17"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"83933656","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Depending on the perspectives and the stage within the life cycle IT product are viewed and managed differently. A model is presented that integrates different perspectives and stages serving as an aid for the analysis of business models purposeful and focused positioning of IT-products. Four generic business models are analysed with regard to the product management function in general and the positioning field for IT-products specifically: off-the-shelf, license plus service, project, and system service.
{"title":"Guidelines for the Analysis of IT Business Models and Strategic Positioning of IT-Products","authors":"G. Herzwurm, W. Pietsch","doi":"10.1109/IWSPM.2008.3","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.3","url":null,"abstract":"Depending on the perspectives and the stage within the life cycle IT product are viewed and managed differently. A model is presented that integrates different perspectives and stages serving as an aid for the analysis of business models purposeful and focused positioning of IT-products. Four generic business models are analysed with regard to the product management function in general and the positioning field for IT-products specifically: off-the-shelf, license plus service, project, and system service.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"69 1","pages":"1-8"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80937100","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Agile requirements engineering is the approach of choice for many software producers whose realities include highly uncertain requirements, use of new development technology, and clients willing to explore the ways in which an evolving product can help their business goals. From customer's perspective, the activity of continuous requirements reprioritization forms the very core of today's agile approaches. However, the freedom for clients to do so does not come for free. This paper presents results of a literature review on agile requirements prioritization methods, derives a conceptual model for understanding the inter-iteration prioritization process in terms of inputs and outcomes, and identifies issues and solutions pertinent to agile prioritization. The latter are derived from the authors' experiences and by using empirical data, published earlier by other authors.
{"title":"Supporting the Dynamic Reprioritization of Requirements in Agile Development of Software Products","authors":"Zornitza Bakalova, M. Daneva, L. Buglione","doi":"10.1109/IWSPM.2008.7","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.7","url":null,"abstract":"Agile requirements engineering is the approach of choice for many software producers whose realities include highly uncertain requirements, use of new development technology, and clients willing to explore the ways in which an evolving product can help their business goals. From customer's perspective, the activity of continuous requirements reprioritization forms the very core of today's agile approaches. However, the freedom for clients to do so does not come for free. This paper presents results of a literature review on agile requirements prioritization methods, derives a conceptual model for understanding the inter-iteration prioritization process in terms of inputs and outcomes, and identifies issues and solutions pertinent to agile prioritization. The latter are derived from the authors' experiences and by using empirical data, published earlier by other authors.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"8 1","pages":"49-58"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"82573630","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
W. Bekkers, I. D. Weerd, S. Brinkkemper, A. Mahieu
Current research in the field of software product management (SPM) and software process improvement does not take the situational context of a company into account. Taking the context into account, allows small and medium sized companies to improve their SPM processes in a more optimal manner. This research shows that situational factors (SFs) influence the selection process of method fragments for SPM in two applications: SPM process maintenance - the influence level of SFs on the SPM processes: if the SF changes value the SPM process may need to be changed; and method fragment choice - selecting a method which fits the situational context of the company. This paper presents a list of 27 situational factors in 5 categories, relevant to SPM, with the level of influence they have on the selection of (parts of) methods.
{"title":"The Influence of Situational Factors in Software Product Management: An Empirical Study","authors":"W. Bekkers, I. D. Weerd, S. Brinkkemper, A. Mahieu","doi":"10.1109/IWSPM.2008.8","DOIUrl":"https://doi.org/10.1109/IWSPM.2008.8","url":null,"abstract":"Current research in the field of software product management (SPM) and software process improvement does not take the situational context of a company into account. Taking the context into account, allows small and medium sized companies to improve their SPM processes in a more optimal manner. This research shows that situational factors (SFs) influence the selection process of method fragments for SPM in two applications: SPM process maintenance - the influence level of SFs on the SPM processes: if the SF changes value the SPM process may need to be changed; and method fragment choice - selecting a method which fits the situational context of the company. This paper presents a list of 27 situational factors in 5 categories, relevant to SPM, with the level of influence they have on the selection of (parts of) methods.","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"41 1","pages":"41-48"},"PeriodicalIF":0.0,"publicationDate":"2008-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89337427","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2002-01-01DOI: 10.1007/978-3-8349-9233-8
M. Gaulke
{"title":"Risikomanagement in IT-Projekten","authors":"M. Gaulke","doi":"10.1007/978-3-8349-9233-8","DOIUrl":"https://doi.org/10.1007/978-3-8349-9233-8","url":null,"abstract":"","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"206 1","pages":"41-48"},"PeriodicalIF":0.0,"publicationDate":"2002-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"77059073","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1997-01-01DOI: 10.1007/978-3-322-85166-6_3
P. Elzer
{"title":"SW-Management im Wandel","authors":"P. Elzer","doi":"10.1007/978-3-322-85166-6_3","DOIUrl":"https://doi.org/10.1007/978-3-322-85166-6_3","url":null,"abstract":"","PeriodicalId":6435,"journal":{"name":"2008 Second International Workshop on Software Product Management","volume":"66 1","pages":"48-62"},"PeriodicalIF":0.0,"publicationDate":"1997-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"76962425","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：