A Method for Balancing Short- and Long-Term Investments: Quality vs. Features

There are a number of conflicting forces between short- and long-term considerations for software release planning in industry. For example, from a business perspective it is usually desired with a short time-to-market. However, from software quality perspective it is usually desired to have a longer time-to-market such that the proper architectural mechanisms can be put in place, which in the long-term reduce development cost and addresses quality aspects. In this paper we outline some of these conflicting forces, with a focus on long-lived systems, and examplify how they impact product quality and time-to-market. In this paper we propose a simple, but useful, extension of the release planning process that addresses these conflicting forces. The method is inspired from empirical data captured in a multiple case study involving 7 companies.

[1]  Barry W. Boehm,et al.  Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..

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

[3]  David Lorge Parnas,et al.  Software aging , 1994, Proceedings of 16th International Conference on Software Engineering.

[4]  Diomidis Spinellis.  Silver Bullets and Other Mysteries , 2007, IEEE Software.

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

[6]  M.M. Lehman,et al.  Programs, life cycles, and laws of software evolution , 1980, Proceedings of the IEEE.

[7]  Anders Wall,et al.  Towards a Capability Model for the Software Release Planning Process - Based on a Multiple Industrial Case Study , 2008, PROFES.

[8]  Günther Ruhe,et al.  Software release planning for evolving systems , 2005, Innovations in Systems and Software Engineering.

[9]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

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

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

[12]  Anders Wall,et al.  Importance of Software Architecture during Release Planning , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).

[13]  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).

[14]  Cmmi Product Team.  CMMI for Development, Version 1.2 , 2010 .

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

[16]  R. Land.  Software Deterioration And Maintainability – A Model Proposal , 2002 .

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

[18]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

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

[20]  J. Gosby.  MEDIA REVIEWS: Basics of Qualitative Research - Techniques and Procedures for Developing Grounded Theory 2nd Edition by A. Strauss and J. Corbin. Sage Publications, , 2000 .

[21]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[22]  Anders Wall,et al.  Key Aspects of Software Release Planning in Industry , 2008 .

[23]  Markus Lindgren,et al.  Release Planning in Industry: Interview Data , 2007 .

[24]  R. Yin.  Case Study Research: Design and Methods , 1984 .