Right now as I take the sip of my tea, I recall my early career when I was a trainee and use to standby observing people at work during production breakdowns and major releases. Those were really fun days, where my goal was to learn as much I can. The discussions ranging from What I should do in life to what I have learned today used to make most of the mental maps. Back in those days, I learned it’s your contribution that matters not how good you are in keeping your knowledge and assets to yourself. Keeping a fine boundary of not letting others know what you know was ‘The Great Wall’ between time to market and stability.

DevOps is a combination of Development and Operations. Making best out of both the teams; — that are harnessing the skills for faster time to market and focus on stability at the same time. The Accelerate State of DevOps Report (2019) shows that companies employing DevOps have gained significantly.

Comparison among the elite group against the low performers shows that the elite group deployed 208 times more frequently, 106 times faster lead time measuring from committing to deploy, 2604 times faster in recovering from incidents and 7 times less like to have unsuccessful change. [2]

The Scaled Agile Framework® (SAFe®) recommends the CALMR approach to harness the potential of DevOps [1, 5]. Let’s see what CALMR stands for :

Culture of shared responsibility

SAFe emphasizes the importance of building a culture that fosters shared responsibility for developing the code, deploying, and ensuring its stable operation.

Automation of Continuous delivery pipeline

Optimize the ways of working and enable automation in the continuous delivery pipeline along with other tools within the IT Service Management can reduce the chances of error while enhancing the outcome.

Lean flow accelerates delivery

Foster understanding that small batch size enables faster delivery, limiting the work in provides with transparency, visibility will bring the culture to focus on the work instead of administration around the value delivery.

Measurement of flow, quality, and value

SAFe mentions measuring the flow through the pipeline. How faster we are delivering and converting the value from concept(customer demand) to cash(Value shipped to customer).

Recovery reduces risk and preserves value

It is a fact that when we deploy new features or services, there is a probability of failures. What matters is how well the team is prepared for fixing and moving ahead as well as rolling it back. The team should not only have a roll-back plan but also should test the roll-back plan from time to time.

Where to start DevOps?

DevOps is not just about the tools. For a reason, SAFe [1] refers to it as “a mindset, a culture, and a set of technical practices”. Starting with DevOps can be challenging and the best start is to prepare for the cultural shift. The next step can be as follows [3]:

  • Create a CI/CD Pipeline (continuous integration, continuous delivery)
  • Create an environment for continuous testing
  • Automate wherever possible from testing to deployment
  • Use Release on Demand techniques- Blue/Green, toggle, etc.
  • Enable Metrics to measure performance. The following image is generated by answering to parameters in SAFe DevOps Health Radar [1].

Measure your DevOps progress right away using the free SAFe® DevOps Health Radar assessment available here.


  1. SAFe DevOps, Scaled Agile, Inc.
  2. “The State of DevOps Report 2019 Is Out.” DevOps.Com, 4 Sept. 2019,
  3. Bertram, Adam. “6 Steps to DevOps Success.” CIO, 18 Oct. 2017,
  4. SAFe DevOps Practice Domains, Scaled Agile, Inc.
  5. SAFe CALMR, Scaled Agile, Inc.

Author: Dhirendra Mishra, Agile Coach and SAFe Trainer, DailyAgile

Related DailyAgile Training Course: SAFe DevOps Practitioner (SDP) Certification Training

This website uses cookies and asks your personal data to enhance your browsing experience.