2015
DOI: 10.1007/978-3-319-18612-2_19
|View full text |Cite
|
Sign up to set email alerts
|

Dimensions of DevOps

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
96
0
1

Year Published

2016
2016
2022
2022

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 102 publications
(97 citation statements)
references
References 25 publications
0
96
0
1
Order By: Relevance
“…Practitioners have defined various mnemonics to describe DevOps: CAMS (Culture, Automation, Measurement, Sharing), CALMS (CAMS + Lean), and CAMM (Culture, Automation, Measurement, Monitoring) . In the interviews, culture and automation are universally considered to be core parts of DevOps adoption.…”
Section: Discussionmentioning
confidence: 99%
“…Practitioners have defined various mnemonics to describe DevOps: CAMS (Culture, Automation, Measurement, Sharing), CALMS (CAMS + Lean), and CAMM (Culture, Automation, Measurement, Monitoring) . In the interviews, culture and automation are universally considered to be core parts of DevOps adoption.…”
Section: Discussionmentioning
confidence: 99%
“…One view identifies DevOps as a specific job description that requires a combination of software development and IT operations skills, and the other argues that the spirit of DevOps addresses an emerging need in contemporary software development rather than a job position. In an attempt to address this issue, one of the two main streams of research in DevOps has strived on achieving a 2 clear understanding of (i) of definitions and characterization of DevOps and its associated practices [7,[10][11][12][13], and (ii) the benefits and challenges of adopting DevOps [7,8]. For example, while Culture, Automation, Measurement, Sharing, Services have been identified as the main dimensions of DevOps [10], others have described it as a cultural movement that enables rapid development with four defining characteristics: open communication, incentive and responsibility alignment, respect, and trust [14].…”
Section: Related Researchmentioning
confidence: 99%
“…Each build / release should undergo this cycle of dev -fvt -regression -stage -production -test phases by clearing all the quality parameters. With this automated pipeline there will be consistent releases [7,8].…”
Section: Delivery Pipeline Figure 7: Delivery Pipelinementioning
confidence: 99%