The scope statement should include, either directly or by reference to other documents: Project justification--the business need that the project was undertaken to ad-dress. The project justification provides the basis for evaluating future trade-offs. Project product--a brief summary of the product description Project deliverables--a list of the summary level sub-products whose full and satisfactory delivery marks completion of the project. For example, the major deliverables for a software development project will include the working computer code, a user manual, and full documentation. Project objectives--the quantifiable criteria that must be met for the project to be considered successful. Project objectives should include: cost, schedule, and quality measures. Unquantified objectives (e.g., customer satisfaction) entail high risk as you can never prove you met them.

Usually a written document describing the project business purpose, objectives and goals, and scope. It often is begun in the project initiation phase (as a preliminary scope statement) and further evolves with the project planning. It is often similar (at least initially) to the project charter. See Unit 3 for a scope statement worksheet. See section 5.2.3.1 in the PMBOK for more information.