Unit 5: Web Field Trip: Managing the Project Scope

1. The product scope describes the finished deliverable of a product or service the project customer will accept. Products, for example such as cars, software, and soda, may have multiple projects contributing to the product. The product scope describes the features and functions of the entity the scope contributes to. Products can live on in an organization for an indefinite duration. The project scope describes all of the project work, and only the project work, to create the project requirements. The project scope is tied to the project which has a definite ending.

2. The project scope statement is the document that serves as a guide for all future project decisions. It is a document that defines all of the project requirements and the project deliverables that will equate to the acceptance of the project work.

3. Project scope change request must be documented so that the change request is fully analyzed for its effect on the project's success. All scope change request must be reviewed for the changes affect on the project time, cost, scope, quality, human resources, communications, risk, and procurement. It is important to document the change request rather than to just incorporate the change into the project work because it can cause problems during scope verification. When the customer inspects the work and they see the changed work does not match the project scope or the WBS there may be confusion as to who approved the change, who paid for the change, and why the change has not been documented.