Summarize some of the documents that the project manager must write (refer to documents outside of the necessary management documents)

There is a brother in Csdn sent a post, titled "Big Project Project Manager role", links are as follows: http://community.csdn.net/Expert/topic/4976/4976335.xml?temp=.2050135

Having read this brother's article, I have a feeling that, based on his experience, I have summed up some of the documents that the project manager must write (referring to documents outside of the necessary management documents):
1, if the customer proposed to increase demand or modify the requirements, then need to change these requirements or increase the record. According to the current situation, write clearly what is being done, what needs to be postponed to the project two or three period, which needs conflict with the previous, which requirements are unreasonable, and ask the customer to confirm the signature.
2, if there is a user to propose a demand, then write clear who is the demand for the proposed, but also a more important link.
3, the minutes of each meeting.
4, every week to write summary, not very detailed, but to make it clear. Monthly report and Progress month are also required.
5, each month progress report, write clearly completes the function module the situation, also needs to let the user point out which has not completed or has the opinion, in forms a report.

The project manager is standing at a higher level to look at the problem, to project success, one of the most important factor is to hold the customer's needs, not to allow customers to mention anything, the customer put forward any needs are reviewed, not what needs can be done. Because sometimes customers for what they want is not very clear, in this case, put forward the demand is problematic, or demand and previous demand contradictions, or the demand is not reasonable, do is also white, so, for each need to undergo review. The significance of the review can not only play a clear role of demand, but also to rationalize the user's thinking to help. Review meetings can often open, when the demand has accumulated to a certain extent, you can open. The review not only needs review, but also includes system analysis and review, design review and so on.

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