Just to summarize once again, DevOps is a methodology interacting between Development and Operations. It is all about improving the joint effort between functions of Development and Operations. The DevOps methodology in a software world is often also referred as a methodology that overcomes the gap between Agile software development and operations, as it enables a fluent process for Continuous Development and Continuous Integration.
It’s also very important to highlight that usage of DevOps methodology reduces the stress in communication, helps to improve the communication between teams, collaboration between all participants and integration between developers and operations teams.
In delivering valuable software to customers, too often development and operations are in conflict with each other. When Development implement the changes, such as new features, bugs or fixes, they want to quickly roll out this changes to production. But once when software is already delivered, the operations departments wants to avoid to make the changes on the software. Here is where DevOps help to overcome the gap between both teams.
Initially, there was ‘Agile Development’, when agility aspect was applied to operations it became ‘Agile Administration’, thus DevOps was formed. Here is a must read article by Visual Studio Magzine – Taking DevOps to the next level: It’s all about continuous delivery.
In this post I’m going to describe a bit deeper view about Three important stages of Conversation, which are People, Process and Products.
The Three Stage Conversation – People, Process, Products
DevOps is the correlation of people, process, and products to enable continuous delivery of value to end users. The outcomes are tightly connected to ability for frequent releases and at the same time to keep the same level of quality.
Thinking of DevOps at a really high level, it’s first all about people. DevOps business, everybody that is involved, that needs to deliver value to the business is working very tightly together on a common goal of adding value to the customer. The latest study by Gartner, which involved 367 IT and leading companies, from which 113 companies were using DevOps, showed that people issue is the biggest concern in the share of interviewed participants. This study also revealed that the share of process and IT issues is on less lower level, than people issue. So we can think that having highly motivated people with good collaboration between teams is very important.
Next – DevOps is about process because even if you have those people that are good working together but then you have got business process in a way that is really blocking innovation, for instance long chain advisory boards before they can do something or they are restricted to doing things in a certain way that really impedes that kind of innovation. The process of designing, building and testing software should be well presented to each individual team member, to make every team member aware of all parts of the the development process. The implementation of DevOps process into company is a hard work, as it completely changes the company’s structure as a whole.
That’s part of a bigger picture of DevOps. Enabling efficient flow of people working together and not having processes get in the way but having processes and practices that help enable that value deliver to your customers.
DevOps is not a tool or product. You can’t buy the DevOps, as DevOps is not a software, tool, process, company or person, it’s a methodology used especially by IT professionals. But there are products, tools and services that really help enable different DevOps practices and different teams can use to make things easier. From very high level those tools are Microsoft Azure, which is offering a lot of different products and services, such as Microsoft Azure Stack and Microsoft Azure. Besides Microsoft Azure there are also other products related to DevOps practices, such as Visual Studio Team Services (VSTS) and Team Foundation Server (TFS).
So, DevOps is working like a mediator between Development and Operations and is helping businesses in a tremendous way that need continuous change to thrive in the competitive market. DevOps is not a software, tool, person or process, it’s way much more than that. It is a philosophy, which is changing the work practices in IT in the way which requires tight collaboration between everyone involved to enable continuous delivery to the end users.
To keep yourself aware of the latest information, you can also go through the 10 Must Read DevOps Articles to stay in the know for 2016:
- A Quick Refresher: DevOps by David Auslander
- From Teams to Tribes: Creating a one-team culture in DevOps by Em Campbell-Pretty
- The DevOps Dilemma by Martin Cooper
- How Can DevOps Accelerate Innovation? by Dan Kobialka
- DevOps Tips: IT Managers Reveal How to Get the Best From DevOps by Matthew Finnegan
- High Performance Teams in DevOps by Kris Bliesner
- 7 Signs You’re Doing DevOps Wrong by Adam Bertram
- The State of DevOps in 2016 by Ben Rossi
- Piecing Together the Elements of DevOps by Aruna Ravichandran
- Setting a DevOps Mindset for 2016 by Derek Langone