Chapter 4 Flashcards
Assumptions log
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 the assumptions log for testing and analysis, and the outcomes are recorded.
Benefit/Cost Ratio (BCR) Models
An example of a benefits comparison model that examines the benefit to cost ratio.
Change control Board (CCB)
A committee that evaluates the worthiness of a proposed changes and either approved or reject the proposed change.
Change control system (CCS)
A system that communicates the process for controlling changes to the project deliverables. This system works with the configuration management system and seeks to control and document proposals to change the project product.
Change log
a log in which all changes that enter into a project are recorded. The characteristics of the change, such as the schedule, cost, risk, and scope details, are also recorded.
Change management system
a plan that details the project procedures for entertaining change request: how change requests are managed, documented, approved, or declined.
Closure processes
this final process group of the project management life cycle that is responsible for closing the project phase or project. This is where project documentation is archived and project contracts are also closed.
Communications management plan
a plan that defines who will get what information, how they will receive it, and in what modality the communication will take place.
Configuration identification
This includes the labeling of the components, how changes are made to the product, and the accountability of the changes.
Configuration management plan
a plan that 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 system
a system that defines how stakeholders are allowed to submit change request, the conditions for approving a change request, and how approved change requests are validated in the project scope. Configuration management also documents the characteristics and functions of the project products and any changes to our products characteristics.
Configuration status accounting
The organization of the product materials, details, and prior product documentation.
Configuration verification and auditing
the scope verification and completeness auditing of project or phase deliverables to ensure that they are in alignment with the project plan.
Contract closure
The formal verification of the contract completeness by the vendor and the performing organization
Cost baseline
The aggregated cost of all of the work packages within the work breakdown structure
Cost management plan
A plan that details how the project cost will be planned for, estimated, budgeted, and then monitored and controlled.