Project planning management-6

The above is a simple introduction. You should have a little understanding of our company's project planning and management processes, that is, we should first establish a preliminary plan, then, adjust the plan based on the actual data. The plan is simple and simple. The Administrator only needs to check whether there is any warning every day and analyze some reports, employees have to record their daily work in the system to obtain real data for devplan analysis.

 

 

In the initial stage of techexcel project migration (devplan was not started at that time, but several other tools, devspec and devtrack, were only enabled, because we need to record a lot of data, such as the daily commuting time, the time for asking for leave, what is the daily activity, how much time it takes, and the exact completion time of the task, we have to record it in the system, at first, I thought it was too time-consuming, which greatly affected my work efficiency. After devplan was launched, I discovered how useful the data was originally recorded. Although it cannot be said that it was 100%, however, most of the trends can still be predicted, so until now, the project has basically been smooth and can generally be completed within a controllable range.

 

Our company uses devplanAt the same timeIt manages more than a dozen projects. In addition to the inconsistent schedule, other projects share the company's resources, mainly human resources and document systems, I would like to mention that many projects are separated by project personnel, so each project can calculate its own resources. However, in some cases, the same manpower will work in different projects at the same time. Therefore, to calculate manpower, you must analyze the situations of several projects at the same time, and these projects may have different time periods, in the past, it was difficult to use the Microsoft Project to analyze whether this person is under pressure. Now we can find it well in devplan.

 

Of course, it is hard to predict or analyze some risks, especially those that do not match software or technology at all, just like the earthquake mentioned above, however, this is a little exaggerated, but there will still be many unpredictable problems in our actual work. We have also consulted Mr. Cai from techexcel before, of course, we can also think of the results. It is indeed difficult to predict the destructive effects of such risks on the project. We can only do some warning to the greatest extent. For example, this project may have such risks, when making any decision, managers should note that such risks have different risk levels, so that leaders can pay attention to them.

 

 

 

(To be continued)