Latest Exam Prep

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.

Explanation/Reference:
Explanation:
Process: 5.1 Plan Scope Management
Definition: The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.
Inputs
1. Project management plan
2. Project charter
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Meetings
Outputs
1. Scope management plan
2. Requirements management plan

Explanation/Reference:
Explanation:
Process: 11.3 Perform Qualitative Risk Analysis
Definition: The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.
Key Benefit: The key benefit of this process is that it enables project managers to reduce the level of uncertainty and to focus on high-priority risks.
Inputs
1. Risk management plan
2. Scope baseline
3. Risk register
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Risk probability and impact assessment
2. Probability and impact matrix
3. Risk data quality assessment
4. Risk categorization
5. Risk urgency assessment
6. Expert judgment
Outputs
1. Project documents updates

Section: Volume D
Explanation:
6.5.2.4 Three-Point Estimating
The accuracy of single-point activity duration estimates may be improved by considering estimation uncertainty and risk. This concept originated with the program evaluation and review technique (PERT).
PERT uses three estimates to define an approximate range for an activity’s duration:
Most likely (tM). This estimate is based on the duration of the activity, given the resources likely to be

assigned, their productivity, realistic expectations of availability for the activity, dependencies on other participants, and interruptions.
Optimistic (tO). The activity duration based on analysis of the best-case scenario for the activity.

Pessimistic (tP). The activity duration based on analysis of the worst-case scenario for the activity.

Depending on the assumed distribution of values within the range of the three estimates the expected duration, tE, can be calculated using a formula. Two commonly used formulas are triangular and beta distributions.
The formulas are:
Triangular Distribution. tE = (tO + tM + tP) / 3

Beta Distribution (from the traditional PERT technique). tE = (tO + 4tM + tP) / 6

Duration estimates based on three points with an assumed distribution provide an expected duration and clarify the range of uncertainty around the expected duration.

Explanation/Reference:
Explanation:
Process: 6.4 Estimate Activity Resources
Definition: The process of estimating the type and quantities of material, human resources, equipment, or supplies required to perform each activity.
Key Benefit: The key benefit of this process is that it identifies the type, quantity, and characteristics of resources required to complete the activity which allows more accurate cost and duration estimates.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Resource calendars
5. Risk register
6. Activity cost estimates
7. Enterprise environmental factors
8. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Alternative analysis
3. Published estimating data
4. Bottom-up estimating
5. Project management software
Outputs
1. Activity resource requirements
2. Resource breakdown structure
3. Project documents updates

Explanation/Reference:
Explanation:
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: 7.1 Plan Cost Management
Definition: The process that establishes the policies, procedures, and documentation for planning, managing, expending, and controlling project costs.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how the project costs will be managed throughout the project.
Inputs
1. Project management plan
2. Project charter
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Analytical techniques
3. Meetings
Outputs
Cost management plan

Explanation/Reference:
Explanation:
Process: 5.6 Control Scope
Definition: The process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Key Benefit: The key benefit of this process is that it allows the scope baseline to be maintained throughout the project.
Inputs
1. Project management plan
2. Requirements documentation
3. Requirements traceability matrix
4. Work performance data
5. Organizational process assets
Tools & Techniques
1. Variance analysis
Outputs
1. Work performance information
2. Change requests
3. Project management plan updates
4. Project documents updates
5. Organizational process assets updates

Section: Volume E
Explanation/Reference: https://www.pmi.org/learning/library/model-risk-contingency-reserve-9310

Section: Volume E
Explanation/Reference: https://www.mindtools.com/pages/article/critical-path-analysis.htm

Explanation/Reference:
Explanation:
4.4.1.5 Work Performance Information
Work performance information is the performance data collected from various controlling processes, analyzed in context, and integrated based on relationships across areas. Thus work performance data has been transformed into work performance information. Data in itself cannot be used in the decision-making process as it has only out-of-context meaning. Work performance information, however, is correlated and contextualized, and provides a sound foundation for project decisions.
Work performance information is circulated through communication processes. Examples of performance information are status of deliverables, implementation status for change requests, and forecasted estimates to complete.
5.4.3.1 Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include:
Project scope statement. The project scope statement includes the description of the project scope,

major deliverables, assumptions, and constraints.
WBS. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project

team to accomplish the project objectives and create the required deliverables. Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information. A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to the earned value for performance measurement. Control accounts are placed at selected management points in the WBS. Each control account may include one or more work packages, but each of the work packages should be associated with only one control account. A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account with known work content but without detailed schedule activities.
WBS dictionary. The WBS dictionary is a document that provides detailed deliverable, activity, and

scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Information in the WBS dictionary may include, but is not limited to:
○ Code of account identifier,
○ Description of work,
○ Assumptions and constraints,
○ Responsible organization,
○ Schedule milestones,
○ Associated schedule activities,
○ Resources required,
○ Cost estimates,
○ Quality requirements,
○ Acceptance criteria,
○ Technical references, and
○ Agreement information

Section: Volume E
Explanation:
T&M contracts are often used for staff augmentation, acquisition of experts and any outside support when a precise statement of work is not quickly prescribed.

Section: Volume E
Explanation/Reference: https://www.google.com/url?
sa=t&rct=j&q=&esrc=s&source=web&cd=4&ved=2ahUKEwityYzPzNThAhUH6qQKHR77AboQFjADegQIARAC
&url=https%3A%2F%2Fpeople.eecs.ku.edu%2F~hossein%2F811%2FLectures%2Fchapter-
10.pptx&usg=AOvVaw0B7ldXssetUgjbMWGxmkXp

Section: Volume C
Explanation/Reference:
Explanation:
6.6.2.7 Schedule Compression
Schedule compression techniques are used to shorten the schedule duration without reducing the project scope, in order to meet schedule constraints, imposed dates, or other schedule objectives. Schedule compression techniques include, but are not limited to:
Crashing. A technique used to shorten the schedule duration for the least incremental cost by adding

resources. Examples of crashing include approving overtime, bringing in additional resources, or paying to expedite delivery to activities on the critical path. Crashing works only for activities on the critical path where additional resources will shorten the activity’s duration. Crashing does not always produce a viable alternative and may result in increased risk and/or cost.
Fast tracking. A schedule compression technique in which activities or phases normally done in sequence

are performed in parallel for at least a portion of their duration. An example is constructing the foundation for a building before completing all of the architectural drawings. Fast tracking may result in rework and increased risk. Fast tracking only works if activities can be overlapped to shorten the project duration.

Section: Volume D
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.3 Perform Qualitative Risk Analysis
Definition: The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.
Key Benefit: The key benefit of this process is that it enables project managers to reduce the level of uncertainty and to focus on high-priority risks.
Inputs
1. Risk management plan
2. Scope baseline
3. Risk register
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Risk probability and impact assessment
2. Probability and impact matrix
3. Risk data quality assessment
4. Risk categorization
5. Risk urgency assessment
6. Expert judgment
Outputs
1. Project documents updates

Section: Volume E
Explanation
Explanation:
13.1.2.1 Stakeholder Analysis
Stakeholder analysis is a technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests, expectations, and influence of the stakeholders and relates them to the purpose of the project. It also helps to identify stakeholder relationships (with the project and with other stakeholders) that can be leveraged to build coalitions and potential partnerships to enhance the project’s chance of success, along with stakeholder relationships that need to be influenced differently at different stages of the project or phase.
Stakeholder analysis generally follows the steps described below:
Identify all potential project stakeholders and relevant information, such as their roles, departments,

interests, knowledge, expectations, and influence levels. Key stakeholders are usually easy to identify. They include anyone in a decision-making or management role who is impacted by the project outcome, such as the sponsor, the project manager, and the primary customer. Identifying other stakeholders is usually done by interviewing identified stakeholders and expanding the list until all potential stakeholders are included.
Analyze the potential impact or support each stakeholder could generate, and classify them so as to define

an approach strategy. In large stakeholder communities, it is important to prioritize the stakeholders to ensure the efficient use of effort to communicate and manage their expectations.
Assess how key stakeholders are likely to react or respond in various situations, in order to plan how to

influence them to enhance their support and mitigate potential negative impacts.
There are multiple classification models used for stakeholders analysis, such as:
Power/interest grid, grouping the stakeholders based on their level of authority (“power”) and their level or

concern (“interest”) regarding the project outcomes;
Power/influence grid, grouping the stakeholders based on their level of authority (“power”) and their active

involvement (“influence”) in the project;
Influence/impact grid, grouping the stakeholders based on their active involvement (“influence”) in the project

and their ability to effect changes to the project’s planning or execution (“impact”); and Salience model, describing classes of stakeholders based on their power (ability to impose their will),

urgency (need for immediate attention), and legitimacy (their involvement is appropriate).