Our previous lesson gave you a definition of, the motivations for, and limitations of using DevOps when creating your software products. In this lesson, we turn to DevOps' basic principles and terminology as used within the software industry.
CALMS is an acronym coined byJohn Willis, Damon Edwards, and Jez Humble, that has become a widespread tool for thinking about how DevOps works in practice. It helps a company to assess its ability to adopt DevOps approaches to software development. Each of the letters stands for the following:
- Culture, which emphasizes that DevOps is as much about cultural change within how an organization operates, as it is about technical or commercial change.
- Automation, which eliminates repetitive manual work, yields repeatable processes, and creates reliable systems.
- Lean, which focuses on ensuring that all processes are defined by continuous improvement throughout the lifecycle of the product's development.
- Measurement, which focuses on proving the ways in which a product's development is continuously improved by gathering and understanding measurable data about the production process.
- Sharing, which emphasizes spreading these approaches to product development across both Development and Operations teams, so as to ensure a standardized approach to development.
Click on each word below to discover the definition and some examples for each.
The DevOps Continuum
Watch below a short animation on how to establish an application lifecycle based on the DevOps Principles.
DevOps is a cultural approach, greatly impacted by lean and agile product development.
Based on the CALMS acronym, you can name the principles of the DevOps approach. In addition, you can rephrase basic phases of the DevOps life-cycle that builds upon those key principles of DevOps.
Links around CALMS on DevOps | SAP Community
Blog post from Google (external link)