Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
20 Cards in this Set
- Front
- Back
Change request |
A formal written request for a change to a baseline, subsidiary plan, or formally controlled document. |
|
Preventive action |
Action required to avoid an anticipated variance to the project management plan. |
|
corrective action |
Action required to correct an existing variance to the project management plan. |
|
lessons learned |
Assessment performed by stakeholders to capture what went well and what could have been done better, in order ot improve future performance. |
|
organizational process assets |
Assets accumulated in the organization that can be used to guide and improve the project management effort. |
|
subsidiary plans |
Elements of the project management plan used to establish management rules for a specific area. |
|
enterprise environmental factors |
Elements that exist around the project and may influence its performance, such as infrastructure, organizaton structure and culture, human resources skills, and project management information system. |
|
assumption |
Factors that, although uncertain, are considered as givens for planning purposes. |
|
project charter |
Formal document that authorizes the beginning of the project and provides the project manager with the authority to apply resources to project activies. |
|
project statement of work (SOW) |
Formal document that describes the products and services that should be provided by the project. |
|
baseline |
Formally approved version of the project objectives used to assess performance. |
|
integration management |
Includes all the processes required to enxure the coordination fo the different project management knowledge areas, protecting their consistency and alignment to project constraints and stakeholders' expectations. |
|
change management plan |
Plan that sets the rules on how to manage project changes. |
|
configuration management plan |
Plan that sets the rules regarding how to identify, document, and change specific product components. |
|
historical information or data |
Project documentation accumulated byt he organization that can be used as planning inputs on future projects. |
|
constraint |
Restrictions to project management decisions that limit the available options. |
|
performance measurement baseline |
Scope, schedule, and cost baseline for the earned value management technique. |
|
project management plan |
Sets the rules regarding how the project will be managed, including which processes will be used and how they will be iplemented; also includes scope, schedule, and cost baseline. |
|
project management information systems (PMIS) |
System that includes the tools required to collect record, process, and desseminate information across project stakeholders |
|
work authorization system |
System used to authorize, formally and in writing, the start of work packages or activities |