It projects how to estimate the amount of work together to learn!!!

In the process of project management, the estimation of workload is an important link, which is directly related to the success and failure of the project.

There are many ways to estimate the workload, such as empirical estimation, work decomposition, and mathematical modelling, but in our actual project management process, many well-known estimation methods are less flexible and convenient to use, and are not necessarily suitable for our actual projects.

   a lot of project managers ' ability to evaluate, manage and control projects is largely from the experience of the project manager itself, for a variety of reasons, The project manager is more of a generalist, this is in the current environment, to ensure that the project can still run the inevitable result.

   in the actual situation, the project is not only a long time, and the success rate is also very low, one of the most important reason is that there is no specific basis for the workload assessment of the demand, Most of the time it is assumed that estimating a number, when the project development process from the demand changes in the new requirements of the workload of insufficient estimates lead to a chain reaction, and finally lost control of the project. The purpose of this paper is to propose a model for estimating the overall workload of the project, which is used for the project manager in the face of the original contract design, in the process of the project to face the need to change the calculation of the workload of a reference. The purpose of this model is to effectively reduce the workload, which does not mean less work, but rather a guide to do the right thing. This model, in particular, can also indicate direction for increased productivity. To design a model, first of all, the daily work of a comprehensive analysis, abstract the work of each step, the need for each step of the knowledge used to summarize, but also need to evaluate the complexity of each step. In the development of a project, the first thing to do in the face of a business function is to design the table structure from the requirements, then define a variety of associations for the table structure, define the correlation basically in the brain to form the approximate appearance of the interface, and then start to write code. From the above procedure, it can be roughly divided into the following two steps:

1. Data structure design phase

2. The code phase of the data structure is followed by an analysis of the knowledge used in each step.

1. The knowledge used in the design phase of the data structure is divided into the following sections

1) Database Design knowledge

2) Business Knowledge

2. The knowledge used in writing the code phase based on the data structure is divided into the following sections

1) Knowledge of database operations

2) Background programming language knowledge

3) Foreground programming language knowledge

4) Business Knowledge

Through the above analysis can be seen, in the first phase of the need for a single, more derived from experience. Because of the less knowledge used, the less time is spent on change when demand changes.

Therefore, a simple conclusion can be drawn that when the knowledge required for a step is relatively single, the time required to change and encode the step is relatively small. Then you can see that in the second phase, the knowledge used is complex, so the second phase must be subdivided. In the second stage, it is common practice, according to the business function, first write about the business table additions and deletions of code, and then according to the relationship between the table write the data relationship code, and finally according to the design of the interface style, writing interface code.

This phase is also divided into the following steps:

1. Write the maintenance code for the single table

2. Write the business relation code for the table and other tables

3. Write the interface code the same

Then analyze the knowledge used in each step:

1. The knowledge used in the preparation of a single-table maintenance code is divided into the following sections

1) Database single table operation knowledge

2) Background programming language knowledge, only need to know how to operate the database

3) Business Knowledge

2. The knowledge used in writing this table with the business relation code of other tables is divided into the following sections

1) Database multi-table query knowledge

2) Background programming language, which is based on the complexity of the business to determine the scope of knowledge used.

3) Business Knowledge

3. The knowledge used in writing the interface code is divided into the following sections

1) HTML knowledge

2) JavaScript knowledge

3) CSS Knowledge

4) Background programming language, use only some knowledge related to writing the foreground interface.

It projects how to estimate the amount of work together to learn!!!