Page 164 -

5 - PROJECT SCOPE MANAGEMENT

5.6.1 control Scope: Inputs

5.6.1.1 Project Management Plan

Described in Section 4.2.3.1. The following information from the project management plan is used to control
scope:
• Scope baseline. The scope baseline is compared to actual results to determine if a change, corrective
action, or preventive action is necessary.

• Scope management plan. Sections from the scope management plan describe how the project scope
will be monitored and controlled.
• change management plan. The change management plan defines the process for managing change
on the project.
• configuration management plan. The configuration management plan defines those items that are
configurable, those items that require formal change control, and the process for controlling changes to
such items.
• requirements management plan. This plan is a component of the project management plan and
describes how the project requirements will be analyzed, documented, and managed.

5.6.1.2 requirements documentation

Described in Section 5.2.3.1. Requirements should be unambiguous (measurable and testable), traceable,
complete, consistent, and acceptable to key stakeholders. Well-documented requirements make it easier to detect
any deviation in the scope agreed for the project or product.

5.6.1.3 requirements traceability Matrix

Described in Section 5.2.3.2. The requirements traceability matrix helps to detect the impact of any change or
deviation from the scope baseline on the project objectives.

138 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.