A
B
C
D
E
100
Generating, gathering, and disseminating information to formalize phase or project completion.
Administrative Closure
100
Factors which for planning purposes can be considered to be true, real, or certain without proof or demonstration.
Assumptions
100
Identifying, documenting, approving or rejecting, and controlling changes to project baselines.
Change Control
100
Focused on the specification of both the deliverables and the process.
Configuration Control
100
Providing the basis from which the configuration of products is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
Configuration Identification
200
Defines and controls changes to project deliverables. Any documented procedure used to apply technical and administrative direction and surveillance to: define and document characteristics of a system; control changes; record and report changes; ensure conformance to requirements.
Configuration management
200
Capturing, storing and accessing configuration information needed to manage products and product information effectively.
Configuration Status Accounting
200
Establishing that the performance and functional requirements defined in the configuration documentation have been met.
Configuration Verification and Auditing
200
The state, quality, or sense of being restricted to a given course of action or inaction. An applicable restriction or limitation, either internal or external to the project, which will affect the performance of a project, program, portfolio or process.
Constraint
200
A management methodology for integrating scope, schedule, and resources, and for objectively measuring project performance and progress. It compares the amount of work that was planned, versus actually earned, versus actually spent, to determine if cost and schedule performance are as planned.
Earned Value Management (EVM)
300
Making trade-offs among competing objectives and alternatives.
Integration
300
The learning gained from the process of performing the project (may be identified at any point)
Lessons Learned
300
A document issued by project initiator or sponsor that formally authorizes the existence of a project, and provides the project manager the authority to apply organizational resources to project activities.
Project Charter
300
Tools and techniques used to gather, integrate, and disseminate the outputs of the project management processes. It is used to support all aspects of the project from initiating through closing, and include both manual and automated systems.
Project Management Information System (PMIS)
300
Description of project scope including deliverables, objectives, assumptions and constraints, and a statement of work that provides a documented basis for making future decisions and for confirming or developing a common understanding of project scope among the stakeholders.
Scope Statement
400
Sustained mental or physical effort to overcome obstacles and achieve an objective.
Project Work
400
A subsystem of the overall Project Management System. It is a formal collection of formal documented procedures that defines how work will be authorized to ensure is it done by the identified organization, at the right time, and in the proper sequence. Includes steps, documents, tracking systems, and defined approval levels
Work Authorization System (WAS)
400
Detailed data collected about deliverables during execution, valuable for monitoring and controlling the project
Work Performance Data (WPD)
400
taking proactive steps to ensure that the work completed is in line with the Project Management Plan
Preventative Action
400
Collection of formal documented procedures used to apply technical & administrative direction & surveillance to identify & document the function & physical characteristics of a product, result, service, or component
Configuration Management System (CMS)
500
Integrated subsystem of the CMS that describes procedures for identifying, documenting, and controlling changes to the project plan and the project and product baselines
Change Control System
500
Process of reviewing all change requests, approving changes, and managing changes to deliverables, OPAs, project documents, and the project management plan; and communicating their disposition
Perform Integrated Change Control (PICC)
500
Process of finalizing all activities across all of the Project Management Process Groups to formally complete the project or phase
Close Project or Phase
500
Unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project
Deliverable
500
Process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority (ONLY PM authority) to apply organizational resources to project activities
Develop Project Charter
M
e
n
u