DevOps has become a powerful movement in the world of software development. By breaking down barriers between development and operations teams, it enables faster, more reliable, and more efficient delivery of value. Yet, organizations often struggle to understand whether they are truly ready to adopt DevOps practices.
This is where the CALMS framework comes in. Originally introduced by thought leaders like Jez Humble in the DevOps Handbook, CALMS offers a simple yet comprehensive way to assess DevOps adoption. It stands for Culture, Automation, Lean, Measurement, and Sharing. Each pillar represents an essential aspect of the DevOps mindset and provides guidance for organizations on their DevOps journey.
In this article, we will explore the five CALMS pillars, their connection to Agile principles, and how they support successful DevOps transformation. By the end, you will understand how CALMS can help teams strengthen agility and achieve continuous improvement.
What is the CALMS Framework?
The CALMS framework is a conceptual model that helps organizations evaluate their readiness for DevOps. It is not a set of tools or technical instructions but a way of thinking that emphasizes collaboration, automation, and learning.
The acronym CALMS stands for:
- Culture
- Automation
- Lean
- Measurement
- Sharing
Together, these five pillars form a DevOps framework that assesses whether a team or organization is prepared for change. They highlight the key DevOps principles needed to move beyond isolated practices and embrace a culture of shared responsibility.
Unlike traditional approaches that focus on processes or technologies alone, CALMS provides a balanced perspective. It shows that successful DevOps requires not just efficient deployment pipelines but also a mindset shift across development teams, operations teams, and leadership.
The 5 CALMS Pillars in DevOps
Culture
At the heart of DevOps lies culture. A successful DevOps transformation depends on trust, transparency, and collaboration across teams. Development and operations must move away from silos and adopt a mindset of shared responsibility.
This cultural shift mirrors the Agile values described in the Agile Manifesto and the Scrum Guide. Team members work together, learn from mistakes, and focus on delivering customer value. A strong DevOps culture also encourages open communication and continuous improvement, enabling organizations to adapt quickly in a changing environment.
Automation
Automation is the backbone of DevOps practices. Without it, teams cannot achieve the speed and reliability required for continuous integration and continuous delivery. Automated deployment pipelines reduce manual errors, shorten lead times, and allow teams to focus on innovation rather than repetitive tasks.
From infrastructure provisioning to testing and monitoring, automation supports the entire development process. It is one of the best practices that drives both productivity and quality, ensuring that DevOps adoption delivers measurable results.
Lean
The Lean pillar applies proven Lean principles to the DevOps world. The goal is to improve the DevOps process by removing waste, reducing bottlenecks, and creating faster feedback loops.
When applied to the development process, Lean encourages small, incremental changes rather than large, risky deployments. This approach supports agility, enabling teams to deliver value early and often. Lean thinking also emphasizes continuous improvement, making it a natural complement to Agile frameworks.
Measurement
In DevOps, improvement is impossible without measurement. Organizations need reliable metrics to understand performance, identify bottlenecks, and validate progress.
The CALMS framework highlights measurement as a way to connect DevOps practices to business outcomes. Teams track deployment frequency, lead time, change failure rate, and recovery time—often referred to as DORA metrics. These measures create feedback loops that allow teams to inspect, adapt, and continuously improve, just as Agile principles recommend.
Sharing
The final pillar, sharing, emphasizes knowledge exchange and transparency across all parts of the organization. DevOps encourages a culture where successes, failures, and lessons learned are openly communicated.
This practice strengthens collaboration between development teams and the operations team, and builds trust. It also ensures that information is not confined to a few experts but is available to all team members. Sharing supports the broader DevOps mindset and is essential for long-term success.
CALMS and Agility
The CALMS DevOps framework is not just about tools or processes; it is about enabling agility at every level. Each of the five CALMS pillars directly supports the principles of Agile, making DevOps and agility natural partners rather than competing approaches.
- Culture aligns with Agile values such as collaboration, transparency, and respect. Without a culture of trust, neither Agile nor DevOps can succeed.
- Automation reinforces Agile’s focus on delivering working software frequently by making deployment fast and reliable.
- Lean mirrors Agile’s emphasis on simplicity and continuous delivery of value.
- Measurement supports empiricism, one of the foundations of Scrum, by providing data for inspection and adaptation.
- Sharing ensures that knowledge flows freely, reducing silos and supporting collaboration across team members.
When combined, these elements turn Agile ceremonies and principles into real business outcomes. For example, a team running Scrum events but without automation or measurement may find that agility isn’t fully realized. The CALMS model ensures that the DevOps mindset and Agile practices work together to deliver continuous improvement and customer value.
In short, CALMS in DevOps creates the bridge between Agile principles and practical delivery, allowing organizations to achieve sustainable and successful DevOps adoption.
Best Practices for Adopting CALMS in DevOps
Adopting the CALMS framework requires more than introducing new tools. It involves a shift in mindset, leadership support, and a commitment to continuous improvement. Below are some best practices to guide a successful DevOps adoption.
Start with culture. Encourage collaboration between development teams and the operations team. Promote a culture of openness where challenges, failures, and lessons learned are shared without blame. This creates the foundation for every other pillar of CALMS.
Invest in automation. Begin with small wins such as automated testing or automated deployment. These improvements shorten the development process, reduce errors, and build confidence in the delivery pipeline.
Apply Lean thinking. Look for bottlenecks in the current DevOps process and remove unnecessary steps. Focus on delivering small increments of value rather than large, risky releases. This Lean approach supports agility and reduces waste.
Measure progress. Define clear metrics that align with business outcomes. Using DORA metrics or other indicators helps teams track performance, improve feedback loops, and connect daily work to organizational goals.
Encourage sharing. Build practices that promote knowledge transfer across team members. This might include shared dashboards, documentation, or communities of practice. Sharing not only strengthens collaboration but also supports long-term DevOps success.
By following these practices, organizations can adopt DevOps processes effectively while using CALMS as a guiding framework. It provides clarity on where to focus first and ensures balance across all aspects of a DevOps transformation.
Role of the Scrum Master in Driving DevOps Success
While DevOps often focuses on technical practices, the Scrum Master plays a crucial role in ensuring its success. Acting as a servant-leader, the Scrum Master helps development and operations teams adopt the DevOps mindset while staying aligned with Agile principles.
One of the most important contributions is fostering a strong DevOps culture. The Scrum Master encourages collaboration and shared responsibility across team members, breaking down silos between development and operations. This cultural shift is essential for successful DevOps implementation.
Scrum Masters also support continuous improvement by using inspection and adaptation. They guide teams in using metrics, such as DORA indicators, to improve feedback loops and strengthen the DevOps process. By making results transparent, they ensure that teams can respond quickly to change.
In addition, Scrum Masters can facilitate discussions on automation, helping teams prioritize work that improves delivery pipelines. They act as catalysts for removing organizational impediments, ensuring that DevOps practices are not blocked by outdated processes or rigid structures.
Finally, the Scrum Master plays a mentoring role in encouraging knowledge sharing. By promoting learning opportunities, communities of practice, and open communication, they help sustain the DevOps journey beyond initial adoption.
In short, Scrum Masters are not technical implementers but cultural and organizational enablers. They ensure that the CALMS pillars are applied effectively, making them key players in the alignment of Agile and DevOps frameworks.
Conclusion
The CALMS framework offers more than a checklist; it provides a balanced lens for evaluating and guiding a DevOps transformation. By focusing on Culture, Automation, Lean, Measurement, and Sharing, organizations can ensure that their DevOps adoption is not only about tools, but about building the right mindset and practices for long-term success.
For Agile teams, CALMS acts as the bridge between principles and execution. It turns the values of the Agile Manifestoand the practices of Scrum into tangible outcomes by enabling faster, more reliable, and sustainable delivery. When paired with meaningful metrics such as the DORA indicators, CALMS helps teams achieve true agility.
The role of the Scrum Master is especially important in this journey. By fostering DevOps culture, encouraging continuous improvement, and facilitating shared responsibility, Scrum Masters act as catalysts for successful DevOpsadoption.
If you want to explore how Agile principles provide the foundation for these practices, discover our guide on the Agile method for project management. Combined with CALMS, Agile and DevOps together unlock the potential for lasting organizational agility.
📚 For a deeper dive, you can also read Accelerate: The Science of Lean Software and DevOps by Nicole Forsgren and Jez Humble, one of the pioneers behind the CALMS acronym and the broader DevOps movement.
