![What are better excuses to talk to classmates or others besides asking "do you know what the teacher is saying?" [closed]](https://cdn.sstatic.net/Sites/interpersonal/Img/apple-touch-icon@2.png?v=17e836faa592)
DevOps is a culture, not a role!
Originally written at pooyan.info Who is the author? Check out my profile on LinkedIn. DevOps is not a “role” DevOps was introduced: to change the culture (which also needed a change in traditional management thinking and habits) to empower teams to continuously grow with more autonomy and less dependencies (which needs more trust, governance, and better risk management) to continuously experiment, analyze the risk, learn, and adapt to changes It was an attempt to change management style, but... Instead, again, we got "isolated DevOps/Ops" teams and tens of thousands of meetings under different names. Remember... DevOps != an isolated separate team of DevOps engineers (ops simply renamed to DevOps) + Scrum/SAFe DevOps != CI/CD pipeline DevOps is... DevOps is a culture and a mindset DevOps is a way of working DevOps is a way of thinking DevOps is a way of continuous improvement If you liked the article and want to keep me motivated to provide more content, you can share this article with your friends and colleagues and follow me here on Medium or LinkedIn. Copyright & Disclaimer All content provided on this article is for informational and educational purposes only. The author makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. All the content is copyrighted, except the assets and content I have referenced to other people's work, and may not be reproduced on other websites, blogs, or social media. You are not allowed to reproduce, summarize to create derivative work, or use any content from this website under your name. This includes creating a similar article or summary based on AI/GenAI. For educational purposes, you may refer to parts of the content, and only refer, but you must provide a link back to the original article on this website. This is allowed only if your content is less than 10% similar to the original article. While every care has been taken to ensure the accuracy of the content of this website, I make no representation as to the accuracy, correctness, or fitness for any purpose of the site content, nor do I accept any liability for loss or damage (including consequential loss or damage), however, caused, which may be incurred by any person or organization from reliance on or use of information on this site. The contents of this article should not be construed as legal advice. Opinions are my own and not the views of my employer. English is not my mother-tongue language, so even though I try my best to express myself correctly, there might be a chance of miscommunication. Links or references to other websites, including the use of information from 3rd-parties, are provided for the benefit of people who use this website. I am not responsible for the accuracy of the content on the websites that I have put a link to and I do not endorse any of those organizations or their contents. If you have any queries or if you believe any information on this article is inaccurate, or if you think any of the assets used in this article are in violation of copyright, please contact me and let me know.
Originally written at pooyan.info
Who is the author? Check out my profile on LinkedIn.
DevOps is not a “role”
DevOps was introduced:
- to change the culture (which also needed a change in traditional management thinking and habits)
- to empower teams to continuously grow with more autonomy and less dependencies (which needs more trust, governance, and better risk management)
- to continuously experiment, analyze the risk, learn, and adapt to changes
It was an attempt to change management style, but... Instead, again, we got "isolated DevOps/Ops" teams and tens of thousands of meetings under different names.
Remember...
DevOps != an isolated separate team of DevOps engineers (ops simply renamed to DevOps) + Scrum/SAFe
DevOps != CI/CD pipeline
DevOps is...
DevOps is a culture and a mindset
DevOps is a way of working
DevOps is a way of thinking
DevOps is a way of continuous improvement
If you liked the article and want to keep me motivated to provide more content, you can share this article with your friends and colleagues and follow me here on Medium or LinkedIn.
Copyright & Disclaimer
- All content provided on this article is for informational and educational purposes only. The author makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site.
- All the content is copyrighted, except the assets and content I have referenced to other people's work, and may not be reproduced on other websites, blogs, or social media. You are not allowed to reproduce, summarize to create derivative work, or use any content from this website under your name. This includes creating a similar article or summary based on AI/GenAI. For educational purposes, you may refer to parts of the content, and only refer, but you must provide a link back to the original article on this website. This is allowed only if your content is less than 10% similar to the original article.
- While every care has been taken to ensure the accuracy of the content of this website, I make no representation as to the accuracy, correctness, or fitness for any purpose of the site content, nor do I accept any liability for loss or damage (including consequential loss or damage), however, caused, which may be incurred by any person or organization from reliance on or use of information on this site.
- The contents of this article should not be construed as legal advice.
- Opinions are my own and not the views of my employer.
- English is not my mother-tongue language, so even though I try my best to express myself correctly, there might be a chance of miscommunication.
- Links or references to other websites, including the use of information from 3rd-parties, are provided for the benefit of people who use this website. I am not responsible for the accuracy of the content on the websites that I have put a link to and I do not endorse any of those organizations or their contents.
- If you have any queries or if you believe any information on this article is inaccurate, or if you think any of the assets used in this article are in violation of copyright, please contact me and let me know.
