Characterizing DevOps Culture: A Systematic Literature Review

  • Mary Sánchez-Gordón
  • Ricardo Colomo-PalaciosEmail author
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 918)


Time and quality pressures are affecting software process in all its stages. One of the proposed solutions to these pressures is DevOps. DevOps is aimed to increase the frequency, quality and speed of deploying software from development into production by means of new organizational structures and processes with a high degree of automation. Several authors underlined the fact, that beyond the tool chain, DevOps is a culture shift. However, to date the characterization of DevOps culture remains unclear. In this paper, authors tackle this problem by means of a Systematic Literature Review. Results provide a deeper understanding of the phenomena from human factor´s perspective.


DevOps Culture Empathy Systematic Literature Review Human factors 


  1. 1.
    Rodríguez, P., et al.: Continuous deployment of software intensive products and services: a systematic mapping study. J. Syst. Softw. 123, 263–291 (2017)CrossRefGoogle Scholar
  2. 2.
    Ameller, D., Farré, C., Franch, X., Valerio, D., Cassarino, A.: Towards continuous software release planning. In: 2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER), pp. 402–406 (2017)Google Scholar
  3. 3.
    Stahl, D., Martensson, T., Bosch, J.: Continuous practices and DevOps: beyond the buzz, what does it all mean?. In: 2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA), pp. 440–448. IEEE (2017)Google Scholar
  4. 4.
    Bosch, J.: Continuous software engineering: an introduction. In: Bosch, J. (ed.) Continuous Software Engineering, pp. 3–13. Springer, Cham (2014). Scholar
  5. 5.
    Fitzgerald, B., Stol, K.-J.: Continuous software engineering: a roadmap and agenda. J. Syst. Softw. 123, 176–189 (2017)CrossRefGoogle Scholar
  6. 6.
    Lwakatare, L.E., Kuvaja, P., Oivo, M.: Relationship of DevOps to agile, lean and continuous deployment. In: Abrahamsson, P., Jedlitschka, A., Nguyen Duc, A., Felderer, M., Amasaki, S., Mikkonen, T. (eds.) PROFES 2016. LNCS, vol. 10027, pp. 399–415. Springer, Cham (2016). Scholar
  7. 7.
    Jabbari, R., bin Ali, N., Petersen, K., Tanveer, B.: What is DevOps?: a systematic mapping study on definitions and practices. In: Proceedings of the Scientific Workshop Proceedings of XP2016, p. 12. ACM (2016)Google Scholar
  8. 8.
    Ebert, C., Gallardo, G., Hernantes, J., Serrano, N.: DevOps. IEEE Softw. 33, 94–100 (2016)CrossRefGoogle Scholar
  9. 9.
    Balalaie, A., Heydarnoori, A., Jamshidi, P.: Microservices architecture enables DevOps: migration to a cloud-native architecture. IEEE Softw. 33, 42–52 (2016)CrossRefGoogle Scholar
  10. 10.
    Humble, J., Molesky, J.: Why enterprises must adopt DevOps to enable continuous delivery. Cut. IT J. 24, 6–12 (2011)Google Scholar
  11. 11.
    Debois, P.: DevOps Areas - Codifying DevOps practices.
  12. 12.
    Mueller, E.: What Is DevOps? (2010).
  13. 13.
    Capretz, L.F.: Bringing the human factor to software engineering. IEEE Softw. 31, 104 (2014)CrossRefGoogle Scholar
  14. 14.
    Colomo-Palacios, R., Gomez-Berbis, J.M., Garcia-Crespo, A., Puebla-Sanchez, I.: Social Global Repository: using semantics and social web in software projects. Int. J. Knowl. Learn. 4, 452–464 (2008)CrossRefGoogle Scholar
  15. 15.
    Colomo-Palacios, R., Casado-Lumbreras, C., Soto-Acosta, P., Misra, S., García-Peñalvo, F.J.: Analyzing human resource management practices within the GSD context. J. Glob. Inf. Technol. Manag. 15, 30–54 (2012)Google Scholar
  16. 16.
    Kromhout, B.: Containers will not fix your broken culture (and other hard truths). Queue 15, 50:46–50:56 (2017)Google Scholar
  17. 17.
    Capretz, L.F., Ahmed, F., da Silva, F.Q.B.: Soft sides of software. Inf. Softw. Technol. 92, 92–94 (2017)CrossRefGoogle Scholar
  18. 18.
    Colomo-Palacios, R., Fernandes, E., Soto-Acosta, P., Larrucea, X.: A case analysis of enabling continuous software deployment through knowledge management. Int. J. Inf. Manag. 40, 186–189 (2018)CrossRefGoogle Scholar
  19. 19.
    Kitchenham, B., Charters, S.: Guidelines for performing Systematic Literature Reviews in Software Engineering. School of Computer Science and Mathematics, Keele University, Keele (2007)Google Scholar
  20. 20.
    Sailunaz, K., Dhaliwal, M., Rokne, J., Alhajj, R.: Emotion detection from text and speech: a survey. Soc. Netw. Anal. Min. 8(1), 28 (2018)CrossRefGoogle Scholar
  21. 21.
    Graziotin, D., Wang, X., Abrahamsson, P.: Understanding the affect of developers: theoretical background and guidelines for psychoempirical software engineering. In: Presented at the 7th International Workshop on Social Software Engineering, pp. 25–32. ACM (2015)Google Scholar
  22. 22.
    Murgia, A., Tourani, P., Adams, B., Ortu, M.: Do developers feel emotions? An exploratory analysis of emotions in software artifacts. In: Proceedings of the 11th Working Conference on Mining Software Repositories, pp. 262–271. ACM, New York (2014)Google Scholar
  23. 23.
    Pavlovich, K., Krahnke, K.: Empathy, connectedness and organisation. J. Bus. Ethics 105, 131–137 (2012)CrossRefGoogle Scholar
  24. 24.
    Akgün, A.E., Keskin, H., Cebecioglu, A.Y., Dogan, D.: Antecedents and consequences of collective empathy in software development project teams. Inf. Manag. 52, 247–259 (2015)CrossRefGoogle Scholar
  25. 25.
    Sánchez-Gordón, M.-L.: Getting the best out of people in small software companies: ISO/IEC 29110 and ISO 10018 standards. Int. J. Inf. Technol. Syst. Approach 10, 45–60 (2017)CrossRefGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  1. 1.Østfold University CollegeHaldenNorway

Personalised recommendations