Section: Volume E
Explanation/Reference:

Section: Volume E
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

Section: Volume D
Explanation:
Control charts, are used to determine whether or not a process is stable or has predictable performance.
Upper and lower specification limits are based on requirements of the agreement. They reflect the maximum and minimum values allowed. There may be penalties associated with exceeding the specification limits. Upper and lower control limits are different from specification limits. The control limits are determined using standard statistical calculations and principles to ultimately establish the natural capability for a stable process. The project manager and appropriate stakeholders may use the statistically calculated control limits to identify the points at which corrective action will be taken to prevent unnatural performance. The corrective action typically seeks to maintain the natural stability of a stable and capable process. For repetitive processes, the control limits are generally set at ±3 s around a process mean that has been set at 0 s. A process is considered out of control when: (1) a data point exceeds a control limit; (2) seven consecutive plot points are above the mean; or (3) seven consecutive plot points are below the mean. Control charts can be used to monitor various types of output variables.
Although used most frequently to track repetitive activities required for producing manufactured lots, control charts may also be used to monitor cost and schedule variances, volume, and frequency of scope changes, or other management results to help determine if the project management processes are in control.

Section: Volume E
Explanation/Reference: https://pmstudycircle.com/2012/06/stakeholder-register-project-management/

Section: Volume C

Section: Volume C
Explanation:
8.2.2.2 Quality Audits
A quality audit is a structured, independent process to determine if project activities comply with organizational and project policies, processes, and procedures. The objectives of a quality audit may include:
Identify all good and best practices being implemented;

Identify all nonconformity, gaps, and shortcomings;

Share good practices introduced or implemented in similar projects in the organization and/or

industry;
Proactively offer assistance in a positive manner to improve implementation of processes to help the team

raise productivity; and
Highlight contributions of each audit in the lessons learned repository of the organization.

The subsequent effort to correct any defciencies should result in a reduced cost of quality and an increase in sponsor or customer acceptance of the project’s product. Quality audits may be scheduled or random, and may be conducted by internal or external auditors.
Quality audits can confirm the implementation of approved change requests including updates, corrective actions, defect repairs, and preventive actions.
8.2.2.3 Process Analysis
Process analysis follows the steps outlined in the process improvement plan to identify needed improvements.
This analysis also examines problems experienced, constraints experienced, and non-value-added activities identified during process operation. Process analysis includes root cause analysis-a specific technique used to identify a problem, discover the underlying causes that lead to it, and develop preventive actions.

Section: Volume E

Section: Volume A
Explanation
Explanation:
Knowledge Areas
1. 4. Project Integration Management
2. 5. Project Scope Management
3. 6. Project Time Management
4. 7. Project Cost Management
5. 8. Project Quality Management
6. 9. Project Human Resource Management
7. 10.Project Communications Management
8. 11.Project Risk Management
9. 12.Project Procurement Management
10.13.Project Stakeholder Management
Planning Process Group
4.2 Develop Project Management Plan
5.1 Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
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
7.1 Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
8.1 Plan Quality Management
9.1 Plan Human Resource Management
10.1 Plan Communications Management
11.1 Plan Risk Management
11.2 Identify Risks
11.3 Perform Qualitative Risk Analysis
11.4 Perform Quantitative Risk Analysis
11.5 Plan Risk Responses
12.1 Plan Procurement Management
13.2 Plan Stakeholder Management