Characterizing DevOps Culture: A Systematic Literature Review

A systematic mapping study about DevOps

“…According to the analyzed studies, it was also observed that DevOps represents: an approach [35,52,55], a cultural movement [17,57], a set of practices [23,27], an emerging paradigm [38,56], a mixture of two words [39], a phenomenon [40], an interdisciplinary theme [22], a set of principles [41], a conceptual framework [42], a development methodology [51], an artificial word [44], a philosophy [47] and a neologism [36]. From the above, it can be evidenced that DevOps has been interpreted in several ways because it is a relatively new subject.…”

“…Classification scheme 3.2. Question Q2: What type of research is carried out in the analyzed literature?The studies selected in this research can be divided into two categories: (i) studies with concrete proposals on the adoption of DevOps[17, 23, 40, 44-47, 49, 50, 56] and (ii) systematic reviews of literature[21,27,35,36,42,48,55,57]. Regarding the first category, it was found that 90% of the studies[17, 23, 40, 44-47, 49, 50] registered on the adoption of DevOps use case studies to validate their proposals, these Case studies have been carried out in a range of one to five years in their application depending on the size of the project.…”

A Survey of DevOps in the South African Software Context

“…DevOps Culture: DevOps is arguably more of a culture shift within IT than a process or tool shift [4,37]. DevOps emphasizes a new culture in which development and deployment tasks are shared between developer and operation teams and where all team members accept responsibility for the quality of the final deliverable [7,32].…”

“…DevOps sees operations engineers picking up development tasks and developers working in an operations environment [40]. DevOps requires communication and collaboration between development and operations [37]. For example in a DevOps culture, operations representatives should attend the meetings traditionally assigned to development and project management teams [4].…”

Untitled

“…This is closely linked to CAMS (Culture-Automation-Measurement-Sharing) model originally coined by John Willis and Damon Edwards [19] and later refined to CALMS (Culture-Automation-Lean-Measurement-Sharing) by Jez Humble. CALMS shares similarities with another model that involves a specific set of categories namely: agility, automation, collaborative culture; also called DevOps Culture [49], continuous measurement, quality assurance, resilience, sharing and transparency [50]. This can be further extended to include collaboration in terms of empathy [44], respect, trust, responsibility and incentive alignment and open communication [51].…”