Free Cram & Latest Exams Dumps

Section: Volume E
Explanation:
1.4.2 Portfolio Management
A portfolio refers to projects, programs, subportfolios, and operations managed as a group to achieve strategic objectives. The projects or programs of the portfolio may not necessarily be interdependent or directly related.
For example, an infrastructure firm that has the strategic objective of “maximizing the return on its investments” may put together a portfolio that includes a mix of projects in oil and gas, power, water, roads, rail, and airports.
From this mix, the firm may choose to manage related projects as one program. All of the power projects may be grouped together as a power program. Similarly, all of the water projects may be grouped together as a water program.
Thus, the power program and the water program become integral components of the enterprise portfolio of the infrastructure firm.

Section: Volume B
Explanation:
5.2.3.1 Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project.
Requirements may start out at a high level and become progressively more detailed as more about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing an executive summary, detailed descriptions, and attachments.
Components of requirements documentation can include, but, are not limited to:
Business requirements, including:

○ Business and project objectives for traceability;
○ Business rules for the performing organization; and
○ Guiding principles of the organization
* Stakeholder requirements, including:
○ Impacts to other organizational areas;
○ Impacts to other entities inside or outside the performing organization; and
○ Stakeholder communication and reporting requirements.
* Solution requirements, including:
○ Functional and nonfunctional requirements;
○ Technology and standard compliance requirements;
○ Support and training requirements;
○ Quality requirements; and
○ Reporting requirements, etc. (solution requirements can be documented textually, in models, or both).
Project requirements, such as:

○ Levels of service, performance, safety, compliance, etc.; and
○ Acceptance criteria.
Transition requirements.

Requirements assumptions, dependencies, and constraints.

Section: Volume C
Explanation:
11.1.3.1 Risk Management Plan
The risk management plan is a component of the project management plan and describes how risk management activities will be structured and performed. The risk management plan includes the following:
Methodology. Defines the approaches, tools, and data sources that will be used to perform risk

management on the project.
Roles and responsibilities. Defines the lead, support, and risk management team members for each type

of activity in the risk management plan, and clarifies their responsibilities.
Budgeting. Estimates funds needed, based on assigned resources, for inclusion in the cost baseline and

establishes protocols for application of contingency and management reserves.
Timing. Defines when and how often the risk management processes will be performed throughout the

project life cycle, establishes protocols for application of schedule contingency reserves, and establishes risk management activities for inclusion in the project schedule.

Section: Volume E

Explanation/Reference:
Explanation:
CPI = EV / AC

Section: Volume E

Section: Volume E
Explanation
Explanation:
Process: 6.2 Define Activities
Definition: The process of identifying and documenting the specific actions to be performed to produce the project deliverables.
Key Benefit: The key benefit of this process is to break down work packages into activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling the project work.
Inputs
1. Schedule management plan
2. Scope baseline
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Decomposition
2. Rolling wave planning
3. Expert judgment
Outputs
1. Activity list
2. Activity attributes
3. Milestone list

Explanation/Reference:
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.

Section: Volume B

Section: Volume E
Explanation/Reference: https://www.projectmanagement.com/blog-post/38075/The-Orchestra-Conductor-of-Projects

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

Explanation/Reference:
Explanation:
4.1.2.1 Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources, including:
Other units within the organization,

Consultants,

Stakeholders, including customers or sponsors,

Professional and technical associations,

Industry groups,

Subject matter experts (SME), and

Project management office (PMO).