Continuous Monitoring and Changes

Chakraborty, Bapi; Karthikeyan, Shijimol Ambi

doi:10.1007/978-1-4842-5130-0_6

Cited by 2 publications

(1 citation statement)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To facilitate understanding, these practices can be grouped into different phases of the DevOps lifecycle, namely, Continuous Planning, 71,72 Continuous Development, 73 Continuous Testing, 74,75 Continuous Integration, 9 Continuous Deployment, 76 and Continuous Monitoring 77 . These groupings align with industry standards and reflect the interconnected nature of these practices in achieving successful DevOps implementations.…”

Section: Results and Analysismentioning

confidence: 99%

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