5.6 Control Scope
Process Definition
Controlling scope is the process of managing scope creep. This process monitors project scope and any changes to the scope baseline. Control scope is there to ensure that it is only the work identified as being in scope that is delivered, and in this way scope creep is avoided.
Figure 43. Project Management Body of Knowledge Figure 5-16. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), 5th Edition" by Project Management Institute, 2013, p. 232. Copyright 2013 by Project Management Institute, Inc. Reprinted without permission.
Process Assessment
This process is primarily utilized to not only monitor scope but to manage the actual changes to the scope that occur. This is tied to other processes and ensures the changes are being vetted through them before implementation. It's imperative that any change correctly adjusts changes to time, cost, resources, etc. to avoid scope creep.
(Inputs) Work Performance Data
Work performance data is raw data on activities being performed. This example is a snapshot of Microsoft Project 2013 project reports taken from an assignment I completed PMGT 501 Fundamentals of Project Management, MS Project Lesson 1.
(Tools & Techniques) Variance Analysis
Variance analysis can determine the degree of difference from the scope baseline and the work that has actually been performed. This example is from a group project in PGMT 612 Leading Projects Across Cultural, Corporate, and International Boundaries, that was written by Jeremy Curbey, Khoi ChuChe, Corey Cowley, Reese Darlington, and Domingo Tuckler.
(Outputs) Work Performance Information
Work performance information is a good output for validating scope and will provide the project manager a good foundation for making project control decisions. This example is from an assignment from PMGT 502 Effective Communications for Managing Projects and a forecast from a Case Study I completed in MGMT 524 Management Science.