5.6 Control Scope

"The process of monitoring the status of the project and product scope and managing changes to the scope baseline."

The definition shown above in italics is taken from the Glossary of the Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Fifth Edition, Project Management Institute Inc., 2013

Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Fifth Edition, Project Management Institute Inc., 2013 Figure 5-16 Page 136

5.6 Control Scope:

Monitoring Project Scope and controlling changes to the Project Scope Baseline.

The PM takes care to:

  • Develop and implement a change control system.
  • Record and Evaluate change requests.
  • Identify and document corrective actions
  • Revise cost, schedule, or quality baselines as necessary.
  • Use performance management techniques to monitor changes.
  • Ensure formal agreements are reached and new specifications detailed when project scope is changed.
  • Prevent further changes from the source of the change(s) proactively
  • Document lessons learned.

Works closely with 4.5 Perform Integrated Change Control

  • By making sure changes are handled and processed

Variance Analysis:

  • Looking at what difference there is between actual and forecast – schedule, cost, baseline, quality
  • Identifying the reasons for the variance
  • Deciding whether corrective or preventive action is required

DISCLAIMER

Firebrand Training grants you a personal, non-exclusive, non-transferable license to access and use the site. You may download or print material from the site only for your own personal, non-commercial use. Read our full terms and conditions on http://www.firebrandtraining.co.uk/learn/terms-and-conditions.