Browse Definitions :
Definition

CALMS

Contributor(s): Ivy Wigmore

CALMS is a conceptual framework for the integration of development and operations (DevOps) teams, functions and systems within an organization. The CALMS framework is often used as a maturity model, helping managers to evaluate whether or not their organization is ready for DevOps -- and if not, what needs to change. The acronym CALMS is credited to Jez Humble, co-author of "The DevOps Handbook."

The five pillars of the CALMS framework for DevOps are:

Culture - there is a culture of shared responsibility.

Automation -  team members seek out ways to automate as many tasks as possible and are comfortable with the idea of continuous delivery.

Lean - team members are able to visualize work in progress (WIP), limit batch sizes and manage queue lengths. 

Measurement - data is collected on everything and there are mechanisms in place that provide visibility into all systems.

Sharing - there are user-friendly communication channels that encourage ongoing communication between development and operations.

The CALMS framework is sometimes considered an alternative to ITSM (Information Technology Service Management), a strategic approach to designing, delivering, managing and improving the way IT is used within an organization. ITSM, which is often associated with ITIL (Information Technology Infrastructure Library) is considered by some IT administrators to be too rigid and therefore incompatible with DevOps. CALMS is sometimes thought of as a way of negotiating the differences between the two approaches.

This was last updated in September 2017

Continue Reading About CALMS

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

I believe this acronym is correctly attributed to John Willis and Damon Edwards in its original form - CAMS - Jez Humble later added the L. See here: https://itrevolution.com/devops-culture-part-1/
Cancel

-ADS BY GOOGLE

File Extensions and File Formats

SearchCompliance

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

  • compliance as a service (CaaS)

    Compliance as a Service (CaaS) is a cloud service service level agreement (SLA) that specified how a managed service provider (...

  • data protection impact assessment (DPIA)

    A data protection impact assessment (DPIA) is a process designed to help organizations determine how data processing systems, ...

SearchSecurity

  • quantum key distribution (QKD)

    Quantum key distribution (QKD) is a secure communication method for exchanging encryption keys only known between shared parties.

  • identity theft

    Identity theft, also known as identity fraud, is a crime in which an imposter obtains key pieces of personally identifiable ...

  • cybercrime

    Cybercrime is any criminal activity that involves a computer, networked device or a network.

SearchHealthIT

SearchDisasterRecovery

  • disaster recovery plan (DRP)

    A disaster recovery plan (DRP) is a documented, structured approach that describes how an organization can quickly resume work ...

  • business continuity plan (BCP)

    A business continuity plan (BCP) is a document that consists of the critical information an organization needs to continue ...

  • disaster recovery team

    A disaster recovery team is a group of individuals focused on planning, implementing, maintaining, auditing and testing an ...

SearchStorage

  • logical unit number (LUN)

    A logical unit number (LUN) is a unique identifier for designating an individual or collection of physical or virtual storage ...

  • NVMe over Fabrics (NVMe-oF)

    NVMe over Fabrics, also known as NVMe-oF and non-volatile memory express over fabrics, is a protocol specification designed to ...

  • CIFS (Common Internet File System)

    CIFS (Common Internet File System) is a protocol that gained popularity around the year 2000, as vendors worked to establish an ...

Close