Control Scope

Posted on June 2, 2009 by


The Control Scope process is one of the 42 project management processes described in the fourth edition PMBOK®. It’s one of the five Scope knowledge area processes, and one of the ten Monitoring and Controlling processes. The primary purpose of this process is to watch the product and project scope as well as manage any changes to the scope baseline. This process safeguards against scope creep so that the project’s boundaries do not expand. Knowing what the project boundaries are and how to handle changes to them is found in the Project Management Plan (specifically the Scope Baseline, Scope Management Plan, Change Management Plan, Configuration Management Plan, and Requirements Management Plan), Requirements Documentation and Requirements Traceability Matrix. Work Performance Information indicates how well actual progress aligns with the scope baseline. The only tool and technique of this process is Variance Analysis. This simply compares actual progress to the scope baseline. These comparisons of Work Performance Measurements are an output that can be shared with stakeholders. If changes are needed based on these measurements, there will be Change Requests which go through the Perform Integrated Change Control process. Updates may also be needed to Organizational Process Assets, the Project Management Plan, and Project Documents. Also see the earlier postings of Change Requests (posted May 11, 2009) and Perform Integrated Change Control Process (posted June 1, 2009).