Section: Volume A
Explanation:
11.4.2.2 Quantitative Risk Analysis and Modeling Techniques
* Sensitivity analysis. Sensitivity analysis helps to determine which risks have the most potential impact on the project. It helps to understand how the variations in project's objectives correlate with variations in different uncertainties. Conversely, it examines the extent to which the uncertainty of each project element affects the objective being studied when all other uncertain elements are held at their baseline values. One typical display of sensitivity analysis is the tornado diagram (Figure 11-15), which is useful for comparing relative importance and impact of variables that have a high degree of uncertainty to those that are more stable. The Tornado diagram is also helpful in analyzing risk-taking scenarios enabled on specific risks whose quantitative analysis highlights possible benefits greater than corresponding identified negative impacts. A tornado diagram is a special type of bar chart used in sensitivity analysis for comparing the relative importance of the variables. In a tornado diagram, the Y-axis contains each type of uncertainty at base values, and the X-axis contains the spread or correlation of the uncertainty to the studied output. In this fgure, each uncertainty contains a horizontal bar and is ordered vertically to show uncertainties with a decreasing spread from the base values.

Section: Volume C
Explanation:
6.3.3.1 Project Schedule Network Diagrams
A project schedule network diagram is a graphical representation of the logical relationships, also referred to as dependencies, among the project schedule activities. Figure 6-11 illustrates a project schedule network diagram. A project schedule network diagram is produced manually or by using project management software.
It can include full project details, or have one or more summary activities. A summary narrative can accompany the diagram and describe the basic approach used to sequence the activities. Any unusual activity sequences within the network should be fully described within the narrative.
Process: 6.3 Sequence Activities
Definition: The process of identifying and documenting relationships among the project activities.
Key Benefit: The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Milestone list
5. Project scope statement
6. Enterprise environmental factors
7. Organizational process assets
Tools & Techniques
1. Precedence diagramming method (PDM)
2. Dependency determination
3. Leads and lags
Outputs
1. Project schedule network diagrams
2. Project documents updates

Explanation/Reference:
Explanation:
5.3.2.2 Product Analysis
For projects that have a product as a deliverable, as opposed to a service or result, product analysis can be an effective tool. Each application area has one or more generally accepted methods for translating high-level product descriptions into tangible deliverables. Product analysis includes techniques such as product breakdown, systems analysis, requirements analysis, systems engineering, value engineering, and value analysis.

Explanation/Reference:
Explanation:
4.1.2.1 Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources, including:
Other units within the organization,

Consultants,

Stakeholders, including customers or sponsors,

Professional and technical associations,

Industry groups,

Subject matter experts (SME), and

Project management office (PMO).

Process: 4.6. Close Project or Phase
Definition: The process of finalizing all activities across all of the Project Management Process Groups to formally complete the phase or project.
Key Benefit: The key benefit of this process is that it provides lessons learned, the formal ending of project work, and the release of organization resources to pursue new endeavors.
Inputs
1. Project management plan
2. Accepted deliverables
3. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Analytical techniques
3. Meetings
Outputs
1. Final product, service, or result transition
2. Organizational process assets updates