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

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