Section: Volume D
Explanation:
A rough order of magnitude (ROM) estimate is the least accurate estimate. A Guide to the Project Management Body of Knowledge (The PMBOK Guide), 5th Edition gives the guidelines that ROMs are -50% to +50% accurate, the PMBOK Guide 5th Edition gives the guidelines that ROMs are -25% to +75% accurate, or potentially even larger. It should be noted that stated percentages are not the main takeaway are not likely specifically tested on; it is more the concept and idea that ROMs are a rough estimate, are used early in the project when info is limited, and are hence the least accurate.

Section: Volume E
Explanation:
4.2.1.1 Project Charter
Described in Section 4.1.3.1. The size of the project charter varies depending on the complexity of the project and the information known at the time of its creation. At a minimum, the project charter should define the high- level boundaries of the project. The project team uses the project charter as the starting point for initial planning throughout the Initiating Process Group.
4.1.3.1 Project Charter
The project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It documents the business needs, assumptions, constraints, the understanding of the customer's needs and high-level requirements, and the new product, service, or result that it is intended to satisfy, such as:
Project purpose or justification,

Measurable project objectives and related success criteria,

High-level requirements,

Assumptions and constraints,

High-level project description and boundaries,

High-level risks,

Summary milestone schedule,

Summary budget,

Stakeholder list,

Project approval requirements (i.e., what constitutes project success, who decides the project is successful,

and who signs off on the project),
Assigned project manager, responsibility, and authority level, and

Name and authority of the sponsor or other person(s) authorizing the project charter.

Process: 4.2. Develop Project Management Plan
Definition: The process of defining, preparing, and coordinating all subsidiary plans and integrating them into a comprehensive project management plan. The project's integrated baselines and subsidiary plans may be included within the project management plan.
Key Benefit: The key benefit of this process is a central document that defines the basis of all project work.
Inputs
1. Project charter
2. Outputs from other processes
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project management plan
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.

Section: Volume D

Section: Volume C
Explanation
Explanation:
2.1.4 Organizational Process Assets
Organizational process assets are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. The process assets also include the organization's knowledge bases such as lessons learned and historical information.
Organizational process assets may include completed schedules, risk data, and earned value data.
Organizational process assets are inputs to most planning processes. Throughout the project, the project team members may update and add to the organizational process assets as necessary. Organizational process assets may be grouped into two categories: (1) processes and procedures, and (2) corporate knowledge base.
Process: 5.3 Define Scope
Definition: The process of developing a detailed description of the project and product.
Key Benefit: The key benefit of this process is that it describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.
Inputs
1. Scope management plan
2. Project charter
3. Requirements documentation
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Product analysis
3. Alternatives generation
4. Facilitated workshops
Outputs
1. Project scope statement
2. Project documents updates