How Agile Is Hybrid Agile? An Analysis of the HELENA Data
Context: Many researchers advocate “tailoring” agile methods to suit a project’s or company’s specific environment and needs. This includes combining agile methods with more traditional “plan driven” practices.
Objective: This study aims to assess to what extent projects actually combine agile and traditional practices.
Method: Data from the HELENA survey of nearly 700 projects were examined to assess how many projects combine agile methods and traditional methods, and also to what extent they used different software development practices.
Results: The data show that, overall, two-thirds of the projects in the survey combine agile and traditional methods to some extent. However, projects that combine agile and traditional methods are significantly less likely to use agile practices than projects that solely use agile methods.
Conclusions: We hypothesize that the mindset of an organization, rather than technical necessity, determines whether a project will adopt a hybrid vs. purely agile approach.
KeywordsAgile development methods Empirical Software engineering Hybrid agile development
This work was supported, in part, by Science Foundation Ireland grants 10/CE/I1855 and 13/RC/2094 to Lero - the Irish Software Research Centre (www.lero.ie).
- 1.Aitken, A., Ilango, V.: A comparative analysis of traditional software engineering and agile software development. In: 2013 46th Hawaii International Conference on System Sciences, pp. 4751–4760, January 2013Google Scholar
- 2.Akbar, R., Safdar, S.: A short review of global software development (gsd) and latest software development trends. In: 2015 International Conference on Computer, Communications, and Control Technology (I4CT), pp. 314–317. IEEE (2015)Google Scholar
- 3.Beck, K., Gamma, E.: Extreme Programming Explained: Embrace Change. Addison Wesley, Boston (2000)Google Scholar
- 5.Ciolkowski, M., Laitenberger, O., Vegas, S., Biffl, S.: Practical experiences in the design and conduct of surveys in empirical software engineering. In: Conradi, R., Wang, A.I. (eds.) Empirical Methods and Studies in Software Engineering. LNCS, vol. 2765, pp. 104–128. Springer, Heidelberg (2003). https://doi.org/10.1007/978-3-540-45143-3_7CrossRefGoogle Scholar
- 10.Fowler, M., Highsmith, J.: The agile manifesto. Softw. Dev. 9(8), 28–35 (2001)Google Scholar
- 11.Klünder, J., et al.: HELENA Study: reasons for combining agile and traditional software development approaches in German companies. In: Felderer, M., Méndez Fernández, D., Turhan, B., Kalinowski, M., Sarro, F., Winkler, D. (eds.) PROFES 2017. LNCS, vol. 10611, pp. 428–434. Springer, Cham (2017). https://doi.org/10.1007/978-3-319-69926-4_32CrossRefGoogle Scholar
- 13.Kuhrmann, M., et al.: Hybrid software and system development in practice: waterfall, scrum, and beyond. In: Proceedings of the 2017 International Conference on Software and System Process, pp. 30–39. ACM (2017)Google Scholar
- 14.Kuhrmann, M., Tell, P., Klünder, J., Hebig, R., Licorish, S., MacDonell, S.: Helena stage 2 results. Technical report, HELENA consortium (11 2018)Google Scholar
- 17.Marinho, M., Noll, J., Richardson, I., Beecham, S.: Plan-driven approaches are alive and kicking in agile global software development. In: International Symposium on Empirical Software Engineering and Measurement (ESEM). ACM/IEEE (2019)Google Scholar
- 22.Tell, P., et al.: What are hybrid development methods made of?: an evidence-based characterization. In: Proceedings of the International Conference on Software and System Processes, pp. 105–114. IEEE Press (2019)Google Scholar
- 23.VersionOne Inc: 13th Annual State of Agile Development Survey (2018). https://www.stateofagile.com/#ufh-i-521251909-13th-annual-state-of-agile-report/473508. Accessed 5 August 2019. web page