A spiral model of software development and enhancement
ACM SIGSOFT Software Engineering Notes
Principles of Software Engineering Management
Principles of Software Engineering Management
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
Optimizing Value and Cost in Requirements Analysis
IEEE Software
An Estimation-Based Management Framework for Enhancive Maintenance in Commercial Software Products
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
An Industrial Survey of Requirements Interdependencies in Software Product Release Plannin
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Quantitative Studies in Software Release Planning under Risk and Resource Constraints
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
Agile Estimating and Planning
The Art and Science of Software Release Planning
IEEE Software
Hybrid Intelligence in Software Release Planning
International Journal of Hybrid Intelligent Systems
| Hi-index | 0.00 |
Release planning is of key importance for incremental software product development. In conjunction with the value and the effort needed to implement features, decisions need to be made as to which features are offered in which releases. The value of features can vary over time depending on market conditions, competition, contractual constraints, and other concerns. Release dates and the specific features placed in releases need to be determined in a way that maximizes the overall value related to the investments made. The main contributions of the paper are (i) the formulation of value-driven release planning where we allow time time-dependent value functions to express the value of features potentially assigned to releases, (ii) time-dependent functions expressing the resource capacities needed for implementing features, (iii) a solution method using genetic algorithms to determine release plans allowing variation of the release dates within a pre-defined interval of feasibility, and (iv) providing a proof-of-concept for the proposed approach by running a case study.