Explanation/Reference:
Explanation:
2.1.4 Organizational Process Assets
Organizational process assets are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. The process assets also include the organization's knowledge bases such as lessons learned and historical information. Organizational process assets may include completed schedules, risk data, and earned value data. Organizational process assets are inputs to most planning processes. Throughout the project, the project team members may update and add to the organizational process assets as necessary.
Organizational process assets may be grouped into two categories: (1) processes and procedures, and (2) corporate knowledge base.

Section: Volume E
Explanation/Reference: https://www.projectsmart.co.uk/the-role-of-the-project-manager.php

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

Explanation/Reference:
Explanation:
8.1.3.3 Quality Metrics
A quality metric specifically describes a project or product attribute and how the control quality process will measure it. A measurement is an actual value. The tolerance defines the allowable variations to the metric. For example, if the quality objective is to stay within the approved budget by ± 10%, the specific quality metric is used to measure the cost of every deliverable and determine the percent variance from the approved budget for that deliverable. Quality metrics are used in the perform quality assurance and control quality processes. Some examples of quality metrics include on-time performance, cost control, defect frequency, failure rate, availability, reliability, and test coverage.
Process: 8.1 Plan Quality Management
Definition: The process of identifying quality requirements and/or standards for the project and its deliverables and documenting how the project will demonstrate compliance with quality requirements and/ or standards.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how quality will be managed and validated throughout the project.
Inputs
1. Project management plan
2. Stakeholder register
3. Risk register
4. Requirements documentation
5. Enterprise environmental factors
6. Organizational process assets
1. Tools & Techniques
2. Cost-benefit analysis
3. Cost of quality
4. Seven basic quality tools
5. Benchmarking
6. Design of experiments
7. Statistical sampling
8. Additional quality planning tools
9. Meetings
Outputs
1. Quality management plan
2. Process improvement plan
3. Quality metrics
4. Quality checklists
5. Project documents updates
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