skip to main content
10.1145/1852786.1852804acmconferencesArticle/Chapter ViewAbstractPublication PagesesemConference Proceedingsconference-collections
research-article

Transition from a plan-driven process to Scrum: a longitudinal case study on software quality

Published: 16 September 2010 Publication History

Abstract

Although Scrum is an important topic in software engineering and information systems, few longitudinal industrial studies have investigated the effects of Scrum on software quality, in terms of defects and defect density, and the quality assurance process. In this paper we report on a longitudinal study in which we have followed a project over a three-year period. We compared software quality assurance processes and software defects of the project between a 17-month phase with a plan-driven process, followed by a 20-month phase with Scrum. The results of the study did not show a significant reduction of defect densities or changes of defect profiles after Scrum was used. However, the iterative nature of Scrum resulted in constant system and acceptance testing and related defect fixing, which made the development process more efficient in terms of fewer surprises and better control of software quality and release date. In addition, software quality and knowledge sharing got more focus when using Scrum. However, Scrum put more stress and time pressure on the developers, and made them reluctant to perform certain tasks for later maintenance, such as refactoring.

References

[1]
Abrahamsson, P. Extreme Programming: First Results from a Controlled Case Study. In Proceedings of the 29th Conference on EUROMICRO (Belek-Antalya, Turkey, Sept., 2003). IEEE Computer Society, 259. doi= http://doi.ieeecomputersociety.org/10.1109/ISESE.2004.1334895
[2]
Baskerville, R., Ramesh, B., Levine, L., Pries-Heje, J. and Slaughter, S. Is Internet-Speed Software Development Different? IEEE Software, 20, 6 (Nov. 2003), 70--77. doi=http://dx.doi.org/10.1109/MS.2003.1241369
[3]
Beck, K. and Andres, C. Extreme Programming Explained: Embrace Change (2nd Edition). Addison-Wesley, 2004.
[4]
Begel, A. and Nagappan, N. Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study. In Proceedings of the First International Symposium on Empirical Software Engineering and Measurement (Madrid, Spain, Sept., 2007). IEEE Computer Society, 255--264. doi=http://dx.doi.org/10.1109/ESEM.2007.85
[5]
Benefield, G. Rolling Out Agile in a Large Enterprise. In Proceedings of the 41st Annual Hawaii International Conference on System Sciences (Waikoloa, Big Island, Hawaii, Jan., 2008). IEEE Computer Society, 461. doi=http://dx.doi.org/10.1109/HICSS.2008.382
[6]
Boehm, B. and Turner, R. Using Risk to Balance Agile and Plan-Driven Methods. IEEE Computer, 36, 6 (June 2003), 57--66. doi=http://dx.doi.org/10.1109/MC.2003.1204376
[7]
Chillarege, R., Bhandari, I. S., Chaar, J. K., Halliday, M. J., Moebus, D. S., Ray, B. K. and Wong, M.-Y. Orthogonal Defect Classification-A Concept for In-Process Measurements. IEEE Transactions on Software Engineering, 18, 11 (Nov. 1992), 943--956. doi=http://dx.doi.org/10.1109/32.177364
[8]
Cockburn, A. and Highsmith, J. Agile Software Development: The People Factor. IEEE Computer, 34, 11 (Nov. 2001), 131--133. doi=http://dx.doi.org/10.1109/2.963450
[9]
Dingsøyr, T., Hanssen, G. K., Dybå, T., Anker, G. and Nygaard, J. O. Developing Software with Scrum in a Small Cross-Organizational Project. In Proceedings of the 13th European Conference on Software Process Improvement (Joensuu, Finland, Oct, 2006). Springer Verlag, 5--15. doi=10.1007/11908562_2
[10]
Dybå, T. and Dingsøyr, T. Empirical Studies of Agile Software Development: A Systematic Review. Information and Software Technology, 50, 9--10 (Aug. 2008), 833--859. doi=http://dx.doi.org/10.1016/j.infsof.2008.01.006
[11]
Emam, K. E. and Wieczorek, I. The Repeatability of Code Defect Classifications. In Proceedings of the 9th International Symposium on Software Reliability Engineering (Paderborn, Germany, Nov., 1998). IEEE Computer Society. doi=http://doi.ieeecomputersociety.org/10.1109/ISSRE.1998.730897
[12]
Erickson, J., Lyytinen, K. and Siau, K. Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research. Journal of Database Management, 16, 4 (Dec. 2005), 88--99.
[13]
Fitzgerald, B., Hartnett, G. and Conboy, K. Customising Agile Methods to Software Practices at Intel Shannon. European Journal of Information System, 15, 2 (Apr. 2006), 200--213. doi=http://dx.doi.org/10.1057/palgrave.ejis.3000605
[14]
Freimut, B., Denger, C. and Ketterer, M. An Industrial Case Study of Implementing and Validating Defect Classification for Process Improvement and Quality Management. In Proceedings of the 11th IEEE International Software Metrics Symposium (Como, Italy, Sept., 2005). IEEE Computer Society, 19. doi=http://dx.doi.org/10.1109/METRICS.2005.10
[15]
Grady, R. B. Practical Software Metrics For Project Management And Process Improvement. Prentice Hall, 1992.
[16]
Huo, M., Verner, J., Zhu, L. and Babar, M. A. Software Quality and Agile Methods. In Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01 (Hong Kong, China, Sept., 2004). IEEE Computer Society, 520--525. doi=http://doi.ieeecomputersociety.org/10.1109/CMPSAC.2004.1342889
[17]
Ilieva, S., Ivanov, P. and Stefanova, E. Analyses of an Agile Methodology Implementation. In Proceedings of the 30th EUROMICRO Conference (Rennes, France, Aug., 2004). IEEE Computer Society, 326--333. doi=http://dx.doi.org/10.1109/EUROMICRO.2004.14
[18]
Kajko-Mattsson, M., Lewis, G. A., Siracusa, D., Nelson, T., Chapin, N., Heydt, M., Nocks, J. and Snee, H. Long-term Life Cycle Impact of Agile Methodologies. In Proceedings of the 22nd IEEE International Conference on Software Maintenance (Philadelphia, Pennsylvania, USA, Sept., 2006). IEEE Computer Society, 422--425. doi=http://dx.doi.org/10.1109/ICSM.2006.34
[19]
Khramov, Y. The Cost of Code Quality. In Proceedings of the AGILE 2006 (Minneapolis, Minnesota, July, 2006). IEEE Computer Society, 119--125. doi=http://dx.doi.org/10.1109/AGILE.2006.52
[20]
Layman, L., Williams, L. and Cunningham, L. Exploring Extreme Programming in Context: An Industrial Case Study. In Proceedings of the Agile Development Conference (Salt Lake City, Utah, USA, June, 2004). IEEE Computer Society, 32--41. doi=http://doi.ieeecomputersociety.org/10.1109/ADEVC.2004.15
[21]
Mann, C. and Maurer, F. A Case Study on the Impact of Scrum on Overtime and Customer Satisfaction. In Proceedings of the Proc. of the Agile Development Conference (Denver, USA, July 2005, 2005). IEEE Computer Society, 70--79. doi=http://dx.doi.org/10.1109/ADC.2005.1
[22]
Moe, N. B., Dingsoyr, T. and Dybå, T. Overcoming Barriers to Self-Management in Software Teams. IEEE Software, 26, 6 (Nov. 2009), 20--26. doi=http://dx.doi.org/10.1109/MS.2009.182
[23]
Nerur, S. and Balijepally, V. Theoretical Reflections on Agile Development Methodologies. Communication of the ACM, 50, 3 (March 2007), 79--83. doi=http://doi.acm.org/10.1145/1226736.1226739
[24]
Nerur, S., Mahapatra, R. and Mangalaraj, G. Challenges of Migrating to Agile Methodologies. Communication of the ACM, 48, 5 (May 2005), 72--78. doi=http://doi.acm.org/10.1145/1060710.1060712
[25]
Richard, M., Kelly, R., James, G. and Brian, H. Scrum at a Fortune 500 Manufacturing Company. In Proceedings of the AGILE 2007 (Washington, DC, Aug., 2007). IEEE Computer Society, 175--180. doi=http://dx.doi.org/10.1109/AGILE.2007.53
[26]
Rising, L. and Janoff, N. S. The Scrum Software Development Process for Small Teams. IEEE Software, 17, 4 (July 2000), 26--32. doi=http://dx.doi.org/10.1109/52.854065
[27]
Rundle, P. J. and Dewar, R. G. Using Return on Investment to Compare Agile and Plan-driven Practices in Undergraduate Group Projects. In Proceedings of the 28th international conference on Software engineering (Shanghai, China, May, 2006). ACM, 649--654. doi=http://doi.acm.org/10.1145/1134285.1134383
[28]
Schwaber, K. and Beedle, M. Agile Software Development with SCRUM. Prentice Hall, 2001.
[29]
Sutherland, J., Jakobsen, C. R. and Johnson, K. Scrum and CMMI Level 5: The Magic Potion for Code Warriors. In Proceedings of the AGILE 2007 (Washington, DC, Aug., 2007). IEEE Computer Society, 272--278. doi=http://dx.doi.org/10.1109/AGILE.2007.52
[30]
Wellington, C. A., Briggs, T. and Girard, C. D. Comparison of Student Experiences with Plan-driven and Agile Methodologies. In Proceedings of the 35th Annual Conference on Frontiers in Education (Indianapolis, Indiana, USA, Oct., 2005), T3G-18.
[31]
Williams, L., Krebs, W., Layman, L., Antón 1, A. I. and Abrahamsson, P. Toward a Framework for Evaluating Extreme Programming. In Proceedings of the 8th Internation Conference on Empirical Assessment in Software Engineering (Edinburgh, Scotland, UK, May, 2004), 11--20.
[32]
Yin, R. K. Case Study Research: Design and Methods (4th Edition). Sage Publications, 2008.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ESEM '10: Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
September 2010
423 pages
ISBN:9781450300391
DOI:10.1145/1852786
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 16 September 2010

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. agile software development
  2. empirical software engineering
  3. software quality

Qualifiers

  • Research-article

Funding Sources

Conference

ESEM '10
Sponsor:

Acceptance Rates

ESEM '10 Paper Acceptance Rate 30 of 102 submissions, 29%;
Overall Acceptance Rate 130 of 594 submissions, 22%

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)41
  • Downloads (Last 6 weeks)2
Reflects downloads up to 26 Jan 2025

Other Metrics

Citations

Cited By

View all

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media