%0 Conference Paper %1 AlAlam:2014:MBA:2652524.2652549 %A Al Alam, S. M. Didar %A Shahnewaz, S. M. %A Pfahl, Dietmar %A Ruhe, Guenther %B Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement %C New York, NY, USA %D 2014 %I ACM %K product.planning release.planning %P 60:1--60:4 %R 10.1145/2652524.2652549 %T Monitoring Bottlenecks in Achieving Release Readiness: A Retrospective Case Study Across Ten OSS Projects %U http://doi.acm.org/10.1145/2652524.2652549 %X Context: Not releasing software on time can cause substantial loss in revenue. Continuous awareness of the product release status is required. Release readiness is a time-dependent attribute of the status of the product release, which aggregates the degree of satisfaction of a portfolio of release process and product measures. Goal: At different stages of a release cycle, the goal is to understand frequencies and pattern of occurrence of factors affecting project success by restricting the status of release readiness (called bottlenecks). Method: As a form of explorative case study research, we analyzed ten open source software (OSS) projects taken from the GitHub repository. As a retrospective study covering a period of 28 weeks, we monitored eight release readiness attributes and identified their impact on release readiness over time across the ten projects. Results: Feature completion rate, Bug fixing rate, and Features implemented were observed as the most frequent bottlenecks. The most frequent transition between bottlenecks is from Pull-request completion rate to Bug fixing rate. With the exception of Pull-request completion rate, no significant differences were found in occurrence of bottleneck factors between early and late stage of the release cycle. Conclusions: We received an initial understanding of the most frequent bottleneck factors for release readiness and their likelihood of subsequent occurrence. This is intended to guide the effort spent on improving release engineering. %@ 978-1-4503-2774-9

@inproceedings{AlAlam:2014:MBA:2652524.2652549, abstract = {Context: Not releasing software on time can cause substantial loss in revenue. Continuous awareness of the product release status is required. Release readiness is a time-dependent attribute of the status of the product release, which aggregates the degree of satisfaction of a portfolio of release process and product measures. Goal: At different stages of a release cycle, the goal is to understand frequencies and pattern of occurrence of factors affecting project success by restricting the status of release readiness (called bottlenecks). Method: As a form of explorative case study research, we analyzed ten open source software (OSS) projects taken from the GitHub repository. As a retrospective study covering a period of 28 weeks, we monitored eight release readiness attributes and identified their impact on release readiness over time across the ten projects. Results: Feature completion rate, Bug fixing rate, and Features implemented were observed as the most frequent bottlenecks. The most frequent transition between bottlenecks is from Pull-request completion rate to Bug fixing rate. With the exception of Pull-request completion rate, no significant differences were found in occurrence of bottleneck factors between early and late stage of the release cycle. Conclusions: We received an initial understanding of the most frequent bottleneck factors for release readiness and their likelihood of subsequent occurrence. This is intended to guide the effort spent on improving release engineering.}, acmid = {2652549}, added-at = {2015-04-20T13:47:59.000+0200}, address = {New York, NY, USA}, articleno = {60}, author = {Al Alam, S. M. Didar and Shahnewaz, S. M. and Pfahl, Dietmar and Ruhe, Guenther}, biburl = {https://www.bibsonomy.org/bibtex/203dff9f68fce164182987f3bfb9a0678/ispma}, booktitle = {Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement}, doi = {10.1145/2652524.2652549}, interhash = {e68f54049c142a9280a969a6473c2fd6}, intrahash = {03dff9f68fce164182987f3bfb9a0678}, isbn = {978-1-4503-2774-9}, keywords = {product.planning release.planning}, location = {Torino, Italy}, numpages = {4}, pages = {60:1--60:4}, publisher = {ACM}, series = {ESEM '14}, timestamp = {2015-04-20T14:18:18.000+0200}, title = {Monitoring Bottlenecks in Achieving Release Readiness: A Retrospective Case Study Across Ten OSS Projects}, url = {http://doi.acm.org/10.1145/2652524.2652549}, year = 2014 }