Explanation/Reference:
Explanation:
11.6.2.5 Reserve Analysis
Throughout execution of the project, some risks may occur with positive or negative impacts on budget or schedule contingency reserves. Reserve analysis compares the amount of the contingency reserves remaining to the amount of risk remaining at any time in the project in order to determine if the remaining reserve is adequate.
Process: 11.6 Control Risks
Definition: The process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project.
Key Benefit: The key benefit of this process is that it improves efficiency of the risk approach throughout the project life cycle to continuously optimize risk responses.
Inputs
1. Project management plan
2. Risk register
3. Work performance data
4. Work performance reports
Tools & Techniques
1. Risk reassessment
2. Risk audits
3. Variance and trend analysis
4. Technical performance measurement
5. Reserve analysis
6. Meetings
Outputs
1. Work performance information
2. Change requests
3. Project management plan updates
4. Project documents updates
5. Organizational process assets updates
6.5.2.6 Reserve Analysis
Duration 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 E

Section: Volume E
Explanation
Explanation:
11.2.1.12 Enterprise Environmental Factors
Described in Section 2.1.5. Enterprise environmental factors that can influence the Identify Risks process include, but are not limited to:
Published information, including commercial databases,

Academic studies,

Published checklists,

Benchmarking,

Industry studies, and

Risk attitudes.

Process: 11.2 Identify Risks
Definition: The process of determining which risks may affect the project and documenting their characteristics.
Key Benefit: The key benefit of this process is the documentation of existing risks and the knowledge and ability it provides to the project team to anticipate events.
Inputs
1. Risk management plan
2. Cost management plan
3. Schedule management plan
4. Quality management plan
5. Human resource management plan
6. Scope baseline
7. Activity cost estimates
8. Activity duration estimates
9. Stakeholder register
10.Project documents
11.Procurement documents
12.Enterprise environmental factors
13.Organizational process assets
Tools & Techniques
1. Documentation reviews
2. Information gathering techniques
3. Checklist analysis
4. Assumptions analysis
5. Diagramming techniques
6. SWOT analysis
Expert judgment
Outputs
Risk register

Section: Volume D

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

Explanation/Reference:
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 E
Explanation/Reference:

Explanation/Reference:
Explanation:
Process: 6.6 Develop Schedule
Definition: The process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule model.
Key Benefit: The key benefit of this process is that by entering schedule activities, durations, resources, resource availabilities, and logical relationships into the scheduling tool, it generates a schedule model with planned dates for completing project activities.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Project schedule network diagrams
5. Activity resource requirements
6. Resource calendars
7. Activity duration estimates
8. Project scope statement
9. Risk register
10.Project staff assignments
11.Resource breakdown structure
12.Enterprise environmental factors
13.Organizational process assets
Tools & Techniques
1. Schedule network analysis
2. Critical path method
3. Critical chain method
4. Resource optimization techniques
5. Modeling techniques
6. Leads and lags
7. Schedule compression
8. .Scheduling tool
Outputs
1. Schedule baseline
2. .Project schedule
3. Schedule data
4. Project calendars
5. Project management plan updates
6. Project documents updates

Section: Volume C
Explanation:
5.3.3.1 Project Scope Statement
The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. The project scope statement documents the entire scope, including project and product scope. It describes, in detail, the project’s deliverables and the work required to create those deliverables. It also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team’s work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries.
The degree and level of detail to which the project scope statement defines the work that will be performed and the work that is excluded can help determine how well the project management team can control the overall project scope. The detailed project scope statement, either directly, or by reference to other documents, includes the following:
Product scope description. Progressively elaborates the characteristics of the product, service, or result

described in the project charter and requirements documentation.
Acceptance criteria. A set of conditions that is required to be met before deliverables are accepted.

Deliverable. Any unique and verifiable product, result, or capability to perform a service that is required to be

produced to complete a process, phase, or project. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.

Section: Volume A
Explanation:
CV = EV – AC
CPI = EV / AC
SV = EV – PV
SPI = EV / PV