WEB Project Manager manual-development time estimation

WEB Project Manager manual-development time estimation

Copyright Disclaimer: If you have a reprinted request, please indicate the source:Http://blog.csdn.net/yzhzYang Zheng

When creating a project schedule, the project manager needs to estimate the time required for each task. The allocation and Time Estimation of modules in the development task are the most important part. This article elaborates on this part.

I. Principles and objectives we need to grasp when allocating modules and estimating development time:
1. ensure the overall progress of the project.
2. It helps to ensure the quality of development codes.
3. It helps increase the development coding speed.

2. Each company has its own technical framework, and developers usually invest in specific business logic.
Generally, the development time required for each module depends on the following three factors:
1. The complexity of the business logic of this module.
2. developer's technical level and familiarity with the project's application (including familiarity with the framework and application ).
3. Are there any technical difficulties in the technical implementation of this module. Here I define technical difficulties as: there are some technical difficulties that have not been implemented in the existing system. For such problems, developers do not have relevant code for reference and need to invest some time to study and solve them.

3. Steps for module allocation and development time estimation:
1. After Dividing modules as project managers, I will estimate the development time required by each module by myself.

2. Call all developers to discuss module allocation and development time estimation.
The project manager will divide the modules so that developers can select the modules they are interested in. This can improve the initiative and participation of developers.
When assigning modules, the Project Manager also needs to consider the following aspects to ensure the development speed and quality.
(1) The same developer is responsible for the development of the same modules. For example, the same developer is responsible for the addition, deletion, and modification of articles. The advantage of doing so is that developers will be more familiar with the relevant logic, and the interface definition will be clearer, with a low communication cost.
(2) Persons with relatively high technical skills are responsible for modules with relatively high technical difficulties.
(3) persons familiar with this logic are responsible for complicated business logic.

 
3. After the module is allocated, the developer evaluates the time required by the module in charge of development. In this process, we will discuss the technical implementation of each module in detail to make the estimation of time more accurate.
 
4. The project manager confirms the estimated time of the developer.
As a project manager during the validation process, I will refer to the three factors mentioned above and compare the estimated time with the estimated time by developers. The difference will certainly exist. I will discuss the reasons for these differences with the technical staff.
For tasks with a long cycle, I usually subdivide them into three days at most. For tasks with a longer cycle, the higher the uncertainty, the higher the risk, and the more likely it will become the bottleneck of the project.
 
 
Suggestion:
1. During the project summary, make statistics on some data in the project, such as the development time and test time of the unit UC, which can be used as a reference for future development.
2. Make technical preparations for technical difficulties and arrange personnel research in advance before the project starts. This will save project time and reduce technical risks in the future.