An Empirical Taxonomy of DevOps in Practice

Macarthy, Ruth W.; Bass, Julian M.

doi:10.1109/seaa51224.2020.00046

Cited by 56 publications

(41 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, many definitions include common aspects outlined in this paper. Furthermore, the conflicting views (DevOps as a cultural movement vs. DevOps as a job description) make it evident, that there is a divide regarding the definition [24].…”

Section: Discussionmentioning

confidence: 99%

“…DevOps is often described as a software engineering culture and philosophy, which employs crossfunctional teams in order to build test and release software faster and more reliably [24]. This is mainly achieved through automation.…”

Section: Definitionmentioning

confidence: 99%

“…In the scientific community, many views and stances on DevOps have been developed. Macarthy & Bass [24] show two conflicting views: DevOps is a cultural movement used to facilitate rapid software development (1) and the view that DevOps is rather a job description, which requires both development and IT operation skills (2).…”

Section: Definitionmentioning

confidence: 99%

“…For example, the implementation of DevOps in SMEs (small and medium-sized enterprises) has not been researched comprehensively in the literature. Various scholars point to this scarcity on the topic, noting that implementation in practice creates a level of uncertainty [24].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

DevOps Adoption: Challenges & Barriers

Krey¹

2022

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

As a modern software engineering paradigm, DevOps has recently gained increasing acceptance in the industry as a set of practices and cultural values to address daily dynamic software demands. While the rising trend of DevOps and its characteristics and challenges have often been characterized by practitioner communities and academic research circles, there is still a lack of a thorough understanding of how to tackle DevOps adoptions. This paper aims to help fill this gap by identifying, discussing, and summarizing current academic and practitioner DevOps adoption & implementation research. Our findings provide a basis for theoretical, empirical, or design-oriented research for IS scholars, that has the potential to be of practical importance. Our goal is to improve understanding of DevOps adoption by uncovering ambiguities in terms, conceptual conflations, and ideas underlying different uses of the concept as well as providing methods to deal with common challenges in the adoption process.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Definitionmentioning

confidence: 99%

Section: Definitionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

DevOps Adoption: Challenges & Barriers

Krey¹

2022

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

show abstract

“…ere are some other studies that highlighted DevOps significance in various aspects. For example, Macarthy and Bass [14] worked on building taxonomy of DevOps in practices, Gokarna and Singh [15] empirically investigated the historical background of DevOps, Mishra and Otaiwi [16] discussed in their research DevOps software quality to maintain continuous environment, and Rafi et al [17] discussed the data quality aspects of software application while adopting DevOps.…”

Section: Background and Motivationmentioning

confidence: 99%

Decision-Making Taxonomy of DevOps Success Factors Using Preference Ranking Organization Method of Enrichment Evaluation

Rafi

Akbar

Alsanad

et al. 2022

Mathematical Problems in Engineering

View full text Add to dashboard Cite

Due to multitudes factors like rapid change in technology, customer needs, and business trends, the software organizations are facing pressure to deliver quality software on time. To address this concern, the software industry is continually looking the solution to improve processing timeline. Thus, the Development and Operations (DevOps) has gained a wide popularity in recent era, and several organizations are adopting it, to leverage its perceived benefits. However, companies are facing several problems while executing the DevOps practices. The objective of this work is to identify the DevOps success factors that will help in DevOps process improvement. To accomplish this research firstly, a systematic literature review is conducted to identify the factors having positive influence on DevOps. Secondly, success factors were mapped with DevOps principles, i.e., culture, automation, measurement, and sharing. Thirdly, the identified success factors and their mapping were further verified with industry experts via questionnaire survey. In the last step, the PROMETHEE-II method has been adopted to prioritize and investigate logical relationship of success factors concerning their criticality for DevOps process. This study’s outcomes portray the taxonomy of the success factors, which help the experts design the new strategies that are effective for DevOps process improvement.

show abstract

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Kumar,

Nadeem,

Shameem

2023

J Software Evolu Process

View full text Add to dashboard Cite

Increasingly, software organizations are implementing DevOps culture to benefit from it in terms of continuous testing, delivery, improvement, and so forth. Implementing DevOps is difficult due to a lack of understanding about the practices and their effective application for its effective implementation. This paper aims to explore different DevOps practices that can be implemented in software organizations. The study involves conducting a systematic literature review (SLR) to identify DevOps implementation practices, followed by the utilization of the fuzzy best–worst method (FBWM) to establish a taxonomy or classification of software practices. We have used an SLR to investigate the practices, and subsequently, the survey method was followed to validate the identified practices. Moreover, the best–worst method (BWM) was considered to evaluate the significance and develop the taxonomy of the practices. The results of this study extracted 19 practices that have been identified in the SLR process. The identified factors are further classified into six core DevOps lifecycle phases. The results of the BWM approach are shown. The outcomes of the study conclude that the proposed taxonomy of the practices could help DevOps practitioners and researchers effectively implement them in software development organizations.

show abstract

An Empirical Taxonomy of DevOps in Practice

Abstract: Ti t l eAn e m pi ric al t a xo n o my of D evO p s in p r a c tic e

Cited by 56 publications

References 21 publications

DevOps Adoption: Challenges & Barriers

DevOps Adoption: Challenges & Barriers

Decision-Making Taxonomy of DevOps Success Factors Using Preference Ranking Organization Method of Enrichment Evaluation

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Contact Info

Product

Resources

About