Section: Volume E

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/Reference:
Explanation:
Schedule -> Time Management Easy question

Section: Volume A
Explanation:
6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required or

inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested.
Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.
Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic,

preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for modification or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and non-

project activities. These dependencies are usually outside the project team's control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project activities

and are generally inside the project team's control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.

Section: Volume D
Explanation:
Process: 8.2 Perform Quality Assurance
Definition: The process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used.
Key Benefit: The key benefit of this process is that it facilitates the improvement of quality processes.
Inputs
1. Quality management plan
2. Process improvement plan
3. Quality metrics
4. Quality control measurements
5. Project documents
Tools & Techniques
1. Quality management and control tools
2. Quality audits
3. Process analysis
Outputs
1. Change requests
2. Project management plan updates
3. Project documents updates
4. Organizational process assets updates