4 Project Integration Management Terms Flashcards
An assumption is something that is believed to be true or false, but it has not yet been proven to be true or false. Assumptions that prove wrong can become risks for the project. All identified project assumptions are recorded in this document for testing and analysis, and the outcomes are recorded.
Assumption log
This is an example of a benefits
comparison model. It examines the
benefit-to-cost.
Benefit/cost ratio (BCR) models
A committee that evaluates the
worthiness of a proposed change and
either approves or rejects the proposed
change.
Change control board (CCB)
Communicates the process for controlling
changes to the project deliverables. This
system works and alongside with the configuration
management system and seeks to control
and document proposals to change the
project’s product.
Change control system (CCS)
All changes that enter into a project are
recorded in this document. The
characteristics of the change, such as the
time, cost, risk, and scope details, are
also recorded.
Change log
This plan details the project procedures
for entertaining change requests: how
change requests are managed,
documented, approved, or declined.
Change management plan
This final process group of the project management life cycle is responsible for closing the project phase or project. This is where project documentation is archived and project contracts are also closed.
Closure processes
This plan defines who will get what
information, how they will receive it, and
in what modality the communication will
take place
Communications management plan
This includes the labeling of the
components, how changes are made to
the product, and the accountability of the
changes
Configuration identification
This plan is an input to the control scope
process. It defines how changes to the
features and functions of the project
deliverable, the product scope, may enter
the project.
Configuration management plan
This system defines how stakeholders are allowed to submit change requests, the conditions for approving a change request, and how approved change requests are validated in the project scope. Also documents the characteristics and functions of the project’s products and any changes to a product’s characteristics.
Configuration management system
The organization of the product materials,
details, and prior product documentation.
Configuration status accounting
The scope verification and completeness
auditing of project or phase deliverables
to ensure that they are in alignment with
the project plan.
Configuration verification and auditing
The formal verification of the contract
completeness by the vendor and the
performing organization.
Contract closure
This is the aggregated costs of all of the work packages within the work breakdown structure (WBS).
Cost baseline
This plan details how the project costs
will be planned for, estimated, budgeted,
and then monitored and controlled.
Cost management plan