Section: Volume E
Explanation/Reference:

Section: Volume E

Section: Volume D

Section: Volume D
Explanation:
6.2.2.2 Rolling Wave Planning
Rolling wave planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. It is a form of progressive elaboration.
Therefore, work can exist at various levels of detail depending on where it is in the project life cycle. During early strategic planning, when information is less defined, work packages may be decomposed to the known level of detail. As more is known about the upcoming events in the near term, work packages can be decomposed into activities.
4.2.3.1 Project Management Plan
The project management plan is the document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates all of the subsidiary plans and baselines from the planning processes.
Project baselines include, but are not limited to:
Scope baseline (Section 5.4.3.1),

Schedule baseline (Section 6.6.3.1), and

Cost baseline (Section 7.3.3.1).

Subsidiary plans include, but are not limited to:
Scope management plan (Section 5.1.3.1),

Requirements management plan (Section 5.1.3.2),

Schedule management plan (Section 6.1.3.1),

Cost management plan (Section 7.1.3.1),

Quality management plan (Section 8.1.3.1),

Process improvement plan (Section 8.1.3.2),

Human resource management plan (Section 9.1.3.1),

Communications management plan (Section 10.1.3.1),

Risk management plan (Section 11.1.3.1),

Procurement management plan (Section 12.1.3.1), and

Stakeholder management plan (Section 13.2.3.1).

Among other things, the project management plan may also include the following:
Life cycle selected for the project and the processes that will be applied to each phase;

Details of the tailoring decisions specified by the project management team as follows:

○ Project management processes selected by the project management team,
○ Level of implementation for each selected process,
○ Descriptions of the tools and techniques to be used for accomplishing those processes, and
○ Description of how the selected processes will be used to manage the specific project, including the dependencies and interactions among those processes and the essential inputs and outputs.
Description of how work will be executed to accomplish the project objectives;

Change management plan that documents how changes will be monitored and controlled;

Configuration management plan that documents how Configuration management will be performed;

Description of how the integrity of the project baselines will be maintained;

Requirements and techniques for communication among stakeholders; and

Key management reviews for content, the extent of, and timing to address, open issues and pending

decisions.
The project management plan may be either summary level or detailed, and may be composed of one or more subsidiary plans. Each of the subsidiary plans is detailed to the extent required by the specific project. Once the project management plan is baselined, it may only be changed when a change request is generated and approved through the Perform Integrated Change Control process.

Explanation/Reference:
Explanation:
Root cause analysis. Root-cause analysis is a specific technique used to identify a problem, discover the underlying causes that lead to it, and develop preventive action.
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

Section: Volume D
Explanation
Explanation:
11.4.2.2 Quantitative Risk Analysis and Modeling Techniques
Commonly used techniques use both event-oriented and project-oriented analysis approaches, including:
* 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.

Explanation/Reference:
Reference: https://www.google.com/url?
sa=t&rct=j&q=&esrc=s&source=web&cd=4&ved=2ahUKEwityYzPzNThAhUH6qQKHR77AboQFjADegQIA RAC&url=https%3A%2F%2Fpeople.eecs.ku.edu%2F~hossein%2F811%2FLectures%2Fchapter-
10.pptx&usg=AOvVaw0B7ldXssetUgjbMWGxmkXp

Explanation/Reference:
Reference: https://www.projectmanager.com/blog/project-quality-management-quick-guide

Explanation/Reference:
Explanation:
6. Project Time Management
6.1 Plan Schedule Management

6.2 Define Activities

6.3 Sequence Activities

6.4 Estimate Activity Resources

6.5 Estimate Activity Durations

6.6 Develop Schedule

6.7 Control Schedule

Section: Volume B

