DevOps team structures

DevOps has never really excited me and I never understood why until I read about DevOps team structures – https://web.devopstopologies.com/

The article suggests 7 bad practices or ‘anti-types:

  1. Dev and Ops Silos
  2. DevOps Team Silo
  3. Dev doesn’t need Ops
  4. DevOps as tools team
  5. Rebranded administrators
  6. Ops embedded in dev team
  7. Dev and DBA silos

It then looks at some team structures that can be made to work

  1. Dev and Ops collaboration
  2. Fully Shared Ops responsibilities
  3. Ops as Infrastructure as a Service
  4. DevOps as external service
  5. DevOps team with expiry date
  6. DevOps evangelist team
  7. Site Reliability Engineering team
  8. Container driven collaboration
  9. Dev and DBA collaboration

One thing that’s often not explicitly mentioned when discussing DevOps is the need for whatever teams, and individuals, to communicate. This is often anathema in my experience and why a DevOps type approach is so badly needed.

As to why DevOps hasn’t excited me – the article made me realise I’d spent a good part of my working life moving between Dev & Ops and often occupying the middle, grey area that DevOps makes its own. Its what I’ve been doing for a long time mainly without the tools we have today and not viewing it as anything special – just getting the job done.

Advertisements
This entry was posted in DevOps. Bookmark the permalink.

One Response to DevOps team structures

  1. cavallogolooso says:

    😀

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s