Monitoring and Controlling Release Readiness by Learning Across Projects

  • S. M. Didar Al AlamEmail author
  • Dietmar Pfahl
  • Günther Ruhe


Releasing software on time, with desired quality while staying within budget is crucial for success. Therefore, product managers should proactively know which release readiness attributes are not performing sufficiently well (i.e., bottleneck factors) throughout the development cycle and consequently may limit readiness of the software release. We present the Cross-project Analysis for Selection of Release Readiness attributes (CASRR) method to help project managers in (i) systematically studying and analyzing release readiness attributes across multiple projects, (ii) selection of release readiness attributes for monitoring which have previously been shown to become bottlenecks in similar projects in the past, and (iii) learning how bottleneck occurrences are influenced by project characteristics. We applied CASRR to two Open Source Software projects, and analyzed six release readiness attributes in 34 similar projects over a period of two years. Continuous integration rate, feature completion rate, and bug fixing rate are observed as the most frequent bottleneck factors. Bottleneck occurrences of the monitored release readiness attributes are significantly influenced by the maturity of a release. Furthermore, the continuous integration rate is found to be significantly influenced by the team size.


Development Cycle Similar Project Software Release Project Characteristic Release Readiness 
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.



This work was partially supported by the Natural Sciences and Engineering Research Council of Canada, NSERC Discovery Grant 250343-12, Alberta Innovates Technology Futures and by the institutional research grant IUT20-55 of the Estonian Research Council.


  1. 1.
    Ashrafi, N.: The impact of software process improvement on quality: in theory and practice. Inf. Manag. 40(7), 677–690 (2003)CrossRefGoogle Scholar
  2. 2.
    Asthana, A., Olivieri, J.: Quantifying software reliability and readiness. In: Proceedings of the International Workshop Technical Committee on Communications Quality and Reliability, pp. 1–6. IEEE, Washington, DC (2009)Google Scholar
  3. 3.
    Basili, V.R., Caldiera, G., Rombach, H.D.: The goal question metric approach. In: Encyclopedia of Software Engineering. Wiley, New Jersey (1994)Google Scholar
  4. 4.
    Borland: Teaminspector 2008.
  5. 5.
    Brettschneider, R.: Is your software ready for release? IEEE Softw 6(4), 100–104 (1989)CrossRefGoogle Scholar
  6. 6.
    Didar Al Alam, S.M., Shahnewaz, S.M., Pfahl, D., Ruhe, G.: Monitoring bottlenecks in achieving release readiness: a retrospective case study across ten oss projects. In: Proceedings of the International Symposium on Empirical Software Engineering and Measurement, pp. 60:1–60:4. ACM, New York, NY, USA (2014)Google Scholar
  7. 7.
    Ebert, C.: The impacts of software product management. J. Syst. Softw. 80(6), 850–861 (2007)CrossRefGoogle Scholar
  8. 8.
    Ebert, C.: Software product management. IEEE Softw. 31(3), 21–24 (2014)CrossRefGoogle Scholar
  9. 9.
    Gokhale, S.: Optimal software release time incorporating fault correction. In: Proceedings of the Annual NASA Goddard Software Engineering Workshop, pp. 175–184. IEEE, Washington, DC (2003)Google Scholar
  10. 10.
    Johnson, M.A.: A case study of tracking software development using quality metrics. Softw. Qual. J. 4(1), 15–31 (1995)CrossRefGoogle Scholar
  11. 11.
    Larman, C.: Agile and Iterative Development: A Manager’s Guide. Addison-Wesley Professional (2003)Google Scholar
  12. 12.
    McConnell, S.: Gauging software readiness with defect tracking. IEEE Softw. 14(3), 135–136 (1997)CrossRefGoogle Scholar
  13. 13.
    Microsoft: Plan the release readiness review meeting. Accessed 2014
  14. 14.
    Pearse, T., Freeman, T., Oman, P.: Using metrics to manage the end-game of a software project. In: Proceedings of the International Symposium on Software Metrics, pp. 207–215. IEEE, Washington, DC (1999)Google Scholar
  15. 15.
    Port, D., Wilf, J.: The value of certifying software release readiness: an exploratory study of certification for a critical system at jpl. In: Proceedings of the International Symposium on Empirical Software Engineering and Measurement, pp. 373–382. IEEE, Washington, DC (2013)Google Scholar
  16. 16.
    Quah, T.S.: Estimating software readiness using predictive models. Inf. Sci. 179(4), 430–445 (2009)CrossRefGoogle Scholar
  17. 17.
    Rothman, J.: Measurements to reduce risk in product ship decisions. Accessed 2014
  18. 18.
    Satapathy, P.R.: Evaluation of software release readiness metric [0,1] across the software development life cycle. Tech. rep., Department of Computer Science & Engineering, University of California (2007)Google Scholar
  19. 19.
    Shahnewaz, S.M.: RELREA-an analytical approach supporting continuous release readiness evaluation. Master’s thesis, University of Calgary (2014)Google Scholar
  20. 20.
    Staron, M., Meding, W., Palm, K.: Release readiness indicator for mature agile and lean software development projects. In: Wohlin, C. (ed.) Agile Processes in Software Engineering and Extreme Programming. Lecture Notes in Business Information Processing, vol. 111, pp. 93–107. Springer, Heidelberg (2012)CrossRefGoogle Scholar
  21. 21.
    Ware, M., Wilkie, F., Shapcott, M.: The use of intra-release product measures in predicting release readiness. In: Proceedings of the International Conference on Software Testing, Verification, and Validation, pp. 230–237. IEEE, Washington, DC (2008)Google Scholar
  22. 22.
    Wild, R., Brune, P.: Determining software product release readiness by the change-error correlation function: on the importance of the change-error time lag. In: Proceeding of the Annual Hawaii International Conference on System Science, pp. 5360–5367. IEEE, Washington, DC (2012)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  • S. M. Didar Al Alam
    • 1
    Email author
  • Dietmar Pfahl
    • 2
  • Günther Ruhe
    • 1
  1. 1.Department of Computer ScienceUniversity of CalgaryCalgaryCanada
  2. 2.Institute of Computer ScienceUniversity of TartuTartuEstonia

Personalised recommendations