Explanation/Reference:
Explanation:
11.5.2.1 Strategies for Negative Risks or Threats
Three strategies, which typically deal with threats or risks that may have negative impacts on project objectives if they occur, are: avoid, transfer, and mitigate. The fourth strategy, accept, can be used for negative risks or threats as well as positive risks or opportunities. Each of these risk response strategies have varied and unique influence on the risk condition. These strategies should be chosen to match the risk’s probability and impact on the project’s overall objectives. Avoidance and mitigation strategies are usually good strategies for critical risks with high impact, while transference and acceptance are usually good strategies for threats that are less critical and with low overall impact. The four strategies for dealing with negative risks or threats are further described as follows:
Avoid. Risk avoidance is a risk response strategy whereby the project team acts to eliminate the threat or

protect the project from its impact. It usually involves changing the project management plan to eliminate the threat entirely. The project manager may also isolate the project objectives from the risk’s impact or change the objective that is in jeopardy. Examples of this include extending the schedule, changing the strategy, or reducing scope. The most radical avoidance strategy is to shut down the project entirely. Some risks that arise early in the project can be avoided by clarifying requirements, obtaining information, improving communication, or acquiring expertise.
Transfer. Risk transference is a risk response strategy whereby the project team shifts the impact of a

threat to a third party, together with ownership of the response. Transferring the risk simply gives another party responsibility for its management-it does not eliminate it. Transferring does not mean disowning the risk by transferring it to a later project or another person without his or her knowledge or agreement. Risk transference nearly always involves payment of a risk premium to the party taking on the risk. Transferring liability for risk is most effective in dealing with financial risk exposure. Transference tools can be quite diverse and include, but are not limited to, the use of insurance, performance bonds, warranties, guarantees, etc. Contracts or agreements may be used to transfer liability for specified risks to another party. For example, when a buyer has capabilities that the seller does not possess, it may be prudent to transfer some work and its concurrent risk contractually back to the buyer. In many cases, use of a cost- plus contract may transfer the cost risk to the buyer, while a fixed-price contract may transfer risk to the seller.
Mitigate. Risk mitigation is a risk response strategy whereby the project team acts to reduce the

probability of occurrence or impact of a risk. It implies a reduction in the probability and/or impact of an adverse risk to be within acceptable threshold limits. Taking early action to reduce the probability and/or impact of a risk occurring on the project is often more effective than trying to repair the damage after the risk has occurred. Adopting less complex processes, conducting more tests, or choosing a more stable supplier are examples of mitigation actions. Mitigation may require prototype development to reduce the risk of scaling up from a bench-scale model of a process or product. Where it is not possible to reduce probability, a mitigation response might address the risk impact by targeting linkages that determine the severity. For example, designing redundancy into a system may reduce the impact from a failure of the original component.
Accept. Risk acceptance is a risk response strategy whereby the project team decides to acknowledge

the risk and not take any action unless the risk occurs. This strategy is adopted where it is not possible or cost-effective to address a specific risk in any other way. This strategy indicates that the project team has decided not to change the project management plan to deal with a risk, or is unable to identify any other suitable response strategy. This strategy can be either passive or active. Passive acceptance requires no action except to document the strategy, leaving the project team to deal with the risks as they occur, and to periodically review the threat to ensure that it does not change significantly. The most common active acceptance strategy is to establish a contingency reserve, including amounts of time, money, or resources to handle the risks.

Section: Volume E
Explanation:
5.1.3.2 Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed. The phase-to-phase relationship, described in Section 2.4.2.1, strongly influences how requirements are managed. The project manager chooses the most effective relationship for the project and documents this approach in the requirements management plan. Many of the requirements management plan components are based on that relationship.
Components of the requirements management plan can include, but are not limited to:
* How requirements activities will be planned, tracked, and reported;
* Configuration management activities such as: how changes to the product will be initiated, how impacts will be analyzed, how they will be traced, tracked, and reported, as well as the authorization levels required to approve these changes;
* Requirements prioritization process;
* Product metrics that will be used and the rationale for using them; and
* Traceability structure to reflect which requirement attributes will be captured on the traceability matrix.