Characterizing DevOps by Hearing Multiple Voices

França, Breno Bernard Nicolau de; Jeronimo, Helvio; Travassos, Guilherme Horta

doi:10.1145/2973839.2973845

Cited by 64 publications

(70 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Similarly, we also only made a simple comparison for the principles identified in the 2 studies. Nicolau de França et al have identified six principles, which overlap our findings. Three of their 6 identified principles have identical names and meanings as the principles identified in this review: “Principle 2 (Automation)” to Pr2 (automation), “Principle 5 (Sharing)” to Pr1 (sharing knowledge), and “Principle 6 (Measurement)” to Pr5 (measurement).…”

Section: Discussionsupporting

confidence: 79%

“…Nicolau de França et al also conducted a literature study with a focus similar to our study, although their study contains only a few peer‐reviewed and more gray literature like websites, technical reports, and industrial sources. Overall, in comparison to Nicolau de França et al, our review has the following distinctive features: We focused solely on the peer‐reviewed literature and identified significantly more published studies. Identified principles, practices, and benefits and the relations among ( a ) DevOps practices and ( b ) their links to DevOps benefits. We also synthesized the results in the form of a benefits dependency network. …”

Section: Discussionmentioning

confidence: 99%

“…Nicolau de França et al have also conducted a literature review on DevOps to characterize the industrial perspectives. They used various types of data source including websites, technical reports, and few peer‐reviewed studies.…”

Section: Related Workmentioning

confidence: 99%

“…According to ProfitBricks, there have been 49 practitioner‐oriented conferences and events for DevOps in 2016. However, it has not been as widely investigated in the scientific community yet …”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

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

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature.In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. KEYWORDSbenefits and values, challenges, development and operations, DevOps, principles and practices, systematic literature review

show abstract

Section: Discussionsupporting

confidence: 79%

Section: Discussionmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

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

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…As argued by Boehm (2008), in the face of an increasingly dynamic and competitive market, software development organizations need to support continuous and fast delivery of value to the customer in both short and long terms. In this scenario, many software organizations introduce agility practices into their development processes to handle the frequents requirements changes and the continuous delivery demand (de França et al 2016).…”

Section: Introductionmentioning

confidence: 99%

A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil

Silva

Jeronimo

Travassos

2019

JSERD

Self Cite

View full text Add to dashboard Cite

Technical debt (TD) is receiving more and more attention to software engineering. Although it was initially used as a communication tool for technical and non-technical stakeholders, nowadays this concept supports the improvement of the software’s internal quality. Despite the increasing number of studies regarding TD and its management, only a few are concerned with the industry. Therefore, this primary study aims to characterize TD and its management under the perspective of Brazilian software organizations using their practitioners as proxies. A survey was performed with 62 practitioners, representing around 12 organizations and 30 software projects. The analysis of 40 valid questionnaires indicates that TD is still unknown to a considerable fraction of the participants, and only a small group of organizations adopt TD management activities in their projects. The survey package is available and can be used to support further investigations on TD management in software organizations.

show abstract

A hybrid DevOps process supporting software reuse: A pilot project

Ali

Daneth

Hong

2020

J Software Evolu Process

View full text Add to dashboard Cite

Large software development organizations manage reusable software components through a reusable software repository in order to reduce development time and cost and to improve software quality and productivity. This paper presents a hybrid DevOps process with a systematic reuse‐based software development and management process to reduce the effort and cost required for the rework and to increase productivity. The proposed approach promotes the systematic reuse of software components based on both information retrieval and ontology‐based retrieval techniques. The reusable assets are presented in different styles to ease and support the reuse process with fine‐grained reusable artifacts. To evaluate our proposed process, a pilot project, aiming to monitor the health of a patient, was developed and monitored the reuse activities throughout the whole experiment. The results revealed that our proposed process got an average gain of 35.2% in terms of developed function points by reusing 30.63% of reusable artifacts available in the reuse repository.

show abstract

Characterizing DevOps by Hearing Multiple Voices

Cited by 64 publications

References 13 publications

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

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

A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil

A hybrid DevOps process supporting software reuse: A pilot project

Contact Info

Product

Resources

About