As organizations scale Agile practices using frameworks like SAFe®, they inevitably encounter challenges around cross-team coordination, automation, and delivering value continuously. DevOps provides the technical and cultural capabilities needed to support agility at scale—but where should teams begin?

Enter the CALMS Framework, a powerful model that helps Agile teams—and the organizations they support—assess readiness for DevOps and foster sustainable, scalable delivery.

What Is the CALMS Framework?

CALMS stands for Culture, Automation, Lean, Measurement, and Sharing. It was developed to articulate the key dimensions of a successful DevOps transformation, but its relevance goes well beyond DevOps engineers. In a scaled Agile context, CALMS becomes a cross-cutting enabler, helping Agile Release Trains (ARTs), Solution Trains, and Value Stream teams deliver faster and more effectively.

Think of CALMS as a diagnostic and guiding framework—one that aligns technical practices with Agile principles across the enterprise.

CALMS Pillars in a Scaled Agile Context

Culture

At scale, culture becomes even more critical. Scaled Agile emphasizes alignment, transparency, and decentralized decision-making—principles that are deeply supported by the collaborative and learning-driven culture in CALMS.

In a SAFe® environment:

• Teams on an ART must share a common mission and vision.
• Psychological safety and trust enable innovation and continuous improvement (Inspect & Adapt).
• Leaders serve as coaches, reinforcing Lean-Agile values.

Example: During PI Planning, team members collaborate openly, raise risks early, and commit as a group to shared objectives—hallmarks of a strong DevOps culture.

Automation

To synchronize dozens (or hundreds) of Agile teams and maintain flow, automation isn’t optional—it’s essential. SAFe advocates for Continuous Delivery Pipelines, where automation is the backbone of build, test, deploy, and release activities.

Scaled Agile teams benefit from:

• Automated integration across component teams
• Infrastructure as Code for consistent environments
• Quality gates and test automation embedded in Definition of Done

Example: ARTs automate compliance checks and regression tests across multiple teams, ensuring that every increment supports release on demand.

Lean

Lean thinking is a core principle of both SAFe and CALMS. Lean drives efficiency, customer focus, and value delivery across the system—not just individual teams.

In scaled Agile:

• Lean Portfolio Management ensures prioritization based on business value.
• Teams limit WIP, use Kanban systems, and optimize flow through value streams.
• MVPs are released to validate hypotheses before scaling investment.

Example: A Solution Train releases a thin slice of functionality across multiple ARTs to get early customer feedback, instead of waiting for a full system integration.

Measurement

Scaled organizations can’t improve what they don’t measure. CALMS emphasizes data-driven decision-making, which aligns directly with SAFe’s use of flow metrics, OKRs, and PI Objectives.

Useful metrics at scale include:

• Deployment frequency and cycle time across teams
• Feature lead time from idea to delivery
• Team and ART predictability (from PI Planning confidence)
• Value Stream KPIs linked to customer satisfaction

Example: An ART uses flow distribution and flow efficiency metrics to identify bottlenecks in the pipeline and realign team capacity.

Sharing

In a scaled Agile system, silos kill flow. Sharing knowledge, tools, feedback, and responsibility is critical for alignment and learning across teams.

SAFe promotes sharing through:

• System Demos that showcase progress across teams
• Communities of Practice (CoPs) for engineering and DevOps knowledge
• Transparent backlogs and shared documentation (e.g., in Confluence or Jira)

Example: A DevOps CoP develops reusable CI/CD templates and publishes onboarding guides for new teams, reducing startup time and duplication of effort.

Why CALMS Matters for Scaled Agile Teams

Too often, large enterprises adopt Agile practices at the team level without addressing the broader system. CALMS helps connect the technical enablers of DevOps with the business agility goals of SAFe. Here’s how it helps:

• Supports enterprise-wide alignment: Culture and sharing ensure that business and technology leaders speak the same language.
• Enables continuous delivery at scale: Automation and measurement keep ARTs synchronized and on track.
• Drives Lean-Agile leadership: Leaders use CALMS as a diagnostic lens for investing in system-level improvements, not just local optimizations.

Final Thoughts

In a scaled Agile environment, success isn’t just about agile practices—it’s about agility across the system. The CALMS Framework provides a simple yet powerful structure for embedding DevOps thinking into your SAFe implementation.

Whether you’re launching your first ART or optimizing across multiple value streams, revisiting each pillar of CALMS can help ensure that your organization is not only building the right thing—but building it the right way.