Page 136 -

5 - PROJECT SCOPE MANAGEMENT

• Process for preparing a detailed project scope statement;
• Process that enables the creation of the WBS from the detailed project scope statement;

• Process that establishes how the WBS will be maintained and approved;
• Process that specifies how formal acceptance of the completed project deliverables will be obtained; and

• Process to control how requests for changes to the detailed project scope statement will be processed.
This process is directly linked to the Perform Integrated Change Control process (Section 4.5).

The scope management plan can be formal or informal, broadly framed or highly detailed, based on the needs
of the project.

5.1.3.2 requirements Management Plan

The requirements management plan is a component of the project management plan that describes how
requirements will be analyzed, documented, and managed. The phase-to-phase relationship, described in
Section 2.4.2.1, strongly influences how requirements are managed. The project manager chooses the most
effective relationship for the project and documents this approach in the requirements management plan. Many of
the requirements management plan components are based on that relationship.

Components of the requirements management plan can include, but are not limited to:

• How requirements activities will be planned, tracked, and reported;
• Configuration management activities such as: how changes to the product will be initiated, how impacts
will be analyzed, how they will be traced, tracked, and reported, as well as the authorization levels
required to approve these changes;
• Requirements prioritization process;

• Product metrics that will be used and the rationale for using them; and
• Traceability structure to reflect which requirement attributes will be captured on the traceability matrix.

5.2 collect requirements

Collect Requirements is the process of determining, documenting, and managing stakeholder needs and
requirements to meet project objectives. The key benefit of this process is that it provides the basis for defining and
managing the project scope including product scope. The inputs, tools and techniques, and outputs of this process
are depicted in Figure 5-4. Figure 5-5 depicts the data flow diagram of the process.

110 ©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.