The agile iteration is outdated, and now the large manufacturers are using the DevOps development model!

Edit Introduction: With the development of the Internet, users' demand for products is getting higher and higher, and more users are pursuing "good -looking" and "good use". The author of this article shared a new development model -the development and development model of the DEVOps development model. Let's take a look together.

Everyone who has learned from the waterfall development, everyone must have heard of agile development. Now I have heard it at work.

Come, let's accept the baptism of knowledge together. Knowledge is power, money, Oli!

Let me tell you two words first, the first sentence is the trend, and the second sentence is the concept.

Trend: At present, many large manufacturers such as Ali, Tencent, Baidu, Toutiao, Meituan and other companies are using DevOps development models.

Concept: DevOps = Developers+Operators, that is, the development team and operation and maintenance team integration.

Ha, just look at the concept? Does it feel that the concept is impossible to understand, and it is impossible to understand in this life.

It doesn't matter, just remember two things here: the first thing is that DevOPS has tied development and operation and maintenance together; the second thing is that DevOps is not a tool or something, but a methodology.

Give me the others, look down, and make sure you explain it.

1. development history

To understand why a new thing appears, such as DevOps, the best way is to understand his past and his history.

As mentioned earlier, DEVOPS is a development model that mentions the words "development model". What can you think of? Is it the development and agile development of waterfalls?

Okay, let's take a look at the evolution of these two development models.

Second, waterfall development

1. Background

In the early days of the Internet, programmers still existed like scientists. At that time, the program of the programmer was also called a laboratory.

At that time, there were not so many netizens. Most of the time, they needed awe with awe.

And the products developed, as long as they can solve their problems, they are scrambling to burn Gao Xiang and send the banner for programmers. Naturally, there are too many requirements for the R & D cycle, and the demand is naturally unchanged.

In this context, the waterfall development model was born, as shown in the figure below:

2. Features

There are three biggest features in the waterfall development model:

The demand is fixed; the development cycle is fixed, it may be 3 months, or it may be 1 year; all aspects of design, development, testing, and operation and maintenance are independent. The current link is completely completed, and the next link will begin to intervene. 3. Disadvantages

The disadvantages of this model, I believe everyone knows that the summary is: demand cannot be verified quickly!

It may have been developed for 1 year, and it has been passed by time, and it is no longer suitable for the market. It is also possible that after half a year, you can find that the things you get and the user's needs are completely the donkey's lips. Come again.

At this time, agile development appeared.

Third, agile development

1. Background

With the development of the times, there are more and more Internet users in the Internet, and the tastes of these netizens are getting more and more.

The products that are made are just "can use", and they can't satisfy their appetite. More netizens are more and more pursuing "good use" and "good -looking".

And these people have become more and more "Chao San Twilight". Maybe I think this is good today. Tomorrow will feel that one is better. The cycle of software development is also more and more compressed.

In the context of the times, there are always a few brains that have evolved quickly, so, the agile development model has appeared on the stage of history:

2. Features

The biggest feature is one word: faster!

Specifically, agile development can find problems faster. The product is delivered to the user faster, and the team can get the user's feedback faster, so as to respond faster.

Another feature is to change development and testing from opposition to the same front.

During the waterfall mode, the test work is to pick up the problem of developing things as much as possible. The agile development has unified the goals of the two in order to be able to develop products faster and better.

From the agile declaration, we can see the true meaning of them:

Twelve agile declarations:

Our primary task is to satisfy customers by delivering software that can be evaluated as soon as possible. Success is willing to accept demand changes, even after development. The agile process can control the change, thereby winning the competitive advantage for customers. Frequent delivery of software, the shorter the delivery interval, the better, from several weeks to several months. During the development of the project, business personnel and developers must work together. Build projects around those who are promoted. Give them the environment and support, and trust them to complete the work. The way to convey the information with the development team and the fastest and effective way to convey information within the development team is a face -to -face conversation. The useful software is the main measurement indicator of progress. The agile process advocates sustainable development. Investors, developers, and users should always maintain a stable development speed. In order to enhance agility, we should continue to pay attention to technical outstanding results and good designs. Simple -the art of maximizing unnecessary work -is essential. The best architecture, needs and design are derived from the self -organization team. The team should regularly reflect on how to become more fighting, and then change and adjust its behavior accordingly. The agile declaration is a very important step to bring peace to the Milky Way and maintain their own balance. For a long time, compared to the process and mechanization of mechanization before, this is the first way to connect different key projects based on culture and "humanity".

