skip to main content
10.1145/2973839.2973845acmotherconferencesArticle/Chapter ViewAbstractPublication PagessbesConference Proceedingsconference-collections
research-article

Characterizing DevOps by Hearing Multiple Voices

Authors Info & Claims
Published:19 September 2016Publication History

ABSTRACT

Recently, DevOps has emerged as an alternative for software organizations inserted into a dynamic market to handle daily software demands. As claimed, it intends to make the software development and operations teams to work collaboratively. However, it is hard to observe a shared understanding of DevOps, what potentially hinders the discussions in the literature and can confound observations when conducting empirical studies. Therefore, we performed a Multivocal Literature Review aiming at characterizing DevOps in multiple perspectives, including data sources from technical and gray literature. Grounded Theory procedures were used to rigorous analyze the collected data. It allowed us to achieve a grounded definition for DevOps, as well as to identify its recurrent principles, practices, required skills, potential benefits, challenges and what motivates the organizations to adopt it. Finally, we understand the DevOps movement has identified relevant issues in the state-of-the-practice. However, we advocate for the scientific investigations concerning the potential benefits and drawbacks as a consequence of adopting the suggested principles and practices.

References

  1. Boehm, Barry. Making a Difference in the Software Century. Computer, 41, 3 (March 2008), 32--38. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. PUPPET LABS & IT REVOLUTIONS PRESS. State of DevOps Report. Puppet Labs, 2013.Google ScholarGoogle Scholar
  3. Erich, Floris, Chintan, Amrit, and Maya, Daneva. A Mapping Study on Cooperation between Information System Development and Operations. In Proceedings of the 15th PROFES (Helsinki, Finland December, 2014), 277--280.Google ScholarGoogle ScholarCross RefCross Ref
  4. Mueller, Ernest. What Is DevOps? The Agile Admin. 2010. Retrieved from: http://goo.gl/mD3LU1.Google ScholarGoogle Scholar
  5. Lwakatare, Lucy Ellen, Kuvaja, Pasi, and Oivo, Markku. Dimensions of DevOps. (Finland 2015), Springer.Google ScholarGoogle Scholar
  6. Biochini, Jorge, Mian, Paula Gomes, Natali, Ana Candida Cruz, and Travassos, Guilherme Horta. Systematic Review in Software Engineering. COPPE/UFRJ, Rio de Janeiro, 2005.Google ScholarGoogle Scholar
  7. Kitchenham, Barbara A. and Charters, S. Guidelines for Performing Systematic Literature Reviews in Software Engineering. Keele University, 2007.Google ScholarGoogle Scholar
  8. Ogawa, Rodney T and Malen, Betty. Towards Rigor in Reviews of Multivocal Literatures: Applying the Exploratory Case Study Method. Review of Educational Research, 61, 3 (1991), 265--286.Google ScholarGoogle Scholar
  9. Strauss, Anselm and Corbin, Juliet. Basics of qualitative research: Procedures and techniques for developing grounded theory. SAGE, Newbury Park, 1990.Google ScholarGoogle Scholar
  10. Roche, J. Adopting DevOps Practices in Quality Assurance. Communications of the ACM, 56, 11 (2013), 38--43. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Liu, Yuhong, Li, Chengbo, and Liu, Wei. Integrated Solution for Timely Delivery of Customer Change Requests: A Case Study of Using DevOps Approach. International Journal of U-& E-Service, Science & Technology, 7, 2 (2014), 41--50.Google ScholarGoogle Scholar
  12. Mohamed, Samer I. DevOps shifting software engineering strategy Value based perspective. IOSR Journal of Computer Engineering (IOSR-JCE), 17, 2 (April 2015), 51--57.Google ScholarGoogle Scholar
  13. Economou, Frossie, Hoblitt, Joshua C., and Norris, Pat. Your data is your dogfood DevOps in the astronomical observatory. 2014.Google ScholarGoogle Scholar
  14. Erich, Floris, Amrit, Chintan, and Daneva, Maya. Report: DevOps Literature Review. University of Twente, 2014.Google ScholarGoogle Scholar
  15. Walls, Mandi. Building a DevOps Culture (2013).Google ScholarGoogle Scholar
  16. Berczuk, Steve. Agile Teams Care About DevOps. 2011. Retrieved from: http://goo.gl/Rw2pWZ.Google ScholarGoogle Scholar
  17. Hedemark, Magnus. DevOps in Straight English -- Enter the Buzzword. RedHat Developers. 2014. Retrieved from: http://goo.gl/W5LMws.Google ScholarGoogle Scholar
  18. Nelson-Smith, Stephen. What Is This Devops Thing, Anyway? Jedi (Patrick Debois' Blog). 2010. Retrieved from: http://goo.gl/qsmNqO.Google ScholarGoogle Scholar
  19. Debois, Patrick. Devops Areas - Codifying devops practices. Jedi (Patrick Debois' Blog). 2014. Retrieved from: http://goo.gl/25sCB3.Google ScholarGoogle Scholar
  20. Humble, Jez. There's No Such Thing as a "Devops Team". Continuous Delivery. 2012. Retrieved from: http://goo.gl/9bTKhb.Google ScholarGoogle Scholar
  21. Tesar, David. DevOps Practices. ITPROGUY.com. 2015. Retrieved from: http://goo.gl/iKPgTJ.Google ScholarGoogle Scholar
  22. Geer, David. Internap's DevOps Culture: PrivateStack + CD = ? {Read On & Draw Your Own Conclusions}. DevOps.com. 2015. Retrieved from: http://goo.gl/vVAqqZ.Google ScholarGoogle Scholar
  23. NEW RELIC. DevOps. New Relic. 2015. Retrieved from: http://goo.gl/IDfddk.Google ScholarGoogle Scholar
  24. Garnichaud, Neil. What Exactly is DevOps. DrDroobs. 2012. Retrieved from: http://goo.gl/V2ev4J.Google ScholarGoogle Scholar
  25. Willis, John. What DevOps Means to Me. Chef.io. 2010. Retrieved from: https://goo.gl/stl6Go.Google ScholarGoogle Scholar
  26. Corriere, Chris. The devOpsSec Dilemma: Effective Strategies for Social Networking. DevOps.com. 2015. Retrieved from: http://goo.gl/fIp7wL.Google ScholarGoogle Scholar
  27. Bang, Soon K, Chung, Sam, Choh, Young, and Dupuis, Marc. A Grounded Theory Analysis of Modern Web Applications - Knowledge, Skills, and Abilities for DevOps. In RIIT'13 ( 2013), ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. Cukier, Daniel. DevOps patterns to scale web applications using cloud services. In Proceedings of the 2013 conference on Systems, programming, & applications: software for humanity ( 2013), ACM, 143--152. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. Hussaini, Syed W. Strengthening harmonization of Development (Dev) and Operations (Ops) silos in IT environment through Systems approach. In IEEE 17th Int. Conf. Intelligent Transportation Systems ( 2014), 178--183.Google ScholarGoogle ScholarCross RefCross Ref
  30. Erich, Floris, Amrit, Chintan, and Daneva, Maya. Cooperation between information system development and operations: a literature review. In Proceedings of the 8th ACM/IEEE ESEM (Torino, Italy September 18-19, 2014). Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. Kim, J., Meirosu, C., Papafili, I., Steinert, R., Sharma, S., Westphal, F. J., and Manzalini, A. Service provider DevOps for large scale modern network services. In Int. Symp. on Integrated Network Management, IFIP/IEEE ( 2015).Google ScholarGoogle ScholarCross RefCross Ref
  32. Waller, Jan, Ehmke, Nils C., and Hasselbring, Wilhelm. Including Performance Benchmarks into Continuous Integration to Enable DevOps. ( 2015), ACM SIGSOFT Software Engineering Notes, 1--4. Google ScholarGoogle ScholarDigital LibraryDigital Library
  33. Pengxiang, Ji and Leong, Peter. Teaching Work-ready Cloud Computing Using the DevOps Approach. In Int. Symp. on Advances in Technology Education (Singapore 2014), Nanyang Polytechnic.Google ScholarGoogle Scholar
  34. Sussna, Jeff. Cloud and DevOps: A Marriage Made in Heaven. Introducing DevOps to the Traditional Enterprise / eMag, 14 (June 2014).Google ScholarGoogle Scholar
  35. Phillips, Andrew. Preparing for Continuous Delivery in the Enterprise. Introducing DevOps to the Traditional Enterprise / eMag, 14 (June 2014).Google ScholarGoogle Scholar
  36. Manglani, Kamal and Bothello, Gerald. DevOps - Pivoting Beyond Pockets. Introducing DevOps to the Traditional Enterprise / eMag, 14 (2014).Google ScholarGoogle Scholar
  37. Humble, Jez and Molesky, Joanne. Why Enterprises Must Adopt Devops to Enable Continuous Delivery. The Journal of Information Technology Management, 24, 8 (2011).Google ScholarGoogle Scholar
  38. Shamow, Eric. Devops at Advance Internet: How We Got in the Door. The Journal of Information Technology Management, 24, 8 (August 2011).Google ScholarGoogle Scholar
  39. Fitzpatrick, Lawrence and Dillon, Michael. The Business Case for Devops: A Five-Year Retrospective. The Journal of Information Technology Management, 24 (August 2011).Google ScholarGoogle Scholar
  40. Phifer, Bill. Next-Generation Process Integration: CMMI and ITIL Do Devops. Cutter IT Journal, 24, 8 (2011).Google ScholarGoogle Scholar
  41. DeGrandis, Dominica. Devops: So You Say You Want a Revolution? The Journal of Information Technology Management, 24, 8 (August 2011).Google ScholarGoogle Scholar
  42. Smith, David M. Hype Cycle for Cloud Computing. Gartner Research, Inc, 2011.Google ScholarGoogle Scholar
  43. Duvall, Paul. Breaking down barriers and reducing cycle times with DevOps and continuous delivery. New Relic. 2012. Retrieved from: http://goo.gl/dqhwod.Google ScholarGoogle Scholar
  44. Azoff, Michael. DevOps Advances in release Management and Automation. Ovum, 2011.Google ScholarGoogle Scholar
  45. PUPPET LABS & IT REVOLUTIONS PRESS. State of DevOps Report. Puppet Labs, 2014.Google ScholarGoogle Scholar
  46. Michelsen, John. Dysfunction Junction: A Pragmatic Guide to Getting Started with DevOps. CA Technologies. 2013. Retrieved from: http://goo.gl/A1ZAYM.Google ScholarGoogle Scholar
  47. APPDYNAMICS, INC. From Dev to Ops: An Introduction. 2014. Retrieved from: https://goo.gl/qn1xUi.Google ScholarGoogle Scholar
  48. CA TECHNOLOGIES. TechInsights Report: What Smart Businesses Know About DevOps. CA Technologies, 2013.Google ScholarGoogle Scholar
  49. Limoncelli, Thomas A. and Hughes, Doug. DevOps: New Challenges, Proven Values.; login:, 36, 4 (2011), 46--48.Google ScholarGoogle Scholar
  50. Womack, James P and Jones, Daniel T. Lean thinking: banish waste and create wealth in your corporation. Simon and Schuster, 2010.Google ScholarGoogle Scholar
  51. Petersen, Kai, Vakkalanka, Sairam, and Kuzniarz, Ludwik. Guidelines for conducting systematic mapping studies in software engineering: An update. IST, 64 (2015), 1--18. Google ScholarGoogle ScholarDigital LibraryDigital Library
  1. Characterizing DevOps by Hearing Multiple Voices

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Other conferences
      SBES '16: Proceedings of the XXX Brazilian Symposium on Software Engineering
      September 2016
      167 pages
      ISBN:9781450342018
      DOI:10.1145/2973839

      Copyright © 2016 ACM

      © 2016 Association for Computing Machinery. ACM acknowledges that this contribution was authored or co-authored by an employee, contractor or affiliate of a national government. As such, the Government retains a nonexclusive, royalty-free right to publish or reproduce this article, or to allow others to do so, for Government purposes only.

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 19 September 2016

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • research-article
      • Research
      • Refereed limited

      Acceptance Rates

      Overall Acceptance Rate147of427submissions,34%

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader