What issues should I pay attention to when creating small engineering tables?

As the smallest Planning Unit in the development process, the small project Table plays an important role in guiding the work content and supervising and tracking the work progress in actual work. The improper small project table not only does not guide the operations of relevant personnel, but also transmits some error information to the project supervisor, resulting in incorrect judgment on the project status. So what problems should we pay attention to when creating small engineering tables?

1. Whether the task unit of the Planning Unit is completely decomposed and measurable. We often see such a plan:
Task: button click Processing
Job period: XXXX-XX-xx ~ Xxxx-xx
WT/Cr: xxxx-xx
The above plan seems to be feasible on the surface, and the task has been refined to the click processing of the button. In fact, the click processing of a simple button is also feasible, but after the button is clicked, it is obviously inappropriate to create a button click task for the click event to be processed by complicated logic. We must perform a structured decomposition based on the features to be implemented after the button is clicked. The following methods are more specific than the preceding methods:
Task: button click Processing
Task 1: After a button is clicked, the screen status is set. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
Task 2: Save the current data status and application environment. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
Task 3: prepare and process the data and application environment required by logical computing. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
Task 4: Logical computing 1. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
Task 5: Logical computing 2. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
......
Task N-1: Data status and application environment recovery before processing. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)
Task N: the screen status is restored. Job period: XXXX-XX-xx ~ Xxxx-xx (0.5 ~ 1 day workload)

2. Whether the completion time of the task plan is short enough. A plan is 3 ~ The five-day task may be due to insufficient decomposition of the task unit. Of course, there will be more invisible workload and unknown problems. Therefore, during the planning period of a task, the degree of cognition of the scheduler to the task can be determined.

3. Check whether the difficulty of a task matches the ability of the task. Unlike physical labor, software jobs are not simply mechanical repetitive work. They require complete and accurate thinking processes and appropriate implementation methods and implementation skills. For example, when Java is used to read and write XML files, if Java reflection mechanism is used, it can not only effectively reduce the amount of code, but also improve the degree of code reuse. For programmers who do not understand the reflection mechanism, the implementation method will be simple and mechanical. Whenever the nodes in the XML file change, they need to add or delete their implementation methods, such code is not only inflexible, but also wastes a lot of time.

4. Whether there is a linear logical dependency between different tasks. That is, the start of a task depends entirely on the end of another task. For such a task, if the scheduled start time is earlier than the completion time of the dependent task, the idle wait time will occur.

5. Is there sufficient time in the project table to review each task and time to correct the issues found during the review. In the small project table, you must not only define the task and plan to complete the task, but also reflect the audit plan and problem correction plan of the task.

6. When creating a small project table, we should put aside the schedule constraints and schedule the table according to the actual work requirements and workload. You cannot compress the job period or reduce the corresponding quality activities due to a tight schedule. The direct consequence of this operation is that the job quality cannot be guaranteed.

7. The planned period of the small project table cannot be too long, 2 ~ 3 weeks is suitable. In actual work, some unpredictable changes occur every day. For small engineering tables that are relatively long during the planning period, they cannot reflect the changing working environment in time, it will inevitably cause us a lot of trouble in adjusting the engineering tables.