Advertisement

Conceptualizing the Transition from Agile to DevOps: A Maturity Model for a Smarter IS Function

  • Aymeric Hemon
  • Barbara Lyonnet
  • Frantz Rowe
  • Brian Fitzgerald
Conference paper
Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT, volume 533)

Abstract

Agile development approaches have become the norm for almost all software development now. While agile approaches can deliver more frequent releases of working software, it quickly became apparent in many organisations that they were not able to leverage these frequent releases due to the disconnect between the development and operations functions, with the latter typically responsible for releasing software to customers. This resulted in the move towards closer integration of these functions through the DevOps movement. As the trend towards digitalisation continues, companies are increasingly implementing DevOps. We propose a maturity model for this agile to DevOps transition with three levels: agile, continuous integration, continuous delivery. Based on an in-depth case study in an organisation which has several years’ experience of DevOps, we identify a fundamental disruption in the soft skills and competences that software teams are expected to possess, and in the patterns of collaboration among teams. The latter is especially salient for release managers, project managers, production engineers and even architects. Arguably, smartness may be characterized as being flexible, teaming up with people who have a different profile, belonging to a different function, and delivering more quickly what had been designed. In light of this, we argue that DevOps leads to greater smartness for the Information Systems (IS) function.

Keywords

DevOps Agile Roles Skills Collaboration 

