Adopting DevOps practices in quality assurance

Roche, J. C.

doi:10.1145/2524713.2524721

Cited by 106 publications

(73 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Software distribution has changed and recurring software updates can happen to the point that software releases are served at the same time as when software is being used [12]. Because of the nature and frequency of the releases, possible issues in the production systems need to be monitored closely in order to provide optimum user experience [12].…”

Section: Introductionmentioning

confidence: 99%

DevOps Adoption Benefits and Challenges in Practice: A Case Study

Riungu-Kalliosaari

Mäkinen

Lwakatare

et al. 2016

Lecture Notes in Computer Science

122

103

View full text Add to dashboard Cite

Abstract. DevOps is an approach in which traditional software engineering roles are merged and communication is enhanced to improve the production release frequency and maintain software quality. There seem to be benefits in adopting DevOps but practical industry experiences have seldom been reported. We conducted a qualitative multiple-case study and interviewed the representatives of three software development organizations in Finland. The responses indicate that with DevOps, practitioners can increase the frequency of releases and improve test automation practices. DevOps was seen to encourage collaboration between departments which boosts communication and employee welfare. Continuous releases enable a more experimental approach and rapid feedback collection. The challenges include communication structures that hinder cross-department collaboration and having to address the cultural shift. Dissimilar development and production environments were mentioned as some of the technical barriers. DevOps might not also be suitable for all industries. Ambiguity in the definition of DevOps makes adoption difficult since organizations might not know which practices they should implement for DevOps.

show abstract

Section: Introductionmentioning

confidence: 99%

DevOps Adoption Benefits and Challenges in Practice: A Case Study

Riungu-Kalliosaari

Mäkinen

Lwakatare

et al. 2016

Lecture Notes in Computer Science

122

103

View full text Add to dashboard Cite

show abstract

“…More specifically, DevOps encompasses automation for reducing manual effort and improving stability, continuous feedback using metrics for improving software development processes, and a culture of collaboration and information sharing between teams [2]. However, the term "DevOps" is still an ambiguous concept and is lacking a standard definition [3][4][5]. While the purpose of DevOps is clear, organizations adopting DevOps must interpret and define what DevOps means to them.…”

Section: Introductionmentioning

confidence: 99%

On the Impact of Mixing Responsibilities Between Devs and Ops

Nybom

Smeds

Porres

2016

Agile Processes, in Software Engineering, and Extreme Programming

View full text Add to dashboard Cite

Abstract. Many software engineering organizations around the world are adopting DevOps. One of the goals of DevOps is to foster better collaboration between development and operations personnel, in order to improve organizational efficiency. Since DevOps is lacking a common definition, there are several approaches to adopt it, and organizations largely need to determine how to apply DevOps for themselves. In this paper, we present results from a case study in which a software organization adopts DevOps. The focus of this research is to study the impact of mixing the responsibilities between development and operations engineers. We interviewed 14 employees in the organization during the study, and results indicate several benefits of the chosen approach, such as improved collaboration and trust, and smoother work flow. This comes at the cost of a number of complications, such as new sources for friction among the employees, risk for holistically sub-optimal service configurations, and more.

show abstract

“…A weakness of Agile is the difficulty of providing quality assurance, since the activities no longer fit into a plan with fixed terms of delivery software, as happens in Waterfall methodology. DevOps exceed this barrier through cooperation and tooling, and through real time monitoring, as a methodology for detecting problems faced by end-user [24]. The literature in domain reflects the major changes introduced by DevOps in software development management and the advantages obtained by the steady collaboration between developers and operational and continuous delivery software to the customer [15].…”

Section: Is Devops a Methodology Or An Extension Of Agile?mentioning

confidence: 99%