Skip to main content

DevOps Team Structure for Enterprise

http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/

I found this blog to be fascinating and a very good representations of different DevOps model.  First off, a full stacked team that builds, releases and operates its own service is the best hands down.  The problem is very few enterprises are doing this.  So the question is what do you do instead.  My opinion is DevOps as a service is the next best model for enterprises. Here is why:

Teams in an enterprise either don't know how or aren't allowed time to do automation.  This means a DevOps as a service team can work with the teams to do all the large up front building and then, teach the teams to own it from there. You have to let the teams own it because pipelines are continuously changing and maturing.  The IaC solutions should be changing and adapting to the needs of dev and ops.  The DevOps team can't stay on one team for too long or you will miss more and more opportunities for improvement across the enterprise.

An option to make sure the "DevOps" keeps going on the team you just helped is to leave an automation engineer with the team or area to mature their pipelines and IaC but working with the team as their goals are alligned.  DevOps is evolving frequently so find a way to keep the engineer engaged with our DevOps service so new ideas and solutions are spread through the enterprise.



Comments

Popular posts from this blog

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.  

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...

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...