Cooperation between information system development and operations

Abstract

CONTEXTSoftware development can profit from improvements in the deployment and maintenance phases. DevOps improves these phases through a collection of principles and practices, centered around close collaboration between Development and Operations personnel. Both sides have paid little attention to issues faced by each other. Yet knowledge sharing is invaluable. Development personnel can for example make software more robust by implementing scalability and performance features desired by operations personnel. GOALAs a starting point for research into DevOps we performed a Systematic Literature Review (SLR) on DevOps.The main question we address in this research is "How does the relation between development and operations influence Information System development?" We asked the following research questions: (1) What are the main concepts related to DevOps? (2) What are the problems encountered in Information System development attributed to the relation between development and operations? (3) How does DevOps alleviate the problems in RQ2?We used Kitchenham's SLR guidelines for conducting the SLR [1]. We used three search terms: (1) DevOps; (2) "Continuous Delivery" AND Software; and (3) "development and operations" AND software. We applied the search terms to the databases of Scopus, Web of Science, IEEE Xplore and ACM Digital Library. As a literature review is conceptcentric [2], we constructed a table describing which major concepts we encountered during the review. RESULTSFor this research we selected 13 journal articles, 10 conference proceedings and two industry reports, totaling 25 articles. Most journal articles (8) originate from the Cutter IT Journal as it released a special issue on DevOps. The main concepts related to DevOps are culture, automation, measurement, sharing, services, quality assurance, structures and standards. The first four of these concepts form the CAMS framework, which multiple articles referred to. The framework can also be used for categorizing problems in adopting DevOps, and for making a DevOps implementation strategy. DevOps is supported by principles and practices which solve problems in each category of the framework. CONCLUSIONSOrganizations need to change their structures for supporting DevOps. We discovered that DevOps is an approach and not a method. Organizations need to experiment with the principles and practices to discover which work for them.There is a great opportunity for empirical researchers to study organizations experimenting with DevOps. Our research aims at helping researchers and practitioners reason about and define DevOps clearly. We hope that in the future a framework for implementing DevOps will be created using the concepts we identified in this research.

Towards a benefits dependency network for DevOps based on a systematic literature review

“…It leads to lower failure rates in new releases by focusing on communication and collaboration between developers and operators. (CB10) Maximize maintainability. Erich et al point out deployment and maintenance improvements achieved through a collection of practices for close collaboration between development and operations personnel. Also, Park et al state that by the adoption of DevOps, maximal maintainability can be achieved. (CB11) Improve reliability.…”

“…However, the definitions of the principles aligned well based on the same peer‐reviewed references. ()…”

“…Few systematic studies have been conducted on the topic of DevOps. Erich et al studied the cooperation between information system (IS) development and operations. They identified 139 papers and summarized results from 26 of them in the form of a mapping study.…”

A Systematic Literature Review on DevOps Capabilities and Areas

“…DevOps use various forms of measurements and monitoring which include business metrics (e.g. revenue) to metrics for a technical overview (Rana & Staron, 2016) (Bang, Chung, Choh, & Dupuis, 2013;Bucena & Kirikova, 2017;Colomo-Palacios et al, 2018;de França et al, 2016;Debois, 2011;Diel et al, 2016;Erich, Amrit, & Daneva, 2014;Gupta, Kapur, & Kumar, 2017;Hüttermann, 2012;Jabbari et al, 2016b;Lassenius et al, 2015;Nielsen et al, 2017;Perera, Silva, & Perera, 2017;Rana & Staron, 2016;Sharma & Coyne, 2015;Silva et al, 2018) 16 A2 Measurement (Bang et al, 2013;Colomo-Palacios et al, 2018;de França et al, 2016;Debois, 2011;Erich et al, 2014;Gupta et al, 2017;Hüttermann, 2012;Jabbari et al, 2016b;Lassenius et al, 2015;Luz et al, 2018;Nielsen et al, 2017;Perera, Silva, et al, 2017;Rana & Staron, 2016;Silva et al, 2018) 14 A3 Sharing (Bang et al, 2013;Colomo-Palacios et al, 2018;de França et al, 2016;Debois, 2011;Erich et al, 2014;Gupta et al, 2017;Hüttermann, 2012;Jabbari et al, 2016b;Lassenius et al, 2015;…”

“…Quality (Erich et al, 2014;Luz et al, 2018;Mohamed, 2015) 3 A9 Collaboration (Luz et al, 2018;Mohamed, 2015…”