References

  1. 1.
    Brunnert, A., et al.: Performance-oriented DevOps: a research agenda. ArXiv Prepr. ArXiv150804752 (2015)Google Scholar
  2. 2.
    Debois, P.: DevOpsDaysGhent. DevOpsDays, Ghent, Belgium (2009)Google Scholar
  3. 3.
    Debois, P.: DevOps: a software revolution in the making. J. Inf. Technol. Manag. 24, 3–39 (2011)Google Scholar
  4. 4.
    Conboy, K., Coyle, S.: People over process: the implications of agile for IS skills and Human Resource Management. IEEE Softw. 28, 48–57 (2009)CrossRefGoogle Scholar
  5. 5.
    Gallivan, M.J., Truex III, D.P., Kvasny, L.: Changing patterns in IT skill sets 1988-2003: a content analysis of classified advertising. ACM SIGMIS Database DATABASE Adv. Inf. Syst. 35, 64–87 (2004)Google Scholar
  6. 6.
    Wong, S., von Hellens, L., Orr, J.: Non-technical skills and personal attributes: the Soft Skills Matter Most. In: Proceedings of the 6th Australiasian Women in Computing Workshop, Brisbane, Australia, pp. 27–33 (2006)Google Scholar
  7. 7.
    Boyatzis, R.E., Kolb, D.A.: From learning styles to learning skills: the executive skills profile. J. Manag. Psychol. 10, 3–17 (1995)CrossRefGoogle Scholar
  8. 8.
    Robles, M.M.: Executive perceptions of the top 10 soft skills needed in today’s workplace. Bus. Commun. Q. 75, 453–465 (2012)CrossRefGoogle Scholar
  9. 9.
    Todd, P.A., McKeen, J.D., Gallupe, R.B.: The evolution of IS job skills: a content analysis of IS job advertisements from 1970 to 1990. MIS Q. 19, 1–27 (1995)CrossRefGoogle Scholar
  10. 10.
    Trauth, E.M., Farwell, D.W., Lee, D.: The IS expectation gap: industry expectations versus academic preparation. Mis Q. 17, 293–307 (1993)CrossRefGoogle Scholar
  11. 11.
    Vivian, R., Tarmazdi, H., Falkner, K., Falkner, N., Szabo, C.: The development of a dashboard tool for visualising online teamwork discussions. In: IEEE/ACM 37th IEEE International Conference on Software Engineering, pp. 380–388. IEEE (2015)Google Scholar
  12. 12.
    Wiedemann, A.M., Schulz, T.: Key Capabilities of DevOps teams and their influence on software process innovation: a resource-based view. In: Proceedings of 23rd ACIS Americas Conference on Information Systems, pp. 1–10, Boston (2017)Google Scholar
  13. 13.
    Wiedemann, A.: A new form of collaboration in IT teams-exploring the DevOps phenomenon. In: Proceedings of the 21st PACIS Pacific Asia Conference on Information Systems, pp. 1–12, Langkawi (2017)Google Scholar
  14. 14.
    Conboy, K., Fitzgerald, B.: Toward a conceptual framework of agile methods: a study of agility in different disciplines. In: Proceedings of the 2004 ACM Workshop on Interdisciplinary Software Engineering Research, pp. 37–44. ACM, Newport Beach (2004)Google Scholar
  15. 15.
    Highsmith, J., Cockburn, A.: Agile software development: the business of innovation. Computer 34, 120–127 (2001)CrossRefGoogle Scholar
  16. 16.
    Conboy, K., Coyle, S., Wang, X., Pikkarainen, M.: People over process: key people challenges in agile development. IEEE Softw. 28, 48–57 (2011)CrossRefGoogle Scholar
  17. 17.
    Coram, M., Bohner, S.: The impact of agile methods on software project management. In: ECBS 2005 Proceedings, pp. 363–370. IEEE Computer Society, Greenbelt (2005)Google Scholar
  18. 18.
    Nerur, S., Mahapatra, R., Mangalaraj, G.: Challenges of migrating to agile methodologies. Commun. ACM 48, 72–78 (2005)CrossRefGoogle Scholar
  19. 19.
    Lwakatare, L.E., Kuvaja, P., Oivo, M.: Dimensions of DevOps. In: Lassenius, C., Dingsøyr, T., Paasivaara, M. (eds.) XP 2015. LNBIP, vol. 212, pp. 212–217. Springer, Cham (2015).  https://doi.org/10.1007/978-3-319-18612-2_19CrossRefGoogle Scholar
  20. 20.
    Wettinger, J., Breitenbücher, U., Leymann, F.: Standards-based DevOps automation and integration using TOSCA. In: Proceedings of the 2014 IEEE/ACM, pp. 59–68. IEEE Computer Society, London (2014)Google Scholar
  21. 21.
    Humble, J., Molesky, J.: Why enterprises must adopt DevOps to enable continuous delivery. Cut. IT J. 24, 6 (2011)Google Scholar
  22. 22.
    Kim, G., Debois, P., Willis, J., Humble, J.: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. IT Revolution, Portland (2016)Google Scholar
  23. 23.
    Ghobadi, S., Mathiassen, L.: Perceived barriers to effective knowledge sharing in agile software teams. Inf. Syst. J. 26, 95–125 (2016)CrossRefGoogle Scholar
  24. 24.
    Coyle, S., Conboy, K., Acton, T.: An exploration of the relationship between contribution behaviours and the decision making process in agile teams. In: Proceedings of the 36th ICIS International Conference on Information Systems, pp. 1–15, Fort Worth, TX, USA (2015)Google Scholar
  25. 25.
    Schwaber, K., Sutherland, J.: The scrum guide. Scrum Alliance 21 (2011)Google Scholar
  26. 26.
    Oomen, S., De Waal, B., Albertin, A., Ravesteyn, P.: How can Scrum be successful? Competences of the Scrum Product Owner. In: Proceedings of the 25th ECIS European Conference on Information Systems, pp. 131–142, Guimarães, Portugal (2017)Google Scholar
  27. 27.
    Yin, R.K.: Validity and generalization in future case study evaluations. Evaluation 19, 321–332 (2013)CrossRefGoogle Scholar
  28. 28.
    Rolland, K.H., Fitzgerald, B., Dingsøyr, T., Stol, K.-J.: Problematizing agile in the large: alternative assumptions for large-scale agile development. In: Proceedings of the 37th ICIS International Conference on Information Systems, pp. 1–21, Dublin, Ireland (2016)Google Scholar
  29. 29.
    Ståhl, D., Bosch, J.: Modeling continuous integration practice differences in industry software development. J. Syst. Softw. 87, 48–59 (2014)CrossRefGoogle Scholar
  30. 30.
    Chen, L.: Continuous delivery: overcoming adoption challenges. J. Syst. Softw. 128, 72–86 (2017)CrossRefGoogle Scholar
  31. 31.
    Tan, C.-H., Teo, H.-H.: Training future software developers to acquire agile development skills. Commun. ACM 50, 97–98 (2007)CrossRefGoogle Scholar
  32. 32.
    Bang, S.K., Chung, S., Choh, Y., Dupuis, M.: A grounded theory analysis of modern web applications: knowledge, skills, and abilities for DevOps. In: Proceedings of the RIIT, 2nd Annual Conference on Research in Information Technology, pp. 61–62. ACM, Orlando (2013)Google Scholar
  33. 33.
    Betz, C., Olagunju, A.O., Paulson, P.: The impacts of digital transformation, agile, and DevOps on future IT curricula. In: Proceedings of the 17th Annual Conference on Information Technology Education, p. 106. ACM, Boston (2016)Google Scholar
  34. 34.
    Kerzazi, N., Adams, B.: Who needs release and DevOps engineers, and why? In: Proceedings of the International Workshop on Continuous Software Evolution and Delivery, pp. 77–83. ACM, Austin (2016)Google Scholar
  35. 35.
    Hussain, W., Clear, T., MacDonell, S.: Emerging trends for global DevOps: a New Zealand perspective. In: Proceedings of the 12th ICGSE International Conference on Global Software Engineering, pp. 21–30. IEEE Press, Buenos Aires (2017)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2019

Authors and Affiliations

  • Aymeric Hemon
    • 1
  • Barbara Lyonnet
    • 1
  • Frantz Rowe
    • 1
    • 3
  • Brian Fitzgerald
    • 2
  1. 1.University of Nantes, LEMNANantesFrance
  2. 2.University of Limerick, LEROLimerickIreland
  3. 3.SKEMA Business School, KTOSophia AntipolisFrance

Personalised recommendations