Practice of project managers (1)-modeling for software development

# It is necessary to become a project manager. If you want to be quick but don't want to pay, it is better to worship Buddha.

# This series of articles is written to people who want to become project managers but are willing to work hard.

When we develop software, many people know that we need to model the target software to meet the development requirements.

It is also a requirement to become a project manager. In order to further develop the key point, modeling is also required-modeling for the software development itself.

Project managers are more similar to Shuai Cai, but individual items may not be the best, but they must make overall planning during software development.

The premise of overall planning is that you have formed your own ideas and ideas for software development. Here, the "road" is your own software development model.

Let's start with the simplest.

The basic input of software projects is: people, requirements, and tools.

One of them is a team member. The requirement is the original requirement, and the tool is something like Visual Studio.

These three are not unchangeable, but in the context of limited time and space, the choice is limited, so they are considered as an input.

The main methods associated with software building include management, process, estimation, development model (waterfall, iteration), demand development, design coding, and testing.

The output of software projects is: software products. Software products can be measured in both functional and non-functional quality dimensions.

The process of switching from input to output is affected by three factors:

Commercial factors, project political factors, and technical factors.

Commercial factors are related to making money. For example, a requirement may be well done, but it is eventually canceled because it is ready to be released in the next version.

Project politics refers to things related to human feelings. For example, A and B may be a bit personal and can't cooperate, but the project needs both of them at the same time.

Technical factors refer to the inherent rationality of each link. For example, the design should comply with the principles of high cohesion and low coupling.

Every dimension alone is not enough to guarantee the success of the project. It is just a chip.

The more chips you have in your hands, the more your balance is leaning towards the victory end. After you tilt to a certain extent, the ending will appear, or you will win or lose.

The above factors can be further subdivided, for example, management can also be divided into: People, management, and management.

The management personnel are the most important, so the so-called management project is the first management personnel. The management personnel are not good, and others are nonsense.

If no one in the team has a basic sense of responsibility, the project will fail even if PMBOK and cmme are moved back.

This is not mentioned this time.

To become a project manager, you must first create a model that covers various fields of software development.

It also provides a self-defined role that locates each role in the model.

I believe that project managers only need to drink coffee every day and do not need to understand anything. It is as dangerous as they believe that Zhao Kuo can fight well.

The above model is far from perfect, but the story has been a long time. Therefore, it takes some patience and accumulation to cultivate the model.

At present, it seems that the software development association elements are not considered as a whole to help everyone form their own "Tao" book.

More books emphasize a single dimension: Object-oriented, programming languages, design patterns, agility, and various development platforms.

In fact, in front of the project, all these are just chips. without violating the law and social morality, the project should be "unscrupulous ".

However, only by forming their own channels can these means be well controlled. Once these means are in turn controlled by these things, it is easy to be narrow.

Certificate ------------------------------------------------------------------------------------------------------------------------------------

Ideal stream + software = perfect software development: Methods and logic
Ideal stream + life = ??
Ideal stream + Management = ??
Ideal stream = the essence of deduction by concept and logic, and the pursuit of truth.