Ch 4 Pmbok Integration Management Definitions

Front 1

Change request

Back 1

A formal written request for a change to a baseline, subsidiary plan, or formally controlled document.

Front 2

Preventive action

Back 2

Action required to avoid an anticipated variance to the project management plan.

Front 3

corrective action

Back 3

Action required to correct an existing variance to the project management plan.

Front 4

lessons learned

Back 4

Assessment performed by stakeholders to capture what went well and what could have been done better, in order ot improve future performance.

Front 5

organizational process assets

Back 5

Assets accumulated in the organization that can be used to guide and improve the project management effort.

Front 6

subsidiary plans

Back 6

Elements of the project management plan used to establish management rules for a specific area.

Front 7

enterprise environmental factors

Back 7

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.

Front 8

assumption

Back 8

Factors that, although uncertain, are considered as givens for planning purposes.

Front 9

project charter

Back 9

Formal document that authorizes the beginning of the project and provides the project manager with the authority to apply resources to project activies.

Front 10

project statement of work (SOW)

Back 10

Formal document that describes the products and services that should be provided by the project.

Front 11

baseline

Back 11

Formally approved version of the project objectives used to assess performance.

Front 12

integration management

Back 12

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.

Front 13

change management plan

Back 13

Plan that sets the rules on how to manage project changes.

Front 14

configuration management plan

Back 14

Plan that sets the rules regarding how to identify, document, and change specific product components.

Front 15

historical information or data

Back 15

Project documentation accumulated byt he organization that can be used as planning inputs on future projects.

Front 16

constraint

Back 16

Restrictions to project management decisions that limit the available options.

Front 17

performance measurement baseline

Back 17

Scope, schedule, and cost baseline for the earned value management technique.

Front 18

project management plan

Back 18

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.

Front 19

project management information systems (PMIS)

Back 19

System that includes the tools required to collect record, process, and desseminate information across project stakeholders

Front 20

work authorization system

Back 20

System used to authorize, formally and in writing, the start of work packages or activities