Project Plan-not just project progress-Adams Wang

The importance of the project plan should be clear to everyone. Brooks mentioned project planning/tracking in the article "hatching a catastrophe. In addition, the importance of plan docalization is described in many other chapters. Here, a project plan not only refers to the project progress, but also draws only the project progress using Microsoft Project.

In practice, the Project Plan can be considered from the following aspects:

Project Description: includes the project definition, name, background, goal and scope, deliverables, and acceptance criteria;

Project Organization Structure: defines the composition of project personnel. Note: This part of content will be continuously adjusted according to the implementation of the project;

Software life cycle: determines the appropriate cycle according to the characteristics of the project. Not all projects are applicable to the iteration cycle, nor are waterfall models useless. Some projects even need waterfall models as the backbone and add iteration features at a certain stage.

Project management: includes customer management, progress management, cost management, risk management, and training management;

Configuration Management: defines the project directory structure, product identification method, version control, and so on;

The project plan must be carefully considered based on the user and project features. It may be a few words, but its role is not described under the requirement specification. Project plans and requirement specifications are the most basic mandatory documents in the project documentation set.

In software development, theories and practices are a constant topic. We are fortunate to have been born in the age of information sharing and can be touched by the wise thoughts of our predecessors. "This magical age is far from over, and it is still developing rapidly. More fun, all in the future ." -- Brooks.
 
Http://www.mmmbook.com/review/pratice.htm