Shulou(Shulou.com)06/01 Report--

In this article, the editor introduces in detail what the DevOps maturity model of a large organization is like, with detailed content, clear steps and proper handling of details. I hope that this article "what the DevOps maturity model of a large organization is like" can help you solve your doubts.

DevOps is a complete workflow for IT operation and maintenance, which optimizes all aspects of program development, testing, system operation and maintenance based on IT automation, continuous integration (CI) and continuous deployment (CD).

The transformation of DevOps is a challenging task. It is not a simple tool or platform to improve the use, operation and maintenance capabilities. Especially in large and medium-sized organizations, it involves a series of organizational problems.

However, the traditional DevOps maturity model is too torn and dispersed to be suitable for large organizations. The DevOps maturity models of DevOps vendors and cloud vendors focus too much on how to sell cloud infrastructure, which does not help enterprises to collaborate efficiently.

To this end, I decided to design an open source DevOps capability maturity model for large organizations on the basis of Ledge. It is an abstract maturity model based on a series of R & D effectiveness models we have refined.

When designing and dividing, we consider two dimensions:

Scale. For medium and large organizations, the design of DevOps model should focus on four large-scale factors: flow / standardization, instrumentation / platform. That is, select the appropriate pilot team, build the DevOps capability of the organization, and then promote it on a large scale. Organizational collaboration. There are already a series of DevOps-related tools / platforms in medium and large organizations, such as Kanban, pipelining, and so on. These tools / platforms need to be adapted to ensure better coordination so that they respond more quickly to business changes. Therefore, in this large-scale DevOps design and implementation, we summed up the four core competencies of DevOps, also known as the four cornerstones.

DevOps Radar

Among them, efficient collaboration is the most important part of the four cornerstones, the essence of DevOps.

Efficient collaboration. Collaboration refers to the previous collaboration between people, that is, business and technology, technology and testing, testing and operation and maintenance, and so on. In terms of standardization, we focus on: collaborative design to minimize waste from the process; organizational / team governance to optimize the team and organizational structure. On the platform, we focus on: requirements management, ensuring the conceptual integrity of the requirements process, such as analysis, split, collaboration; indexing improvement; that is, the collaborative platform as a display platform for measurement indicators for continuous improvement, such as technical debt.

Continuous delivery. Continuous delivery refers to the ability to release all types of changes quickly, securely, and sustainably as needed. In terms of standardization, we focus on: service-oriented architecture, which is similar to micro-service architecture and service-oriented architecture, so that the technical architecture can respond to business changes quickly; version management, that is, standardize the version from the source of the source, through branch management, semantic version and so on. In terms of tools, we focus on flexible change, that is, managing changes and artifacts through the platform, and continuous deployment, which is continuous integration and deployment associated with change.

Quality assurance. Quality assurance refers to providing high-quality software products for end users. In standardization, we focus on: testing strategy, that is, paired quality left shift design test life cycle, design test hierarchical model for indexing guidance, test methods, define the type, timing and exit standards of automated testing and manual testing. In the platform, we focus on: test management, such as use case management and design, test data management; quality and safety, is aimed at code, environment, etc., automatic quality and security-related scanning.

Environmental support. Environmental support refers to the infrastructure and operation and maintenance system needed to support the system. In standardization, we focus on: configuration management, that is, infrastructure coding, the corresponding baseline configuration management, application configuration, etc.; resource management, that is, the management of the environment, as well as the management of resources and environment needed by each link. On the platform, we focus on deployment management, that is, the management of the release environment, as well as the management of advanced deployment methods such as grayscale publishing, and automation of operation and maintenance, automated monitoring and warning on operation and maintenance. and support better flexible release, such as high availability.

After planning the DevOps subdomain, we can subdivide the subdomain and the corresponding details according to the size of the organization. For example, in collaborative design, process collaboration and role collaboration can be further designed. As shown in the following figure:

DevOps model of large organization

Considering that this is a maturity model, we also need to define the level of maturity. Generally speaking, a maturity model should range from 1 to 5, or 0 to 4.

For large-scale organizations, we only need 4 levels, that is, there are only 2-5 levels. From the process standardization and platform, we have eliminated the existence of level 1, they are non-compliant. At the same time, in terms of standardization and platform, in fact, we don't have level 5 because they are too flexible and advanced.

So, it only needs a three-level model:

Level 2, normalization. From the generation of the original requirements to the launch of the requirements, all follow the scale standards defined within the organization. The process of requirements collaboration is transparent, the process is clear, and the flow is automated; in continuous delivery, the practice defined by the organization is adopted, such as semantic version, credible product source and output, etc.; in terms of quality, the testing strategy is designed according to the model defined by the organization; in the environment, the platform can support the design needed for standardization.

Level 3, platform standardization and automation. Standardize the standardized content one by one on the platform, that is, define a variety of technical practices, and you can only choose one of two, or one of three. The four cornerstones are all automated through this series of standards. The only debatable point is that in terms of continuous delivery, we need a loosely coupled architecture to support the rapid delivery of a single team, such as micro-service architecture, plug-in architecture, etc.

Level 4, indicator driven and automatic improvement. Establish a series of measurement models to comprehensively measure the software development process. At the same time, the team and platform optimize the system and platform according to these definitions. For example, in the environmental support, the real-time monitoring of the application status can be realized automatically and flexibly.

For level 5, it varies slightly depending on the organization. As we define it:

Level 5, cloud R & D architecture. Build infrastructure architecture based on cloud development, such as cloud R & D architecture, Serverless, Typeflow, Darklang, etc., to achieve a high degree of decoupling of infrastructure automation and architecture. In terms of quality, it monitors the runtime, realizes automatic test writing, static analysis of the code, and lean testing; in collaboration, through the construction of domain-specific languages, the requirements generate the code skeleton; in the environment, automatically achieve features such as grayscale release.

After reading this, the article "what is the DevOps maturity model for large organizations" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it yourself. If you want to know more about related articles, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.