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).

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.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

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