When making the project schedule, we should pay attention to the following points:
1. Confirm the function module
Because the function module is defined, the time to develop the function can be evaluated. General functional modules only need to list large modules, because the modules are too small to be evaluated in a few days, which leads to poor scheduling.
2. Confirm the start time and end time.
Because only when the start time and end time are clear can we talk about the schedule. These two time points need to be confirmed with the customer. The start time is the official start time of the project, and the end time is the delivery time of the project (this is generally stipulated in the contract).
To teach you a little trick, the starting time can be arranged in about three working days after the confirmation of the renderings, because this will give R&D time to study the prototype drawings. Don't underestimate these three working days, sometimes it is these three working days to complete the test. There is a spirit of racing against time in doing projects.
3. Determine milestones
It is called project schedule, in order to plan milestones. Usually, a milestone is the time to produce an actual result (the actual result here is the actual product that can be seen).
Please note that a project milestone is not a simple project time node, but a point in time when results can be delivered.
4. Reasonable arrangement of project time ratio
Generally speaking, the project time is divided into research and development time, interface docking time, testing time and online time.
It is difficult for junior project managers to arrange the time ratio. I personally summarize the time proportion distribution of a project here. Generally, R&D accounts for three fifths of the whole project. For example, for a three-month project, the R&D time should be at least 1.8 months and 40 working days, and the testing time is half of the R&D time. This test time includes writing test cases and simple test time. Why is the exam so long? Because the tested bugs need to be modified, the modified bugs need to be tested. The general test is divided into three rounds. The first round of testing runs in the whole process, the second round of testing is aimed at functional testing with bugs, and the third round of testing tries to imitate application scenario testing based on simulation data.
Interface docking and online time is usually 7 working days, and then the project needs to reserve 7 to 10 working days as the time to deal with mobile risks.
5. Project schedule (Yin and Yang)
Why do you need to make two project schedules? Because one is for customers and the other is for internal research and development to catch up with the progress, this is called tight inside and loose outside; Make up a little internal time, stay ahead of time, and reserve more risk handling time for the project. External relaxation is to win customers more project time. Remember that the time won is evenly distributed among the functional modules, and you can't just increase the project testing time, so as to avoid customers asking for testing projects in advance.