The degree and level of detail to which the project scope statement defi nes the work that will be performed and the work that is excluded can determine how well the project management team can control the overall project scope. The detailed project scope statement includes, either directly, or by reference to other documents, the following:
• Product scope description. Progressively elaborates the characteristics of the product, service, or result described in the project charter and requirements documentation.
• Product acceptance criteria. Defi nes the process and criteria for accepting completed products, services, or results.
• Project deliverables. Deliverables include both the outputs that comprise the product or service of the project, as well as ancillary results, such as project management reports and documentation. The deliverables may be described at a summary level or in great detail.
• Project exclusions. Generally identifi es what is excluded as from the project. Explicitly stating what is out of scope for the project helps to manage stakeholders’ expectations.
• Project constraints. Lists and describes the specifi c project constraints associated with the project scope that limits the team’s options, for example, a predefi ned budget or any imposed dates or schedule milestones that are issued by the customer or performing organization. When a project is performed under contract, contractual provisions will generally be constraints. Information on constraints may be listed in the project scope statement or in a separate log.
• Project assumptions. Lists and describes the specifi c project assumptions associated with the project scope and the potential impact of those assumptions if they prove to be false. Project teams frequently identify, document, and validate assumptions as part of their planning process.Information on assumptions may be listed in the project scope statement or in a separate log.

詞條貢獻者： wyr  
 貢獻者按積分從高到低進行排序