Managing and reporting on project progress is the primary focus of the Monitoring and Controlling processes. One of the Monitoring and Controlling processes that helps manage and control project progress is the Scope Verification process.
The inputs of the Scope Verification arc the project scope statement, WBS dictionary, project scope management plan, and deliverables. This process involves evaluating these inputs to determine if the work is complete and if it satisfies the project objectives. Evaluation is performed using inspection, which is the only tool and technique of this process. You should perform Scope Verification—even if the project is canceled—to document the degree to which the project was completed. This serves as historical information, and if the project is ever started up again, you've got documentation that tells you what was completed and how far the project progressed.
Scope Control Outputs
The outputs of the Scope Control process arc as follows:
• Project scope statement updates
■ WBS updates
• WBS dictionary updates
■ Scope baseline updates
• Requested changes
• Recommended corrective action
■ Organizational process assets update
■ Project management plan updates
Let's take a look at project scope statement changes and scope baseline updates. The remaining outputs have all been discussed previously.
Changes to scope will likely require that you run back through the project Planning processes and make any needed adjustments. This also means you'll need to update the project scope statement so it accurately reflects the project work after the change.
Scope changes include any changes to the project scope as defined by the agreed-upon WBS. This in turn may require changes or updates to project objectives, costs, quality measures or controls, or time in the form of schedule revisions. Scope changes always require schedule revisions.
The inputs of the Scope Verification arc the project scope statement, WBS dictionary, project scope management plan, and deliverables. This process involves evaluating these inputs to determine if the work is complete and if it satisfies the project objectives. Evaluation is performed using inspection, which is the only tool and technique of this process. You should perform Scope Verification—even if the project is canceled—to document the degree to which the project was completed. This serves as historical information, and if the project is ever started up again, you've got documentation that tells you what was completed and how far the project progressed.
Scope Control Outputs
The outputs of the Scope Control process arc as follows:
• Project scope statement updates
■ WBS updates
• WBS dictionary updates
■ Scope baseline updates
• Requested changes
• Recommended corrective action
■ Organizational process assets update
■ Project management plan updates
Let's take a look at project scope statement changes and scope baseline updates. The remaining outputs have all been discussed previously.
Changes to scope will likely require that you run back through the project Planning processes and make any needed adjustments. This also means you'll need to update the project scope statement so it accurately reflects the project work after the change.
Scope changes include any changes to the project scope as defined by the agreed-upon WBS. This in turn may require changes or updates to project objectives, costs, quality measures or controls, or time in the form of schedule revisions. Scope changes always require schedule revisions.