Explanation/Reference:
Explanation:
5.6.2.1 Variance Analysis
Variance analysis is a technique for determining the cause and degree of difference between the baseline and actual performance. Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline (Section 5.4.3.1) and deciding whether corrective or preventive action is required.
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

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.

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.

Explanation/Reference:
Explanation:
Process: 4.5 Perform Integrated Change Control
Definition: Perform Integrated Change Control is the process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating their disposition. It reviews all requests for changes or modifications to project documents, deliverables, baselines, or the project management plan and approves or rejects the changes.
Key Benefit: The key benefit of this process is that it allows for documented changes within the project to be considered in an integrated fashion while reducing project risk, which often arises from changes made without consideration to the overall project objectives or plans.
Inputs
1. Project management plan
2. Work performance reports
3. Change requests
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Meetings
3. Change control tools
Outputs
1. Approved change requests
2. Change log
3. Project management plan updates
4. Project documents updates