Keep control Scope in project management ( PMP ) is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. controlling project scope method’s major benefit is that it keeps the scope baseline throughout the project. This method is used all the way through the project. The steps, tools, and Techniques of this process are shown in the figure below.
Controlling the project scope makes sure that the Perform Integrated Change Control method handles all changes that are asked for and suggested actions to fix or stop problems. In addition to managing changes as they happen, Control Scope works with all the other control processes. Scope creep is the unchecked growth of a product or project’s goals without adjusting for time, cost, or resources. Since things are always changing, every project needs to have some kind of change control method.
Control Scope: Inputs
Project Management Plan
The following are some of the parts of a project management plan:
- The scope management plan defines how the project and product scope will be managed.
- The requirements management plan spells out how the needs of the project will be handled.
- The change management plan lays out how to handle changes on the job.
- The configuration management plan lists the things that can be configured, the things that need official change control, and the way that changes to those things can be controlled.
- Compared to the scope baseline, the real results show if a change, corrective action, or preventative action is needed.
- The performance measurement baseline is compared to the real results in earned value analysis to see if a change, corrective action, or preventive action is needed.
Project Documents
It’s possible to use the following project documents as inputs for control Scope in project management ( PMP ) process:
- Lessons learned register
- Requirements documentation
- Requirements traceability matrix
Work Performance Data
Some types of work performance data are the number of change requests that are sent in, the number that are accepted, and the number of projects that are checked, confirmed, and finished.
Organizational Process Assets
Existing official and informal scope, control-related policies, procedures, and guidelines, as well as monitoring and reporting methods and templates, are some of the organizational process assets that can affect the Control Scope process.
Control Scope: Tools And Techniques
Data Analysis
Variance analysis
Variance analysis checks if the difference between the starting point and the real results is within a certain range and suggestive or preventative actions.
Trend analysis
Trend analysis looks at how well a project is doing over time to see if it is getting better or worse.
Control Scope: Outputs
Work Performance Information
It includes correlated and contextualized data on how the project and product scope are doing compared to the standard scope. You can list the types of changes you made, the differences in the scope that you found and why they happened, how they affect the plan or cost, and your prediction for how the scope will perform in the future.
Change Requests
A review of the project’s progress could lead to a request to alter the scope and schedule guidelines or other parts of the project management plan. The Perform Integrated Change Control method takes change requests and reviews and decides what to do with them.
Project Management Plan Updates
People in the company have to fill out a change request for any changes they want to make to the project management plan. The following parts of the project management plan may need a change request after controlling project scope :
- Scope management plan
- Scope baseline
- Schedule baseline
- Cost baseline
- Performance measurement baseline
Project Documents Updates
Because of control Scope in project management ( PMP ) process, project documents like, but aren’t limited to, the following may be updated:
- The lessons learned register can be updated with methods that are quick and good at controlling scope, such as the reasons for differences and the corrective actions that were chosen.
- Updates to requirements documents may include new or different requirements.
- It is possible to make changes to the requirements traceability grid to match changes made to the documentation of the requirements.
References :