What to do with DevOps transformation
DevOps is everywhere, everyone is talking and doing. There are many cases and stories of DevOps transformations, some of which have succeeded, but perhaps more have failed (although you didn't have a chance to hear them come out and share). Different organizations face different situations and environments, and it is difficult to simply replicate the success of others.
An example that I often like to give is that there are different ways to learn DevOps, just like when humans learn to fly there are birds flying and aerodynamics. The human dream of flying began in an ancient and distant era, but the real flying practice originated from imitating bird flight, that is, attaching a pair of wings to oneself and learning the flapping movements of birds to fly, but a lot of long-term practice has proved that this is the case. Attempts have been unsuccessful. But there is another faction. British scientists proposed that artificial aircraft should solve the problems of propulsion and lift, and it is necessary to enhance the basic understanding of the theoretical system of aerodynamics, which makes many people give up simply imitating the flight of birds and gradually accept And practice the design ideas of fixed-wing aircraft, and finally invented a fully controlled, sustainable flight manned aircraft by the Wright brothers.
The same is true for the practice and transformation of DevOps. It is difficult for us to copy the success of other organizations. Instead, we should deeply understand the principles, principles and practices behind it and start from the right direction. The main content of this article comes from Jez Humble's speech "Leading a DevOps Transformation" at the Devon Summit, focusing on five misunderstandings, five practices of DevOps transformation, and specific suggestions for transformation implementation. Because of the length, I will share it with you through two articles. In addition, like the previous articles, I will expand the content appropriately based on my experience and understanding, not just limited to the content of the speech. The core is to help you avoid detours, avoid pitfalls, and make your way to DevOps success more smoothly. .
Another introduction to Jez Humble, a recognized world-class leader in DevOps, a highly influential software researcher and an award-winning author. His co-authored book "Continuous Delivery" (Continuous Delivery) won the Jot Award and is a must-read for learning DevOps. Jez's other bestsellers include "LeanEnterprise", and DevOps Handbook, the Chinese translation of "DevOps Practice Guide" will be released at DevOpsDays Beijing on May 5th, and the great god Jez Humble will also come to China to talk about DevOps face to face with everyone !
How DevOps can help us
The problems with traditional software delivery methods are well known, such as long lead times, poor resilience, and inefficient value delivery. All, many organizations have undergone agile transformation, but the journey to agile transformation may not have been smooth sailing. The engineering department, represented by development, operates in an agile manner, shifting from waterfall to Scrum for rapid iteration, and introducing TDD, doing a good job of decoupling the architecture, and working very happily.
But other parts of the organization may not think so. For example, the operation and maintenance team used to do a few releases a year, but now there are online packages thrown over at any time, and they need to prepare for release at any time. This is really scary. When faced with such a problem, the natural response is to establish a barrier, such as a "change management process", whose job is to limit change.
The emergence of DevOps is to solve such problems. Many people may have different understandings of DevOps, and there may not be a unified definition. But that's okay, we can think from the origins of DevOps. The DevOps movement started in the community, with some people trying to solve some problems that have never been solved: how to build large-scale, distributed, reliable, and secure systems that can be kept safe and secure under continuous and rapid changes. reliable.
In the past five years, through the research of many high-performance enterprises, it can be found that there are many benefits obtained by investing in DevOps practices. The first is that software delivery will have a significant impact on business development. High-performance enterprises have twice as many The probability of other companies reaching their business goals such as profit margin, market share, and production efficiency.
Next, we analyze IT performance from a statistical point of view, here we design two categories and four indicators. They are metrics that measure throughput (deployment frequency, change lead time), and metrics that measure stability (MTTR, change failure rate). These data come from the annual DevOps status survey report. I have also interpreted and shared online and offline many times last year. I will not explain it here. But it is worth emphasizing again that from the statistical results, high-performance enterprises can achieve both throughput and stability , rather than sacrificing quality for efficiency in the traditional sense, or sacrificing efficiency for quality.
Facebook used to have a motto "Move fast and break things", which meant that companies should move fast and break things. But I think it can be changed to " Move fast and don't break things ", that is, fast delivery while ensuring quality and security, which is what DevOps can give us.
DevOpsDays Conference Beijing Station Registration Channel
On May 5, 2018, have a face-to-face chat with the great god Jez Humble about DevOps!
It is a rare opportunity to meet and communicate with the Great God, hurry up to scan the code to register!
