Skip to main content

DevOps Enterprise Culture Thoughts

How do you get DevOps going in an Enterprise?  The same way you eat an elephant but you have to keep reminding your self of two things:

1.  I am hungry.
2.  I may never finish eating.

You are hungry or you would not be eating.  DevOps passion is something you have to be starving to embark on.  If you don't really want to own the message, the transformation or believe in it, just stop and do little things as you can.   If you want to own it and you know you know the org will not change, even a little, then leave.  The market is too good for people that want to do DevOps to sit and starve with an Org that is dying.

The DevOps journey is never ending and you have to keep reminding yourself of that.  You will have plenty of people that get in your way. Tools will sometimes crush your spirit.  Process will sometimes seem crazy.  You just have to remember, you may never finish evangelizing DevOps.  

I can't stress enough, if you company is not already doing DevOps, be ready for a long battle.  If you are not doing it now, that means your leadership is not ready for it.  There is enough information out there in IT to know about DevOps and the benefits for a good IT leader to not have already started heading that way.

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

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

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