Chapter III
u How to develop a stage plan
u How to develop product plans
u Manage time
3.1 How to Develop a Stage Plan
Here are two plans: stage planning and product plans. The stage plan is about the arrangement of time during this time, the product plan is the time schedule for making product activities. Take a book as an example to explain the difference between stage planning and product plan. In order to plan this work, first it is estimated how long it takes to spend the entire task. For example, you might want to read the contents of 20 chapters 20 hours. For this task, the product plan is the target of 20 hours, and the stage plan is to arrange 1 hour of reading every week. The figure below shows the relationship between product plans and stage programs in business areas.
In order to formulate a stage plan, you must clear the use of time. According to the weekly audio summary table introduced in the previous chapter, we can track how you give yourself. When developing a next week, you can refer to the nearest weekly audio summary table. Depending on the time that the previous task spends, it can judge how much time will be spent on these tasks next week. The easiest way to develop this plan is to assume that the time to use is the same as the past average. A more accurate method is to first consider the work content to be done next week, then estimate a suitable time based on the previous maximum and shortest times.
3.2 How to Develop Product Plan
When the engineer working in the project team, you need to plan your personal work. The plan is the reliable basis for completing the commitment of the commitment. It can help engineers understand the status of the project during the development of the engineer. It is an important part of the software engineer's work. To become a talented engineer, you must know how to develop an accurate plan, and you need to know how to compare these plans to actual results, so learning to develop a better plan.
Developing a product plan is a skill that can be improved through an event. From now on, you can develop a plan for each product, the product can be a developable program, a programming or a test plan, and continue to do so in future projects.
Collect historical project data. For engineers, a product plan includes estimates of product scale, working hours and progress. The most basic product plan includes only estimates of time required for tasks or jobs. By collecting data used in previous tasks, you can estimate the time required for similar tasks. Table 3.1 is to record job number logs designed for each project estimation time and actual time, refer to these historical project data, we can make an estimate of it, and accurately. Accurate estimate is the key to doing a plan.
Table 3.1 Operation Number Log
Work number
date
process
Estimate data
The actual data
Cumulative data
time
unit
time
unit
average value
time
unit
average value
Maximum
Minimum
description:
description:
Estimation program size. The first step in the product plan is to estimate the size of the product. For programs, you can use the code line measurement method to estimate the size of the new program. For accurate estimation, it is necessary to use the previous scale data, so the previous scale data is helpful. First check the needs of the new program, it is estimated how many lines have, and then compare the number of previously statistics, how much time it takes to develop new programs. As the accumulated data is increasing, the estimated estimate will become more accurate. The job number log is a simple method as a large number of historical scale and efficiency data, and can also use Table 3.2 record the programs historical data of the incomplete function, and arrange it according to scale.
Table 3.2 Program size estimation table
program
Code line
Previous function
Estimate
Minimum
average
maximum
