Introducing Tool Support for Retrospective Analysis of Release Planning Decisions

  • Lena Karlsson
  • Björn Regnell
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4034)


The release planning activity in market-driven requirements engineering is crucial but difficult. The quality of the decisions on product content and release timing determines the market success, but as predictions of market value and development cost are uncertain, the decisions are not always optimal. This paper presents a prototype tool for retrospective analysis of release planning decisions based on tool requirements gathered in two previous empirical studies where retrospective analysis was done manually. The supported method enables representation of different views in the decision-making process. The results from an initial validation indicate that the retrospective analysis benefits from the supporting tool.


Analytical Hierarchy Process Release Planning Development Cost Requirement Engineer Industrial Case Study 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Beck, K.: Extreme Programming Explained. Addison-Wesley, Reading (1999)Google Scholar
  2. 2.
    Carlshamre, P.: Release Planning in Market-Driven Software Product Development: Provoking an Understanding. Requirements Engineering 7, 139–151 (2002)CrossRefGoogle Scholar
  3. 3.
    Greer, D., Ruhe, G.: Software Release Planning: an Evolutionary and Iterative Approach. Inf. and Software Techn. 46, 243–253 (2004)CrossRefGoogle Scholar
  4. 4.
    Harker, P.T.: Incomplete Pairwise Comparisons in the Analytical Hierarchy Process. Math. Modelling 9, 837–848 (1987)CrossRefMathSciNetGoogle Scholar
  5. 5.
    Kanungo, S., Monga, I.S.: Prioritizing Process Change Requests (PCRs) in Software Process Improvement. Software Process Improvement and Practice 10, 441–453 (2005)CrossRefGoogle Scholar
  6. 6.
    Karlsson, J., Ryan, K.: A Cost-Value Approach for Prioritizing Requirements. IEEE Software, 67–74 (September/October 1997)Google Scholar
  7. 7.
    Karlsson, L., Regnell, B., Karlsson, J., Olsson, S.: Post-Release Analysis of Requirements Selection Quality - An Industrial Case Study. In: Proc. of the 9th Int. Workshop on Requirements Engineering - Foundation for Software Quality (REFSQ 2003), Velden, Austria, pp. 47–56 (2003)Google Scholar
  8. 8.
    Karlsson, L., Regnell, B., Thelin, T.: A Case Study in Retrospective Analysis of Release Planning in an Agile Project. In: Workshop on the Interplay of Requirements Engineering and Project Management in Software Projects (REProMan 2005), Paris, France (2005)Google Scholar
  9. 9.
    Kerth, N.L.: Project Retrospectives - A handbook for team reviews. Dorset House Publishing, New York (2001)Google Scholar
  10. 10.
    Mens, T., Demeyer, S.: Evolution Metrics. In: International Workshop on Principles of Software Evolution (IWPSE 2001), Vienna, Austria (2001)Google Scholar
  11. 11.
    Regnell, B., Höst, M., Natt och Dag, J., Beremark, P., Hjelm, T.: An Industrial Case Study on Distributed Prioritisation in Market-driven Requirements Engineering for Packaged Software. Requirements Engineering 6, 51–62 (2001)MATHCrossRefGoogle Scholar
  12. 12.
    Saaty, T.L.: The Analytic Hierarchy Process. McGraw-Hill, New York (1980)MATHGoogle Scholar
  13. 13. (visited, March 2006)
  14. 14. (visited, March 2006)
  15. 15. (visited, March 2006)

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Lena Karlsson
    • 1
  • Björn Regnell
    • 1
  1. 1.Department of Communication SystemsLund UniversityLundSweden

Personalised recommendations