Section: Volume B
Explanation:
5.4.3.1 Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include:
Project scope statement. The project scope statement includes the description of the project scope, major
deliverables, assumptions, and constraints.
WBS. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project
team to accomplish the project objectives and create the required deliverables. Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information. A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to the earned value for performance measurement. Control accounts are placed at selected management points in the WBS. Each control account may include one or more work packages, but each of the work packages should be associated with only one control account. A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account with known work content but without detailed schedule activities.
WBS dictionary. The WBS dictionary is a document that provides detailed deliverable, activity, and
scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Information in the WBS dictionary may include, but is not limited to:
○ Code of account identifier,
○ Description of work,
○ Assumptions and constraints,
○ Responsible organization,
○ Schedule milestones,
○ Associated schedule activities,
○ Resources required,
○ Cost estimates,
○ Quality requirements,
○ Acceptance criteria,
○ Technical references, and
○ Agreement information
4.2.3.1 Project Management Plan
The project management plan is the document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates all of the subsidiary plans and baselines from the planning processes.
Project baselines include, but are not limited to:
Scope baseline (Section 5.4.3.1),
Schedule baseline (Section 6.6.3.1), and
Cost baseline (Section 7.3.3.1).
Subsidiary plans include, but are not limited to:
Scope management plan (Section 5.1.3.1),
Requirements management plan (Section 5.1.3.2),
Schedule management plan (Section 6.1.3.1),
Cost management plan (Section 7.1.3.1),
Quality management plan (Section 8.1.3.1),
Process improvement plan (Section 8.1.3.2),
Human resource management plan (Section 9.1.3.1),
Communications management plan (Section 10.1.3.1),
Risk management plan (Section 11.1.3.1),
Procurement management plan (Section 12.1.3.1), and
Stakeholder management plan (Section 13.2.3.1).
Among other things, the project management plan may also include the following:
Life cycle selected for the project and the processes that will be applied to each phase;
Details of the tailoring decisions specified by the project management team as follows:
○ Project management processes selected by the project management team,
○ Level of implementation for each selected process,
○ Descriptions of the tools and techniques to be used for accomplishing those processes, and
○ Description of how the selected processes will be used to manage the specific project, including the dependencies and interactions among those processes and the essential inputs and outputs.
Description of how work will be executed to accomplish the project objectives;
Change management plan that documents how changes will be monitored and controlled;
Configuration management plan that documents how Configuration management will be performed;
Description of how the integrity of the project baselines will be maintained;
Requirements and techniques for communication among stakeholders; and
Key management reviews for content, the extent of, and timing to address, open issues and pending
decisions.
The project management plan may be either summary level or detailed, and may be composed of one or more subsidiary plans. Each of the subsidiary plans is detailed to the extent required by the specific project. Once the project management plan is baselined, it may only be changed when a change request is generated and approved through the Perform Integrated Change Control process.
