A year after the Flickr presentation at the O’Reilly Velocity conference and the initial DevOpsDays conference, John Willis and Damon Edwards tried to define the important elements of this new movement called DevOps at the 2010 DevOpsDays conference. They eventually settled on Culture, Automation, Measuring, and Sharing (CAMS).

CAMS remained the approach to DevOps until Jez Humble decided that a Lean Flow was also essential to DevOps and needed to be added to the model. CAMS then became CALMS.

Scaled Agile incorporated DevOps into the Scaled Agile Framework® in 2018. When they did this, they evaluated the current CALMS model and made a realization: sharing is an important part of culture. By establishing that the Culture was one of shared responsibility, it defined the kind of Culture needed for DevOps. It also allowed Recovery to be added to the model, which became CALMR.

In Part 1, we will examine Scaled Agile’s CALMR approach to DevOps. We will examine what characteristics form a Culture of Shared Responsibility. We will then examine the kinds of technology used for automation and who is responsible for setting them up. We will look at how a Lean Flow allows us to deploy quickly and with a high level of quality. We will then look at ensuring quality and security by continuously measuring the progress, correctness, and value of the product under development. Finally, we will look at preventing production failures and what corrective measures we can take if a production failure does occur.

This part of the book comprises the following chapters:

• Chapter 2, Culture of Shared Responsibility
• Chapter 3, Automation for Efficiency and Quality
• Chapter 4, Leveraging Lean Flow to Keep the Work Moving
• Chapter 5, Measuring the Process and Solution
• Chapter 6, Recovering from Production Failures