Free certification test prep

Section: Volume C
Explanation:
7.3.3.1 Cost Baseline
The cost baseline is the approved version of the time-phased project budget, excluding any management reserves, which can only be changed through formal change control procedures and is used as a basis for comparison to actual results. It is developed as a summation of the approved budgets for the different schedule activities.
Process: 7.3 Determine Budget
Definition: The process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline.
Key Benefit: The key benefit of this process is that it determines the cost baseline against which project performance can be monitored and controlled.
Inputs
1. Cost management plan
2. Scope baseline
3. Activity cost estimates
4. Basis of estimates
5. Project schedule
6. Resource calendars
7. Risk register
8. Agreements
9. Organizational process assets
Tools & Techniques
1. Cost aggregation
2. Reserve analysis
3. Expert judgment
4. Historical relationships
5. Funding limit reconciliation
Outputs
1. Cost baseline
2. Project funding requirements
3. Project documents updates

Section: Volume E

Section: Volume D
Explanation:
5.2.3.2 Requirements Traceability Matrix
The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing changes to the product scope.
Tracing includes, but is not limited to, tracing requirements for the following:
Business needs, opportunities, goals, and objectives;

Project objectives;

Project scope/WBS deliverables;

Product design;

Product development;

Test strategy and test scenarios; and

High-level requirements to more detailed requirements.

Attributes associated with each requirement can be recorded in the requirements traceability matrix. These attributes help to define key information about the requirement. Typical attributes used in the requirements traceability matrix may include: a unique identifier, a textual description of the requirement, the rationale for inclusion, owner, source, priority, version, current status (such as active, cancelled, deferred, added, approved, assigned, completed), and status date. Additional attributes to ensure that the requirement has met stakeholders’ satisfaction may include stability, complexity, and acceptance criteria.
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 D
Explanation
Explanation:
11.4.2.2 Quantitative Risk Analysis and Modeling Techniques
Commonly used techniques use both event-oriented and project-oriented analysis approaches, including:
* Sensitivity analysis. Sensitivity analysis helps to determine which risks have the most potential impact on the project. It helps to understand how the variations in project’s objectives correlate with variations in different uncertainties. Conversely, it examines the extent to which the uncertainty of each project element affects the objective being studied when all other uncertain elements are held at their baseline values.

Explanation/Reference:
Explanation:
11 PROJECT RISK MANAGEMENT
[..]
Organizations perceive risk as the effect of uncertainty on projects and organizational objectives.
Organizations and stakeholders are willing to accept varying degrees of risk depending on their risk attitude. The risk attitudes of both the organization and the stakeholders may be influenced by a number of factors, which are broadly classifed into three themes:
Risk appetite, which is the degree of uncertainty an entity is willing to take on in anticipation of a reward.

Risk tolerance, which is the degree, amount, or volume of risk that an organization or individual will

withstand.
Risk threshold, which refers to measures along the level of uncertainty or the level of impact at which a

stakeholder may have a specific interest. Below that risk threshold, the organization will accept the risk.
Above that risk threshold, the organization will not tolerate the risk.
For example, an organization’s risk attitude may include its appetite for uncertainty, its threshold for risk levels that are unacceptable, or its risk tolerance at which point the organization may select a different risk response.
Positive and negative risks are commonly referred to as opportunities and threats. The project may be accepted if the risks are within tolerances and are in balance with the rewards that may be gained by taking the risks. Positive risks that offer opportunities within the limits of risk tolerances may be pursued in order to generate enhanced value. For example, adopting an aggressive resource optimization technique is a risk taken in anticipation of a reward for using fewer resources.

Section: Volume A
Explanation:
13.2 Plan Stakeholder Management
Definition: Stakeholder Management is the process of developing appropriate management strategies to effectively engage stakeholders throughout the project life cycle, based on the analysis of their needs, interests, and potential impact on project success.
Key Benefit: The key benefit of this process is that it provides a clear, actionable plan to interact with project stakeholders to support the project’s interests.
Inputs
1. Project management plan
2. Stakeholder register
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Meetings
3. Analytical techniques
Outputs
Stakeholder management plan

Project documents updates

5.2.1.5 Stakeholder Register
Described in Section 13.1.3.1. The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project.
13.1.3.1 Stakeholder Register
The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related to the identified stakeholders including, but not limited to:
Identification information. Name, organizational position, location, role in the project, contact information;

Assessment information. Major requirements, main expectations, potential influence in the project, phase

in the life cycle with the most interest; and
Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.

The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change- or new ones identified-throughout the life cycle of the project.

Explanation/Reference:
Explanation:
6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required

or inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested.
Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.
Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic,

preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for modification or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and

non-project activities. These dependencies are usually outside the project team’s control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project

activities and are generally inside the project team’s control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.

Section: Volume E