Skip to main content

DevOps Adoption Benefits and Challenges in Practice: A Case Study

  • Conference paper
  • First Online:
Product-Focused Software Process Improvement (PROFES 2016)

Abstract

DevOps is an approach in which traditional software engineering roles are merged and communication is enhanced to improve the production release frequency and maintain software quality. There seem to be benefits in adopting DevOps but practical industry experiences have seldom been reported. We conducted a qualitative multiple-case study and interviewed the representatives of three software development organizations in Finland. The responses indicate that with DevOps, practitioners can increase the frequency of releases and improve test automation practices. DevOps was seen to encourage collaboration between departments which boosts communication and employee welfare. Continuous releases enable a more experimental approach and rapid feedback collection. The challenges include communication structures that hinder cross-department collaboration and having to address the cultural shift. Dissimilar development and production environments were mentioned as some of the technical barriers. DevOps might not also be suitable for all industries. Ambiguity in the definition of DevOps makes adoption difficult since organizations might not know which practices they should implement for DevOps.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

References

  1. Digile N4S (2016). http://www.n4s.fi/en. Accessed Sep 2016

  2. Balalaie, A., Heydarnoori, A., Jamshidi, P.: Microservices architecture enables DevOps: migration to a cloud-native architecture. IEEE Softw. 33(3), 42–52 (2016)

    Article  Google Scholar 

  3. Bass, L., Weber, I., Zhu, L.: DevOps: A Software Architect’s Perspective. Addison-Wesley, Boston (2015)

    Google Scholar 

  4. Callanan, M., Spillane, A.: DevOps: making it easy to do the right thing. IEEE Softw. 33(3), 53–59 (2016)

    Article  Google Scholar 

  5. Cruzes, D., Dyba, T.: Recommended steps for thematic synthesis in software engineering. In: International Symposium on Empirical Software Engineering and Measurement (ESEM), pp. 275–284, September 2011

    Google Scholar 

  6. Cukier, D.: DevOps patterns to scale web applications using cloud services. In: Proceedings of the 2013 Companion Publication for Conference on Systems, Programming, & Applications: Software for Humanity, pp. 143–152, SPLASH 2013. ACM, New York (2013)

    Google Scholar 

  7. Ebert, C., Gallardo, G., Hernantes, J., Serrano, N.: Devops. IEEE Softw. 33(3), 94–100 (2016)

    Article  Google Scholar 

  8. Humble, J., Farley, D.: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation. Addison-Wesley Professional, Boston (2010)

    Google Scholar 

  9. Iden, J., Tessem, B., Päivärinta, T.: Problems in the interplay of development and IT operations in system development projects: a Delphi study of Norwegian IT experts. Inf. Softw. Technol. 53(4), 394–406 (2011)

    Article  Google Scholar 

  10. Lindgren, E., Münch, J.: Software development as an experiment system: a qualitative survey on the state of the practice. In: Lassenius, C., Dingsøyr, T., Paasivaara, M. (eds.) XP 2015. LNBIP, vol. 212, pp. 117–128. Springer, Heidelberg (2015). doi:10.1007/978-3-319-18612-2_10

    Chapter  Google Scholar 

  11. Neely, S., Stolt, S.: Continuous delivery? Easy! just change everything (well, maybe it is not that easy). In: Proceedings of the 2013 Agile Conference, pp. 121–128, AGILE 2013. IEEE Computer Society, Washington, DC (2013)

    Google Scholar 

  12. Roche, J.: Adopting DevOps practices in quality assurance. Commun. ACM 56(11), 38–43 (2013)

    Article  Google Scholar 

  13. Smeds, J., Nybom, K., Porres, I.: DevOps: a definition and perceived adoption impediments. In: Lassenius, C., Dingsøyr, T., Paasivaara, M. (eds.) XP 2015. LNBIP, vol. 212, pp. 166–177. Springer, Heidelberg (2015). doi:10.1007/978-3-319-18612-2_14

    Chapter  Google Scholar 

  14. Tessem, B., Iden, J.: Cooperation between developers and operations in software engineering projects. In: Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, pp. 105–108, CHASE 2008, NY, USA. ACM, New York (2008)

    Google Scholar 

Download references

Acknowledgments

This article was supported by TEKES as part of the N4S Program of DIMECC (Digital, Internet, Materials & Engineering Co-Creation).

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Leah Riungu-Kalliosaari .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing AG

About this paper

Cite this paper

Riungu-Kalliosaari, L., Mäkinen, S., Lwakatare, L.E., Tiihonen, J., Männistö, T. (2016). DevOps Adoption Benefits and Challenges in Practice: A Case Study. In: Abrahamsson, P., Jedlitschka, A., Nguyen Duc, A., Felderer, M., Amasaki, S., Mikkonen, T. (eds) Product-Focused Software Process Improvement. PROFES 2016. Lecture Notes in Computer Science(), vol 10027. Springer, Cham. https://doi.org/10.1007/978-3-319-49094-6_44

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-49094-6_44

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-49093-9

  • Online ISBN: 978-3-319-49094-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics