Release Planning in Industry: Interview Data

Release planning can be seen as company-wide optimization problem involving many stakeholders where the goal is to maximize utilization of the often limited resources of a company and turn them into business benefit. The release planning results in a decision ofwhat to include in future release(s) of a product. In making this decisionone needs to consider how to make a product profitable both in the short- and long-term. As input to release planning are a set of {em needs} that, when realized into a product, provides some business/customer value. Normally the cost of implementing all of the proposed needs is larger than the budget allocated to a release, therefore a decision needs to be made of what to include in a release and what to post-pone. Thus, the set of needs needs to be prioritized in order to maximize business value of the needs included in a release.This report documents interview data resulting from multiple case study investigating how release planning is performed in industry today. In a sense it captures state-of-the-practice for release planning.

[1]  Günther Ruhe,et al.  The art and science of software release planning , 2005, IEEE Software.

[2]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.

[3]  David A. Penny Release planning , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[4]  Ivica Crnkovic,et al.  Real world influences on software architecture - interviews with industrial system experts , 2004, Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004).

[5]  Ho-Won Jung,et al.  Optimizing Value and Cost in Requirements Analysis , 1998, IEEE Softw..

[6]  Günther Ruhe,et al.  Supporting Software Release Planning Decisions for Evolving Systems , 2005, 29th Annual IEEE/NASA Software Engineering Workshop.

[7]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[8]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[9]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..