Methods of Implementation, Maturity Models and Definition of Roles in DevOps Frameworks: A Systematic Mapping

Monteiro, Luciano de Aguiar; Monteiro, Domingos S. M. P.; Almeida, Washington Henrique Carvalho; Lima, Anderson; Sette, Ioram Schechtman

doi:10.1109/csci51800.2020.00327

Cited by 7 publications

(3 citation statements)

References 43 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Burn‐down charts align with continuous monitoring as they provide insights into the progress of work. Iteration/Sprint Reviews (P14): Iteration or sprint reviews are meetings held at the end of each iteration or sprint to demonstrate completed work to stakeholders and gather feedback 95 . They contribute to continuous monitoring as they provide a checkpoint to assess progress and gather insights for future iterations. Limit Work in Progress (P15): Limiting work in progress (WIP) is a practice of restricting the number of tasks or user stories actively being worked on at any given time 96 . It helps maintain focus, reduce multitasking, and improve flow.…”

Section: Results and Analysismentioning

confidence: 99%

See 1 more Smart Citation

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

Section: Results and Analysismentioning

confidence: 99%

“…• Limit Work in Progress (P15): Limiting work in progress (WIP) is a practice of restricting the number of tasks or user stories actively being worked on at any given time. 96 It helps maintain focus, reduce multitasking, and improve flow. Limiting WIP supports continuous monitoring by promoting a smooth and efficient workflow.…”

Section: Validation Responsesmentioning

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

show abstract

“…Each variable has five levels, respectively from lowest to highest as follows: Initial, Repeatable, Defined, Managed, and Optimized. This model was chosen because its broad scope makes it viable for a holistic evaluation, and its modular nature means that organizations using it can choose which aspects to prioritize independently of each other [32]. In addition, the chosen reference study [13] had a notably identical research objective in specifically evaluating the research object's DevOps maturity level.…”

Section: Related Workmentioning

confidence: 99%

An Evaluation of DevOps Practices to Prevent Fraud: A Case Study of PT XYZ

Adi Hartanto,

Rizal Fathoni Aji

2024

ijcs

View full text Add to dashboard Cite

Fraudulent transactions caused mainly by high level bugs in PT XYZ’s production environment have caused significant financial losses for the company. Such issues were attributed to subpar DevOps practices in PT XYZ. Based on the given problem, this research evaluates DevOps practices in PT XYZ based on Bucena’s maturity model and proposes recommendations for improvement. This study collects data using interviews with four key figures in PT XYZ’s software development team and processed using the thematic analysis method in conjunction with magnitude coding. The results showed that PT XYZ’s primary weaknesses in implementing DevOps practices fall mostly within Technology and Process domains. From these findings, a roadmap is designed for a timeframe of 12 months, which consists of 9 primary objectives to fulfill to increase overall DevOps maturity level at PT XYZ up to the Defined level.

show abstract

Enterprise Architecture and IT Governance to Support the BizDevOps Approach: a Systematic Mapping Study

Fuentes-Quijada,

Ruiz-González,

Caro

2024

Inf Syst Front

View full text Add to dashboard Cite

Current software development practices are transforming the governance and management of software projects with the objective of aligning software products/services with business needs, ensuring business continuity, optimizing resource allocation, and fostering strong stakeholder relationships. The innovative BizDevOps approach has emerged as a response to these challenges, since it extends DevOps by incorporating an additional cycle and involving non-IT stakeholders with a focus on business-IT alignment. The application of IT Governance practices is crucial as regards ensuring the success of complex BizDevOps projects, and this paper, therefore, presents a systematic mapping study that explores the approaches for BizDevOps and encourages DevOps proposals that will seamlessly integrate with the business lifecycle. It examines the support provided by IT Governance practices and investigates the potential roles of Enterprise Architecture. The study analyzed 86 primary studies and 11 secondary studies, revealing a lack of empirical validations and a prevalence of recommendation-oriented papers without concrete solution proposals. These findings highlight the need for further research with which to validate BizDevOps practices and provide actionable insights.

show abstract

Methods of Implementation, Maturity Models and Definition of Roles in DevOps Frameworks: A Systematic Mapping

Cited by 7 publications

References 43 publications

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

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

An Evaluation of DevOps Practices to Prevent Fraud: A Case Study of PT XYZ

Enterprise Architecture and IT Governance to Support the BizDevOps Approach: a Systematic Mapping Study

Contact Info

Product

Resources

About