Skip to main content

DevOps is a Metaphor

It finally dawned on me why people struggle with defining DevOps.  If someone is truly trying to define DevOps, they will start to realize it is different in different context.  I have tried many times and each time I slant my response to the situation or what is important to me at the time.  You have seen DevSecOps, DevTestOps, DevOpsSomething and so on.  This is because people are trying to use the fundamental point of DevOps to describe more examples of it.  This made me realize that if you view DevOps as a culture, you will start using it to define more than just "dev" and "ops" because it is a metaphor.

DevOps is really a metaphor for two opposing entities that clash when required to work together because they have different goals and motivators.  Dev wants to change and Ops wants stability.  Apply the same concept to other challenges like Dev/Test, ITIL/Agile, Offense/Defense, Politics/Religion, Blacks/Whites, Husband/Wife, InSource/OutSource and many more.  Think about the core of DevOps: Transparency, Empathy, Lean Thinking, Blameless, Shared Goals, and define interactions through code. If you apply all of these concepts to each of these items, you can see how they can improve and be successful together.  You can apply this to every interaction.  The successful IT professionals are able to apply DevOps in everything they do because they get it, DevOps is a metaphor for a better way of treating humans.

PS.  You might be thinking, how can you define interactions through code between a husband and wife.  Well realistically you can't but think how much better it would be if you had every conversation, agreement or decision in a code repository to reference every time there was a dispute in a marriage.  Yes, momma would still be right but you could fork the repo when she changes her mind. :)

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