Section: Volume C
Explanation:
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)

12.1.3.1 Procurement Management Plan
Definition: Procurement management plan is a component of the project management plan that describes how a project team will acquire goods and services from outside the performing organization. It describes how the procurement processes will be managed from developing procurement documents through contract closure.
The procurement management plan can include guidance for:
Types of contracts to be used;

Risk management issues;

Whether independent estimates will be used and whether they are needed as evaluation criteria;

Those actions the project management team can take unilaterally, if the performing organization has a

prescribed procurement, contracting, or purchasing department;
Standardized procurement documents, if needed;

Managing multiple suppliers;

Coordinating procurement with other project aspects, such as scheduling and performance reporting;

Any constraints and assumptions that could affect planned procurements;

Handling the long lead times to purchase certain items from sellers and coordinating the extra time needed to

procure these items with the development of the project schedule;
Handling the make-or-buy decisions and linking them into the Estimate Activity Resources and Develop

Schedule processes; the scheduled dates in each contract for the contract deliverables and coordinating with the schedule development and control processes; Identifying requirements for performance bonds or insurance contracts to mitigate some forms of project risk;

Establishing the direction to be provided to the sellers on developing and maintaining a work breakdown

structure (WBS);
Establishing the form and format to be used for the procurement/contract statements of work;

Identifying prequalified sellers, if any, to be used; and

Procurement metrics to be used to manage contracts and evaluate sellers.

A procurement management plan can be formal or informal, can be highly detailed or broadly framed, and is based upon the needs of each project.

Explanation/Reference:
Explanation:
7.2.3.1 Activity Cost Estimates
Activity cost estimates are quantitative assessments of the probable costs required to complete project work. Cost estimates can be presented in summary form or in detail. Costs are estimated for all resources that are applied to the activity cost estimate. This includes, but is not limited to, direct labor, materials, equipment, services, facilities, information technology, and special categories such as cost of financing (including interest charges), an inflation allowance, exchange rates, or a cost contingency reserve. Indirect costs, if they are included in the project estimate, can be included at the activity level or at higher levels.
Process: 7.3 Determine Budget
Definition: The process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline.
Key Benefit: The key benefit of this process is that it determines the cost baseline against which project performance can be monitored and controlled.
Inputs
1. Cost management plan
2. Scope baseline
3. Activity cost estimates
4. Basis of estimates
5. Project schedule
6. Resource calendars
7. Risk register
8. Agreements
9. Organizational process assets
Tools & Techniques
1. Cost aggregation
2. Reserve analysis
3. Expert judgment
4. Historical relationships
5. Funding limit reconciliation
Outputs
1. Cost baseline
2. Project funding requirements
3. Project documents updates

Section: Volume A
Explanation:
Configuration control is focused on the specification of both the deliverables and the processes; while change control is focused on identifying, documenting, and approving or rejecting changes to the project documents, deliverables, or baselines.
Some of the configuration management activities included in the Perform Integrated Change Control process are as follows:
Configuration identification. Identification and selection of a configuration item to provide the basis for

which the product configuration is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
Configuration status accounting. Information is recorded and reported as to when appropriate data about

the configuration item should be provided. This information includes a listing of approved configuration identification, status of proposed changes to the configuration, and the implementation status of approved changes.
Configuration verification and audit. Configuration verification and configuration audits ensure the

composition of a project's configuration items is correct and that corresponding changes are registered, assessed, approved, tracked, and correctly implemented. This ensures the functional requirements defined in the configuration documentation have been met.

Explanation/Reference:
Explanation:
5.2.3.2 Requirements Traceability Matrix
The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing changes to the product scope.
Tracing includes, but is not limited to, tracing requirements for the following:
Business needs, opportunities, goals, and objectives;

Project objectives;

Project scope/WBS deliverables;

Product design;

Product development;

Test strategy and test scenarios; and

High-level requirements to more detailed requirements.

Attributes associated with each requirement can be recorded in the requirements traceability matrix. These attributes help to define key information about the requirement. Typical attributes used in the requirements traceability matrix may include: a unique identifier, a textual description of the requirement, the rationale for inclusion, owner, source, priority, version, current status (such as active, cancelled, deferred, added, approved, assigned, completed), and status date. Additional attributes to ensure that the requirement has met stakeholders' satisfaction may include stability, complexity, and acceptance criteria.