Discussion on software project Management (2)--Project contract problem

We all know whether the project can be concluded, is to be determined by the acceptance of the situation, in the domestic small and medium-sized enterprises in the project, for the project acceptance of this piece of the existence of a lot of fuzzy situation, is leading to the project acceptance process can not be carried out smoothly, and even can not be carried out
I ask a question, what is the standard of project acceptance? Everyone will say is the demand confirmation, then ask again, the requirements of the standard of confirmation is what. Yes, it's a project contract. Project contract is the first basis of project acceptance criteria, in the domestic software project contract, there are many problems, most of these project contracts describe the amount of the contract, project name, deliverables, several key points of time, for the implementation of the scope of the project will be some description, but are relatively simple and fuzzy. Another point, for some project managers, it is possible to even the project contract only part of the project boundary description also has no opportunity to see, this will inevitably lead to software project later acceptance problems.
Therefore, when a project contract is signed, we should consider the problem of project acceptance, define a clear scope for project acceptance, such as the departments involved in the project, the business list to be resolved, the objectives to be achieved, the delivery standards and specifications of deliverables, and the project acceptance plan as the appendix of the Contract, After the project acceptance, only this acceptance plan as the benchmark, this can effectively avoid the project in the process of unlimited expansion of the boundaries caused by the project can not complete the acceptance of the problem.
After the project contract period clear acceptance standard, in the demand stage, should take the project contract as the foundation, the acceptance Plan book as the guidance basis carries on the demand confirmation, if necessary, may revise the acceptance Plan book in the demand confirmation stage, thus may guarantee the project boundary and the contract not to have too many discrepancy.
After ensuring the quality of the project acceptance plan, later, when the project acceptance, it will not appear this did not realize, that also did not realize the problem (if there is no implementation, that may really be the implementation of the problem, forget to achieve), because the laws, and the project manager in the preparation of project acceptance, can also be referred to the acceptance plan in advance, so as not to achieve the goal of the part of the emergence of the problem can also be resolved in advance, for the project acceptance clears the barrier.