Section: Volume E
Explanation/Reference:

Section: Volume B
Explanation:
Inspections and Audits. A process to observe performance of contracted work or a promised product against agreed-upon requirements.
Process: 12.3 Control Procurements
Definition: The process of managing procurement relationships, monitoring contract performance, and making changes and corrections as appropriate.
Key Benefit: The key benefit of this process is that it ensures that both the seller's and buyer's performance meets procurement requirements according to the terms of the legal agreement.
Inputs
1. Project management plan
2. Procurement documents
3. Agreements
4. Approved change requests
5. Work performance reports
6. Work performance data
Tools & Techniques
1. Contract change control system
2. Procurement performance reviews
3. Inspections and audits
4. Performance reporting
5. Payment systems
6. Claims administration
7. Records management system
Outputs
1. Work performance information
2. Change requests
3. Project management plan updates
4. Project documents updates
5. Organizational process assets updates

Section: Volume D
Explanation
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 modifcation 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.