QUESTION: 61

Which process determines the risks that may affect the project and documents their characteristics?

Control Risks
Plan Risk Management
Plan Risk Responses
Identify Risks

Answer(s): D

Explanation:

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
7. Expert judgment

Outputs
1. Risk register

11.2.3.1 Risk Register
The primary output from Identify Risks is the initial entry into the risk register. The risk register is a document in which the results of risk analysis and risk response planning are recorded. It contains the outcomes of the other risk management processes as they are conducted, resulting in an increase in the level and type of information contained in the risk register over time. The preparation of the risk register begins in the Identify Risks process with the following information, and then becomes available to other project management and risk management processes:
List of identified risks. The identified risks are described in as much detail as is reasonable. A structure for describing risks using risk statements may be applied, for example, EVENT may occur causing IMPACT, or If CAUSE exists, EVENT may occur leading to EFFECT. In addition to the list of identified risks, the root causes of those risks may become more evident. These are the fundamental conditions or events that may give rise to one or more identified risks. They should be recorded and used to support future risk identification for this and other projects.
List of potential responses. Potential responses to a risk may sometimes be identified during the Identify Risks process. These responses, if identified in this process, should be used as inputs to the Plan Risk Responses process.

Reveal Solution Next Question

QUESTION: 62

An example of a group decision-ma king technique is:

Nominal group technique.
Majority.
Affinity diagram.
Multi-criteria decision analysis.

Answer(s): B

Reveal Solution Next Question

QUESTION: 63

A risk response strategy in which the project team shifts the impact of a threat, together with ownership of the response, to a third party is called:

mitigate
accept
transfer
avoid

Answer(s): C

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 inﬂuence 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.

Reveal Solution Next Question

QUESTION: 64

An output of the Plan Quality Management process is:

A process improvement plan.
Quality control measurements.
Work performance information.
The project management plan.

Answer(s): A

Explanation:

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

Tools & Techniques
1. Cost-benefit analysis
2. Cost of quality
3. Seven basic quality tools
4. Benchmarking
5. Design of experiments
6. Statistical sampling
7. Additional quality planning tools
8. Meetings

Outputs
1. Quality management plan
2. Process improvement plan
3. Quality metrics
4. Quality checklists
5. Project documents updates

Reveal Solution Next Question

Free CAPM Exam Braindumps (page: 16)

QUESTION: 61

Explanation:

QUESTION: 62

QUESTION: 63

Explanation:

QUESTION: 64

Explanation: