The project plan is generally formed in the initial stage of the plan and is relatively stable during the project.

Once the timetable project structure is clear, it should be compiled and updated as the project progresses.

The project plan shall include the following aspects:

Name, code and other relevant identification reference materials, background materials, role assignment and responsibility division of the identification plan.

Decision-making of project design method

Staffing includes skills requirements, arrival time and employment methods.

Training requirements, external training and internal training requirements, methods and cost plans, etc.

Risk Identify risk factors, analyze costs and plan avoidance measures.

Handling of unexpected events

Configure management version control tools and usage rules

Monitoring and reporting of process

Test plan and scheme

Management of program errors

The process of software release

Generally speaking, the project plan is relatively stable. Generally, it is completed at the beginning of the project, and few changes are needed in the subsequent process. It should be emphasized that the value of the project plan lies not in the paper document itself, but in the thinking and problem-solving ideas generated in the writing process. Similarly, it can also be the basis for your decision.

Besides, you don't have to write everything in the project plan. Because many contents in the plan file are similar to those in the past, some contents can be in different documents.