The Scope Management Knowledge Area includes Scope Planning, Scope Definition, Create WBS, Scope Verification, and Scope Control. You'll recall that project scope describes the work required to produce the product or service of the project. This includes the requirements of the product, which describe the features and functionality of the product or service. Product scope, on the other hand, is the description of the product features. The product description is the document that defines the characteristics of the product or service of the project.
You can conclude from this that the Scope Control process involves changes to the project scope. Any modification to the agreed-upon WBS is considered a scope change. (It's been cons ago that we looked at this so remember that the WBS, or work breakdown structure, is a deliverables-oriented hierarchy that defines the total work of the project.) This means that the addition or deletion of activities or modifications to the existing activities on the WBS constitute a project scope change.
Changes in product scope will require changes to the project scope as well. Let's say one of your project deliverables is the design of a piece of specialized equipment that's integrated into your final product. Now let's say that due to engineering setbacks and some miscalculations, the specialized equipment requires design modifications. The redesign of this equipment impacts the end product, or product scope. Since changes to the product scope impact the project requirements, which arc detailed in the scope document, changes to project scope arc also required.
You can conclude from this that the Scope Control process involves changes to the project scope. Any modification to the agreed-upon WBS is considered a scope change. (It's been cons ago that we looked at this so remember that the WBS, or work breakdown structure, is a deliverables-oriented hierarchy that defines the total work of the project.) This means that the addition or deletion of activities or modifications to the existing activities on the WBS constitute a project scope change.
Changes in product scope will require changes to the project scope as well. Let's say one of your project deliverables is the design of a piece of specialized equipment that's integrated into your final product. Now let's say that due to engineering setbacks and some miscalculations, the specialized equipment requires design modifications. The redesign of this equipment impacts the end product, or product scope. Since changes to the product scope impact the project requirements, which arc detailed in the scope document, changes to project scope arc also required.