The reason why the project becomes agile is that the customer's thinking is not agile? Four types of project management

Before entering the industry, I often heard about "waterfall development" and "agile development". What are you talking about? In fact, this is the concept of project management in programmer companies. Let's take a look at the types of project management in "waterfall development" and "agile development".

 

A predictive

The result is clear and the process is clear.

For example, when building a building, the sales department will be able to draw you what the future will look like before the ground is broken (the result is clear), and every day of construction, you know what it will look like today, tomorrow, yesterday, and the day before yesterday (the process is clear) .

Waterfall development in the IT industry is this category.

2.3 Iterative and Incremental

As pictured~

 It can be understood that incremental development is to divide a requirement into several parts and complete it sequentially, while iterative development is to gradually clarify a requirement and strive to complete it every time.

Four agile or adaptable

The type of project that needs to adjust the project schedule at any time according to demand and other factors.

For example, the emergence of demand library. To put it simply, when users think of any requirements, they write them into the "requirements library". And programmers look at the requirements library written last weekend, pick a few requirements that can be realized and are relatively important, put them into this week's plan, and start typing code.

Users may think of other requirements at any time, and then continue to write in the requirements library; programmers also continue to summarize and select the requirements library to be implemented in the next cycle at the end of the previous work cycle.

 Simple comparison of four projects

Text comparison of the four items

 

Pictures of the four projects

Classify according to requirements and whether the technical realization is clear

① Predictive type

If the requirements are clear and the technology implementation is simple and feasible, then use predictive development. For example, the example of building a building mentioned earlier. (The technology is feasible, which means that the technical standards in civil engineering are very clear, and the process is very standardized)

②Iterative type

The requirements are clear, but the technology is cumbersome to implement, so we should use iterative thinking to think about this kind of project. For example, unmanned driving has been researched at home and abroad for more than 20 or 30 years and even until the beginning of the last century. The demand is very clear: it is to drive a car without a human being. But technical implementation has always been a problem. Until the recent explosive growth of deep learning technology, the hope of the success of autonomous driving has become great.

③Incremental type

There is no problem with technical implementation, but the requirements are very vague. At this time, part of it is explained clearly and part of it is completed. This kind of development is incremental development. Many program projects are developed in this way.

④ Don't touch the hard nails of chaos!

The requirements and technologies are not clear. Such a project is too difficult to control in project management. As a general project manager, I still take a detour. If you are very self-motivated, then continue to delve into the field of project management, I believe one day you can.

⑤Agility

In addition, requirements and technical implementation are partly difficult, but generally acceptable, use agile development. If you think about a part clearly, if you can realize a part, you can complete a part and modify the previous part. Through reasonable management and control, realize the landing of the project.

Are clients of agile projects quick-thinking?

After reading the above article, the customers of agile development services may not be able to explain the specific needs of the project themselves. He can think quickly and quickly think about the general requirements of the project, but there may be a period of time when he is troubled by the details and other functions of the project.

Guess you like

Origin blog.csdn.net/m0_46948660/article/details/129915528