The Most In-Demand PMI CAPM Pass Guaranteed Quiz [Q44-Q61]

Section: Volume E
Explanation:
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.
Process: 11.5 Plan Risk Responses
Definition: The process of developing options and actions to enhance opportunities and to reduce threats to project objectives.
Key Benefit: The key benefit of this process is that it addresses the risks by their priority, inserting resources and activities into the budget, schedule and project management plan as needed.
Inputs
1. Risk management plan
2. Risk register
Tools & Techniques
1. Strategies for negative risks or threats
2. Strategies for positive risks or opportunities
3. Contingent response strategies
4. Expert judgment
Outputs
1. Project management plan updates
2. Project documents updates

Section: Volume D
Explanation/Reference:

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

Explanation/Reference:
Explanation:
10.1.3.1 Communications Management Plan
The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, monitored, and controlled. The plan contains the following information:
Stakeholder communication requirements;

Information to be communicated, including language, format, content, and level of detail;

Reason for the distribution of that information;

Time frame and frequency for the distribution of required information and receipt of acknowledgment or

response, if applicable;
Person responsible for communicating the information;

Person responsible for authorizing release of confidential information;

Person or groups who will receive the information;

Methods or technologies used to convey the information, such as memos, e-mail, and/or press releases;

Resources allocated for communication activities, including time and budget;

Escalation process identifying time frames and the management chain (names) for escalation of issues

that cannot be resolved at a lower staff level;
Method for updating and refining the communications management plan as the project progresses and

develops;
Glossary of common terminology;

Flow charts of the information flow in the project, workflows with possible sequence of authorization, list

of reports, and meeting plans, etc.; and
Communication constraints usually derived from a specific legislation or regulation, technology, and

organizational policies, etc.
The communications management plan can also include guidelines and templates for project status meetings, project team meetings, e-meetings, and e-mail messages. The use of a project website and project management software can also be included if these are to be used in the project.

Section: Volume D
Explanation:
Project Life Cycle. The series of phases that a project passes through from its initiation to its closure.

Section: Volume A
Explanation:
Process: 4.1. Develop Project Charter
Definition: The process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Key Benefit: The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project.
Inputs
1. Project statement of work
2. Business case
3. Agreements
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project charter
4.1.1.2 Business Case
The business case or similar document describes the necessary information from a business standpoint to determine whether or not the project is worth the required investment. It is commonly used for decision making by managers or executives above the project level. Typically, the business need and the cost-benefit analysis are contained in the business case to justify and establish boundaries for the project, and such analysis is usually completed by a business analyst using various stakeholder inputs. The sponsor should agree to the scope and limitations of the business case. The business case is created as a result of one or more of the following:
Market demand (e.g., a car company authorizing a project to build more fuel-efficient cars in response to

gasoline shortages),
Organizational need (e.g., due to high overhead costs a company may combine staff functions and

streamline processes to reduce costs.),
Customer request (e.g., an electric utility authorizing a project to build a new substation to serve a new

industrial park),
Technological advance (e.g., an airline authorizing a new project to develop electronic tickets instead of

paper tickets based on technological advances),
Legal requirement (e.g., a paint manufacturer authorizing a project to establish guidelines for handling toxic

materials),
Ecological impacts (e.g., a company authorizing a project to lessen its environmental impact), or

Social need (e.g., a nongovernmental organization in a developing country authorizing a project to provide

potable water systems, latrines, and sanitation education to communities suffering from high rates of cholera).
Each of the examples in this list may contain elements of risk that should be addressed. In the case of multiphase projects, the business case may be periodically reviewed to ensure that the project is on track to deliver the business benefits. In the early stages of the project life cycle, periodic review of the business case by the sponsoring organization also helps to confirm that the project is still aligned with the business case. The project manager is responsible for ensuring that the project effectively and efficiently meets the goals of the organization and those requirements of a broad set of stakeholders, as defined in the business case.

Explanation/Reference:
Reference: http://www.free-management-ebooks.com/faqpm/scope-06.htm

Section: Volume D

Section: Volume C