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

Post a Comment

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.  
Post a Comment
Read more

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/
3 comments
Read more

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...
3 comments
Read more