Skip to main content

Why DevOps is not a team.

I really want people to stop talking about DevOps but I really want people to keep asking questions about DevOps.   This does not make sense right?

The problem is DevOps is getting a bad name in lots of places because people don't understand it.  DevOps is not CI, CD, Infra as Code, Cloud, Agile, Lean.....  DevOps is a culture of continuous improvement and scalable IT.

We really should talk about DevOps from a leadership level and talk about automation separately.  Leaders need to remove obstacles, manual tasks, and improve processes all while demonstrating people and teams working together.  These things will naturally allow people to innovate and grow towards automation.

You can do automation anywhere and you should do automation.  A company could be a large enterprise with silos of people that don't trust each other with competing goals but even those can do automation like CI and Chef.  They likely are doing it at a silo level and everyone doing it differently.

This is really why there should not be a DevOps team.  You can start an automation team but not a DevOps team.  If a company has a posting for a DevOps manager or DevOps engineer, their culture might be a long way away from a DevOps culture.  Just be careful.


Comments

Popular posts from this blog

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  

How AI is Transforming DevSecOps: A New Era of Secure, Agile Software Delivery

 As software delivery accelerates and attack surfaces grow, traditional DevSecOps practices are being pushed to their limits. The integration of artificial intelligence (AI) into DevSecOps workflows is not just a trend—it’s a strategic imperative. AI is driving a seismic shift in how we manage code quality, automate security, respond to threats, and enable secure innovation at scale. In this post, we’ll explore the key ways AI is improving DevSecOps and why forward-thinking organizations are embedding it deeply into their pipelines. 1. Proactive Threat Detection and Response In modern CI/CD pipelines, code moves fast—sometimes too fast for human eyes to catch every vulnerability or misconfiguration. AI helps shift security left and right by: Analyzing code and dependencies with natural language processing and ML to detect hidden vulnerabilities, insecure APIs, or anomalous changes during commits. Real-time anomaly detection in production environments using AI-powered o...