Breaking Down the 7 Cs of DevOps

Today’s digital-first economy does not afford organizations the luxury of taking their time with product services and releases.

New technologies are arriving almost daily, customer demands are becoming more steadfast, and the average time-to-market is shrinking as competitors execute faster than ever.

However, one hard truth remains: speed is dangerous without structure! Expanding IT systems and technologies without a stable operational platform opens organizations up to instability in Cyberspace, potential security liabilities, and costs that quickly get out of control.

FAQs

What aspect of the 7 Cs is the most important in DevOps?

Culture! Without it, the tools and processes won’t have a lasting impact.

Can small teams effectively implement all 7 Cs?

Definitely. Small teams are usually the first to implement the 7 Cs, simply due to being nimbler and with less bureaucracy to deal with.

How do the 7 Cs differ from the DevOps CALMS framework?

CALMS stands for Culture, Automation, Lean, Measurement, and Sharing. The 7 Cs places more of an emphasis on delivery flow and operational excellence.

What tools can assist us in applying the 7 Cs?

Typical tools are Jenkins, GitLab CI/CD, Selenium, Prometheus, Grafana, Jira, and Slack etc., but the teams will need to find what works best.