People began to communicate with each other, conduct basic meetings, and began to communicate opinions and opinions.

They began to realize that they had a lot of things in common than they expected. Customers began to become one of them, and they were no longer just smashing money into the project and then began to ask God to worship and pray for everything.

3) Disadvantages

Although agile development has greatly improved the efficiency of software development and the speed of version update, its effect is limited to development links. We found that the operation and maintenance side, a very backward manual deployment launch, has become a new bottleneck.

Operating and maintenance engineers have completely different thinking logic with developing engineers. The motto of the operation and maintenance team is very simple, that is, "stable and overwhelming everything." The core appeal of operation and maintenance is that there is no problem.

Under what circumstances is the easiest problem? When changing changes, the easiest problem. Therefore, operation and maintenance is very exclusive to "change".

As a result, the contradiction broke out between the two.

At this time, the mysterious protagonist DevOps appeared grandly.

3. DevOps development

1. Background

In today's era, Internet users in the Internet have increased by massive volume. In this context, many Internet manufacturers have been born, as well as a number of phenomenal products, such as WeChat, Taobao, Douyin, etc. Essence

Quickly iterative products, quickly occupying the market, and quickly occupying users' minds have become the goal of various Internet companies. At this time, higher requirements have been put on product development. Continuous monitoring, new versions can be carried out every day every day.

The contradiction between the development team and operation and maintenance is the time to alleviate it. How can I relieve it? Then get them the same front line:

2. Features

In this model, it will "faster" and improve a level: users can get a part of the final product or service for the actual experience very early, so that the hairpin can be passed back to the demand management team and the product research and development team as soon as possible Essence

And everything that needs to be attributed to: DEVOPS has pulled development, testing, and operation and maintenance to the same front!

Agile has its own declaration, and DevOPS also has its own list:

DEVOPS list:

There are no obstacles between the development team and the operation and maintenance team, both of which are part of the unified DevOPS process. The work from one team to another can get high -quality verification. There is no accumulation at work, and all bottlenecks have been dealt with. The development team does not occupy the operation and maintenance team, because deployment and maintenance are in the same time box. The development team will not deploy the code after 5 pm on Friday, and the rest of the operation and maintenance team will work overtime to wipe them on the weekend. The development environment is standardized, and operation and maintenance personnel can easily expand it and deploy it. The development team can find a suitable way to deliver the new version, and the operation and maintenance team can easily deploy. The communication lines between each team are clear. All team members have time to test and practice to improve the system. Routine introduction (or simulation) defects come to the system and get handled. Each experience of learning should be documentary and shared with relevant personnel. The accident handling becomes part of the daily work, and the processing method is known. Generally speaking, under the circumstances of such high labor costs, such competition in the market, and frequent user demand, DevOps is a way that a large factory must choose.

Fourth, conclusion

Well, the above is what I summarized for everyone today. You ask me what is the use of these?

As the most cutting -edge product manager in the Internet industry, you said that you should understand these stuff; then as both face value and IQ, and then look forward to the world's peaceful code farmers, there is such an opportunity to place it in front of you in front of youShouldn't you cherish it?#Columnist#

Xiaozhuang classmate; public account: Xiaozhuang classmate product notes, everyone is a product manager columnist.Internet veterans, column authors of major platforms.

This article was originally published in everyone's product manager.Reprinting is prohibited without permission.

The question map is from UNSPLASH, based on the CC0 protocol.

- END -