Section: Volume B
Explanation:
10.1.2.3 Communication Models
The communication models used to facilitate communications and the exchange of information may vary from project to project and also within different stages of the same project. [..]. Medium is the technology medium and includes the mode of communication while noise includes any interference or barriers that might compromise the delivery of the message. The sequence of steps in a basic communication model is:
Encode. Thoughts or ideas are translated (encoded) into language by the sender.

Transmit Message. This information is then sent by the sender using communication channel (medium). The

transmission of this message may be compromised by various factors (e.g., distance, unfamiliar technology, inadequate infrastructure, cultural difference, and lack of background information). These factors are collectively termed as noise.
Decode. The message is translated by the receiver back into meaningful thoughts or ideas.

Acknowledge. Upon receipt of a message, the receiver may signal (acknowledge) receipt of the message but

this does not necessarily mean agreement with or comprehension of the message.
Feedback/Response. When the received message has been decoded and understood, the receiver encodes

thoughts and ideas into a message and then transmits this message to the original sender.
Process: 10.2 Manage Communications
Definition: The process of creating, collecting, distributing, storing, retrieving and the ultimate disposition of project information in accordance with the communications management plan.
Key Benefit: The key benefit of this process is that it enables an efficient and effective communications flow between project stakeholders.
Inputs
1. Communications management plan
2. Work performance reports
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Communication technology
2. Communication models
3. Communication methods
4. Information management systems
5. Performance reporting
Outputs
1. Project communications
2. Project management plan updates
3. Project documents updates
4. Organizational process assets updates

Section: Volume A
Explanation:
12.1.3.2 Procurement Statement of Work
The statement of work (SOW) for each procurement is developed from the project scope baseline and defines only that portion of the project scope that is to be included within the related contract. The procurement SOW describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products, services, or results. Sufficient detail can vary based on the nature of the item, the needs of the buyer, or the expected contract form. Information included in a SOW can include specifications, quantity desired, quality levels, performance data, period of performance, work location, and other requirements.
The procurement SOW is written to be clear, complete, and concise. It includes a description of any collateral services required, such as performance reporting or post-project operational support for the procured item. In some application areas, there are specific content and format requirements for a procurement SOW. Each individual procurement item requires a SOW; however, multiple products or services can be grouped as one procurement item within a single SOW.
The procurement SOW can be revised and refined as required as it moves through the procurement process until incorporated into a signed agreement.

Explanation/Reference:
Explanation:
6.5.2.6 Reserve Analysis
Definition: estimates may include contingency reserves, sometimes referred to as time reserves or buffers, into the project schedule to account for schedule uncertainty. Contingency reserves are the estimated duration within the schedule baseline, which is allocated for identified risks that are accepted and for which contingent or mitigation responses are developed. Contingency reserves are associated with the "known-unknowns," which may be estimated to account for this unknown amount of rework.
As more precise information about the project becomes available, the contingency reserve may be used, reduced, or eliminated. Contingency should be clearly identified in schedule documentation.
[..]
Estimates may also be produced for the amount of management reserve of time for the project.
Management reserves are a specified amount of the project duration withheld for management control purposes and are reserved for unforeseen work that is within scope of the project.
Management reserves are intended to address the "unknown-unknowns" that can affect a project.
Management reserve is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of management reserves may require a change to the schedule baseline.

Section: Volume B

Section: Volume E