This process monitors the status of the project and product scope. It also entails manages all changes relating to the scope or the performance of the project.
This process helps the project stay on track. It also prevents getting to far out 'in the weeds' with any changes or upgrades that may come along during the project life cycle. If the scope is validated, controlling the scope should not be too hard because it serves as the path.
Control Scope: Inputs, Tools and Techniques, and Outputs. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), 5th Edition" by Project Management Institute, 2013, p. 136. Copyright 2013 by PMI.Inc. Reprinted without permission.
1. Work performance data (Input): This homework assignment was from PMGT 614. It entailed observing schedule compressing techniques and how it would save time. The example from this homework assignment would be a start and finish from scheduled activities.
2. Variance Analysis (Tools and Techniques): Artifact was taken from homework from PMGT 614; it represents the variance analysis relating to costs and schedule from the bicycle project. This is the only tool and technique for the Control Scope process.
3. Work Performance Information (Output): data taken from the bicycle project from PMGT 614. This data contextualized information on how the project scope is performing compared to the baseline.