Summarize some documents that the project manager must write (refers to documents other than the necessary management documents)

A brother in Csdn sent a post, titled "The Role of project manager in large Projects", the link is as follows: http://community.csdn.net/Expert/topic/4976/4976335.xml?temp=.2050135

Read this brother's article, quite touched, according to his experience, I summed up the project manager must write some documents (refers to the necessary management documents outside the document):
1. If the customer proposes to increase the demand or modify the requirements, then need to change or increase the demand for these records. According to the current situation, it is clear what is being done, what needs to be deferred to the two or three phases of the project, what needs are in conflict with the previous ones, and which are unreasonable, and ask the customer to confirm the signature.
2, if there are users to put forward a demand, then write clearly this demand is who proposed, but also a more important link.
3. Meeting minutes of each meeting.
4, every week to write the summary, do not need to be very detailed, but to speak clearly. Monthly reports are also required monthly, progress Monthly report.
5, each month's progress report, writes clearly completes the function module the situation, also needs to let the user indicate which has not completed or has the opinion, in forms a report.

Project manager is to stand on a higher level to look at the problem, to the success of the project, one of the most important factor is to grasp the customer's needs, can not let the customer anything to mention, the customer put forward any needs to be reviewed, not what needs can be done. Because sometimes the customer is what they want is not very clear, in this case, the proposed demand is problematic, or demand and the previous demand contradiction, or demand is not reasonable, do is also white do, so, for each need to undergo review. The significance of the review can not only play a clear role of demand, but also to the user to straighten out the idea of help. The review meeting can open frequently, when the demand accumulates to a certain extent, can open. Review not only needs to review, but also should include system analysis review, design review and so on.

The project manager must grasp well, can not let the customer's demand spread or the customer's demand is in you can grasp the situation, otherwise, once this situation, the project failure has become a foregone conclusion.
The project manager must grasp the rhythm of the project, so that all things are in the rhythm of your control, otherwise, if the project controls you, you will be finished.