A Survey on Software Release Planning Models

Ameller, David; Farré, Carles; Franch, Xavier; Rufian, Guillem

doi:10.1007/978-3-319-49094-6_4

Cited by 32 publications

(36 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Once these values are determined, weighted averages taking into account stakeholder weights wstake(s) are determined similar to Equations (1) and (2). It is known that the whole AHP process provides more reliable scores.…”

Section: Pair-wise Comparison Of Features By Ahpmentioning

confidence: 99%

Asymmetric Release Planning: Compromising Satisfaction against Dissatisfaction

Nayebi

Ruhe

2019

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Maximizing satisfaction from offering features as part of the upcoming release(s) is different from minimizing dissatisfaction gained from not offering features. This asymmetric behavior has never been utilized for product release planning. We study Asymmetric Release Planning (ARP) by accommodating asymmetric feature evaluation. We formulated and solved ARP as a bicriteria optimization problem. In its essence, it is the search for optimized trade-offs between maximum stakeholder satisfaction and minimum dissatisfaction. Different techniques including a continuous variant of Kano analysis are available to predict the impact on satisfaction and dissatisfaction with a product release from offering or not offering a feature. As a proof of concept, we validated the proposed solution approach called Satisfaction-Dissatisfaction Optimizer (SDO) via a real-world case study project. From running three replications with varying effort capacities, we demonstrate that SDO generates optimized trade-off solutions being (i) of a different value profile and different structure, (ii) superior to the application of random search and heuristics in terms of quality and completeness, and (iii) superior to the usage of manually generated solutions generated from managers of the case study company. A survey with 20 stakeholders evaluated the applicability and usefulness of the generated results.

show abstract

Section: Pair-wise Comparison Of Features By Ahpmentioning

confidence: 99%

Asymmetric Release Planning: Compromising Satisfaction against Dissatisfaction

Nayebi

Ruhe

2019

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Ernst and Mylopoulos analyzed open source projects and concluded that there are large differences among projects and no clear correlation to the project age [13]. Concerning release planning, Ameller et al report that most models provide "simple output for which requirements to implement in the next release" [14]. Others have identified an under-emphasis of product quality and difficulties in handling cross-cutting concerns across teams with agile methodologies [15].…”

Section: Introductionmentioning

confidence: 99%

QREME – Quality Requirements Management Model for Supporting Decision-Making

Olsson

Wnuk²

2018

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Context and motivation] Quality requirements (QRs) are inherently difficult to manage as they are often subjective, context-dependent and hard to fully grasp by various stakeholders. Furthermore, there are many sources that can provide input on important QRs and suitable levels. Responding timely to customer needs and realizing them in product portfolio and product scope decisions remain the main challenge.[Question/problem] Data-driven methodologies based on product usage data analysis gain popularity and enable new (bottom-up, feedback-driven) ways of planning and evaluating QRs in product development. Can these be efficiently combined with established top-down, forward-driven management of QRs? [Principal idea / Results] We propose a model for how to handle decisions about QRs at a strategic and operational level, encompassing product decisions as well as business intelligence and usage data. We inferred the model from an extensive empirical investigation of five years of decision making history at a large B2C company. We illustrate the model by assessing two industrial case studies from different domains.[Contribution] We believe that utilizing the right approach in the right situation will be key for handling QRs, as both different groups of QRs and domains have their special characteristics.

show abstract

“…A literature review of the SRP models proposed in the academic literature can be found in [3]. In that survey, in which some of the authors of this paper participated, up to 17 SRP models published in 2009-2016 were identified and analysed.…”

Section: Related Workmentioning

confidence: 99%

“…Most of these solutions only provided some proof-of-concept tool support. The only exception to the last point is ReleasePlanner [4], a commercial SRP tool used by some of the SRP models discussed in [3]. However, ReleasePlanner only addresses strategic planning.…”

Section: Related Workmentioning

confidence: 99%

Replan: A Release Planning Tool

Ameller

Farré

Franch

et al. 2017

2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)

Self Cite

View full text Add to dashboard Cite

Abstract-Software release planning is the activity of deciding what is to be implemented, when and by who. It can be divided into two tasks: strategic planning (i.e., the what) and operational (i.e., the when and the who). Replan, the tool that we present in this demo, handles both tasks in an integrated and flexible way, allowing its users (typically software product managers and developer team leaders) to (re)plan the releases dynamically by assigning new features and/or modifying the available resources allocated at each release. A recorded video demo of Replan is available at https://youtu.be/PNK5EUTdqEg.

show abstract

A Survey on Software Release Planning Models

Cited by 32 publications

References 13 publications

Asymmetric Release Planning: Compromising Satisfaction against Dissatisfaction

Asymmetric Release Planning: Compromising Satisfaction against Dissatisfaction

QREME – Quality Requirements Management Model for Supporting Decision-Making

Replan: A Release Planning Tool

Contact Info

Product

Resources

About