Abstract
Agile software development methods are widely used by software organisations, focusing on short developmental life cycles and customer satisfaction through the iterative and incremental development of software products. Despite their popularity, these methods present risks that may be underappreciated. This paper examines certain risks attributed to agile software development, with a focus on the lack of documentation, scope creep, technical debt and job satisfaction. Through the application of a multivocal literature review, we find that agile software development can greatly benefit projects. However, when agile methods are implemented inappropriately or sub-optimally, projects risk over-spending, delayed or defective software, employee turnover, and overall decreased productivity. Understanding the risks associated with agile software development can help practitioners to achieve higher efficiency and success in their software development projects.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
Zhi, J., Garousi-Yusifoğlu, V., Sun, B., Garousi, G., Shahnewaz, S., Ruhe, G.: Cost, benefits and quality of software development documentation: a systematic mapping. J. Syst. Softw. 99, 175–198 (2015)
Hadar, I., Sherman, S., Hadar, E., Harrison, J.J.: Less is more: architecture documentation for agile development. In: 2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), pp. 121–124. IEEE (2013)
Haugset, B., Stalhane, T.: Automated acceptance testing as an agile requirements engineering practice. In: 2012 45th Hawaii International Conference on System Sciences, pp. 5289–5298. IEEE (2012)
Aghajani, E., et al.: Software documentation issues unveiled. In: 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE), pp. 1199–1210. IEEE (2019)
Behutiye, W., Rodríguez, P., Oivo, M., Aaramaa, S., Partanen, J., Abhervé, A.: Towards optimal quality requirement documentation in agile software development: a multiple case study. J. Syst. Softw. 183, 111112 (2022)
Saito, S., Iimura, Y., Massey, A.K., Antón, A.I.: How much undocumented knowledge is there in agile software development?: case study on industrial project using issue tracking system and version control system. In: 2017 IEEE 25th International Requirements Engineering Conference (RE), pp. 194–203. IEEE (2017)
Sommerville, I.: Software documentation. Softw. Eng. 2, 143–154 (2001)
Prause, C.R., Nonnen, J., Vinkovits, M.: A field experiment on gamification of code quality in agile development. In: PPIG, p. 17 (2012)
Madhuri, K.L., Rao, J.J., Suma, V.: Effect of scope creep in software projects — its bearing on critical success factors. Int. J. Comput. Appl. 106(2), 9–13 (2014)
Aizaz, F., Khan, S.U.R., Khan, J.A., Akhunzada, A.: An empirical investigation of factors causing scope creep in agile global software development context: a conceptual model for project managers. IEEE Access 9, 109166–109195 (2021)
Shastri, Y., Hoda, R., Amor, R.: The role of the project manager in agile software development projects. J. Syst. Softw. 173, 110871 (2021)
Turk, W.: Scope creep horror. Defense AT&L 39(2), 53–55 (2010)
Tuohey, W.G.: Benefits and effective application of software engineering standards. Softw. Qual. J. 10(1), 47–68 (2002)
Fowler, M., Highsmith, J.: The agile manifesto. Softw. Dev. 9(8), 28–35 (2001)
"ISO Brief 2019”: Iso.Org. https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100007.pdf (2019). Accessed: 6 Mar 2022
Theunissen, W.M., Kourie, D.G., Watson, B.W.: Standards and agile software development. In: Proceedings of SAICSIT, vol. 30, no. 3, pp. 178–188 (2003)
Reifer, D.J.: How to get the most out of extreme programming/agile methods. In: Wells, D., Williams, L. (eds.) XP/Agile Universe 2002. LNCS, vol. 2418, pp. 185–196. Springer, Heidelberg (2002). https://doi.org/10.1007/3-540-45672-4_18
Komal, B., et al.: The impact of scope creep on project success: an empirical investigation. IEEE Access 8, 125755–125775 (2020)
Cunningham, W.: The WyCash portfolio management system. ACM SIGPLAN OOPS Messenger 4(2), 29–30 (1992)
Kruchten, P., Nord, R.L., Ozkaya, I.: Technical debt: from metaphor to theory and practice. IEEE Softw. 29(6), 18–21 (2012)
Tom, E., Aurum, A., Vidgen, R.: An exploration of technical debt. J. Syst. Softw. 86(6), 1498–1516 (2013)
Holvitie, J., Leppänen, V., Hyrynsalmi, S.: Technical debt and the effect of agile software development practices on it-an industry practitioner survey. In: 2014 Sixth International Workshop on Managing Technical Debt, pp. 35–42. IEEE (2014)
Martini, A., Bosch, J., Chaudron, M.: August. Architecture technical debt: understanding causes and a qualitative model. In: 2014 40th EUROMICRO Conference on Software Engineering and Advanced Applications, pp. 85–92. IEEE (2014)
Martini, A., Bosch, J.: The danger of architectural technical debt: contagious debt and vicious circles. In: 2015 12th Working IEEE/IFIP Conference on Software Architecture, pp. 1–10. IEEE (2015)
Li, Z., Avgeriou, P., Liang, P.: A systematic mapping study on technical debt and its management. J. Syst. Softw. 101, 193–220 (2015)
Martini, A., Stray, V., Moe, N.B.: Technical-, social- and process debt in large-scale agile: an exploratory case-study. In: Hoda, R. (ed.) XP 2019. LNBIP, vol. 364, pp. 112–119. Springer, Cham (2019). https://doi.org/10.1007/978-3-030-30126-2_14
Codabux, Z., Williams, B.: Managing technical debt: an industrial case study. In: 2013 4th International Workshop on Managing Technical Debt (MTD), pp. 8–15. IEEE (2013)
Cho, J.: Issues and challenges of agile software development with SCRUM. Issues Inform. Syst. 9(2), 188–195 (2008)
Pedrycz, W., Russo, B., Succi, G.: A model of job satisfaction for collaborative development processes. J. Syst. Softw. 84(5), 739–752 (2011)
Conboy, K., Coyle, S., Wang, X.: People over process: key challenges in agile development (99), 48–57 (2010)
Tripp, J.F., Riemenschneider, C.K.: Toward an understanding of job satisfaction on agile teams: agile development as work redesign. In: 2014 47th Hawaii International Conference on System Sciences, pp. 3993–4002 (2014)
Melnik, G., Maurer, F.: Comparative analysis of job satisfaction in agile and non-agile software development teams. In: International Conference on Extreme Programming and Agile Processes in Software Engineering, pp. 32–42 (2006)
Sillitti, A., Wang, X., Martin, A., Whitworth, E.: Agile processes in software engineering and extreme programming. In 11th International Conference, XP, pp. 1–4 (2010)
Amin, A., Basri, S., Hassan, M.F., Rehman, M.: Software engineering occupational stress and knowledge sharing in the context of Global Software Development. In: 2011 National Postgraduate Conference, pp. 1–4 (2011)
Ersoy, I.B., Mahdy, A.M.: Agile knowledge sharing. Int. J. Softw. Eng. (IJSE) 6(1), 1–15 (2015)
Madhura, S., Subramanya, P., Balaram, P.: Job satisfaction, job stress and psychosomatic health problems in software professionals in India. Indian J. Occup. Environ. Med 18(3), 153 (2014)
Clarke, P., O’Connor, R.V., Leavy, B., Yilmaz, M.: Exploring the relationship between software process adaptive capability and organisational performance. IEEE Trans. Softw. Eng. 41(12), 1169–1183 (2015). https://doi.org/10.1109/TSE.2015.2467388
Clarke, P., O’Connor, R.V.: The situational factors that affect the software development process: towards a comprehensive reference framework. Inf. Softw. Technol. 54(5), 433–447 (2012)
International Software Benchmarking Standards Group. https://www.isbsg.org/. Accessed: 6 Mar 2022
Clarke, P., et al.: An investigation of software development process terminology. In: Clarke, P.M., O’Connor, R.V., Rout, T., Dorling, A. (eds.) SPICE 2016. CCIS, vol. 609, pp. 351–361. Springer, Cham (2016). https://doi.org/10.1007/978-3-319-38980-6_25
Leffingwell, D., et al.: Scaled agile framework (SAFe). https://www.scaledagileframework.com/. Accessed 6 Mar 2022
SonarCube: https://www.sonarqube.org/. Accessed 6 Mar 2022
Acknowledgements
This research is supported in part by SFI, Science Foundation Ireland (https://www.sfi.ie/) grant No. SFI 13/RC/2094 P2 to Lero - the Science Foundation Ireland Research Centre for Software.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2022 Springer Nature Switzerland AG
About this paper
Cite this paper
Nolan, A., Strickland, B., Quinn, A., Gallagher, K., Yilmaz, M., Clarke, P.M. (2022). Exploring Aspects of Agile Software Development Risk – Results from a MLR. In: Yilmaz, M., Clarke, P., Messnarz, R., Wöran, B. (eds) Systems, Software and Services Process Improvement. EuroSPI 2022. Communications in Computer and Information Science, vol 1646. Springer, Cham. https://doi.org/10.1007/978-3-031-15559-8_35
Download citation
DOI: https://doi.org/10.1007/978-3-031-15559-8_35
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-031-15558-1
Online ISBN: 978-3-031-15559-8
eBook Packages: Computer ScienceComputer Science (R0)