Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Proceedings of the Conference on The Future of Software Engineering
Software Development
Value-based software engineering (VBSE): a value-driven approach to product-line engineering
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
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
Quest for a Silver Bullet: Creating Software Product Value through Requirements Selection
EUROMICRO '06 Proceedings of the 32nd EUROMICRO Conference on Software Engineering and Advanced Applications
Marketplace Issues in Software Planning and Design
IEEE Software
Value based management and agile methods
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
A value-based approach in requirements engineering: explaining some of the fundamental concepts
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
When Product Managers Gamble with Requirements: Attitudes to Value and Risk
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
Balancing software product investments
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
A systematic review on strategic release planning models
Information and Software Technology
A conceptual model of client-driven agile requirements prioritization: results of a case study
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Proceedings of the 11th International Conference on Product Focused Software
Bridging the gap between software product management and software project management
Proceedings of the 11th International Conference on Product Focused Software
Agile requirements prioritization: what happens in practice and what is described in literature
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
Eliciting user requirements using Appreciative inquiry
Empirical Software Engineering
Business value is not only dollars – results from case study research on agile software projects
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
International Journal of Information Management: The Journal for Information Professionals
Estimating the software product value during the development process
PROFES'12 Proceedings of the 13th international conference on Product-Focused Software Process Improvement
Equality in cumulative voting: A systematic review with an improvement proposal
Information and Software Technology
Context aware exception handling in business process execution language
Information and Software Technology
A systematic literature review of software requirements prioritization research
Information and Software Technology
Hi-index | 0.00 |
It is important for a software company to maximize value creation for a given investment. The purpose of requirements engineering activities is to add business value that is accounted for in terms of return on investment of a software product. This paper provides insight into the release planning processes used in the software industry to create software product value, by presenting three case studies. It examines how IT professionals perceive value creation through requirements engineering and how the release planning process is conducted to create software product value. It also presents to what degree the major stakeholders' perspectives are represented in the decision-making process. Our findings show that the client and market base of the software product represents the most influential group in the decision to implement specific requirements. This is reflected both in terms of deciding the processes followed and the decision-making criteria applied when selecting requirements for the product. Furthermore, the management of software product value is dependant on the context in which the product exists. Factors, such as the maturity of the product, the marketplace in which it exists, and the development tools and methods available, influence the criteria that decide whether a requirement is included in a specific project or release.