Chapter 4- Project Integration Management Flashcards
Assumption 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 assumption log for testing and analysis, and the outcomes are recorded.
Benefit/Cost BCR ratio
This is an example of a benefits comparison model. It examines the benefit-to-cost ratio.
Change control board CCB
A committee that evaluates the worthiness of proposed change and either approves or disapproves.
Change control system CCS
The change control system communicates the process for controlling changes to the project deliverables. This system works with configuration management system and seeks to control and document proposals to change the project’s product.
Change log
All changes that enter into a project are recorded in the change log. The characteristics of the change, such as the time, cost, risk, and scope details, are also recorded.
Change management plan
This plan details the project procedures for entertaining change requests; how requests are managed, documented, approved, or declined
Closure processes
This final process group of the project management lice cycle and responsible for closing the project phase or project. This is where project documentation is archived and project contracts are also closed.
Communications management plan
This plan defines who will get what information, how they will receive it, and in what modality the communication with take place.
Configuration identification
This includes the labelling of the components, how changes are made to the product, and the accountability of the changes.
Configurations management plan
This plan is an input to the control scope process. It defines how the changes to the features and functions of the project deliverable, the product scope, may enter the project.
Configuration management system
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. Configurations management also documents the characteristic and functions of the project’s products and any changes to a product’s characteristics/
Configuration status accounting
The organisation of the product material, 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 organisation
Cost baseline
This is an aggregated costs of all of the work packages within the work breakdown structure. WBS
Cost management plan
This plan details how the project costs will be planned for, estimated, budgeted and then monitored and controlled.
Enterprise environmental factors
The culture, structure, standards, regulations, organisational logistics, and other organisational characteristics that influence how a project operates.
Future value
A benefit comparison model to determine a future value of money.
Human resource plan
The plan defines how project team member will be brought onto the project team, managed and released from the project team. It also defines team training, safety issues, roles and responsibilities, and how the project’s reward and recognition system will operate.
Integrated change control
A process to consider and control the impact of the proposed change on the project’s knowledge areas.
Issue log
Issues are points of contention where some question of the project’s direction need to be resolved. All identified issues are documented in the issue log, along with an issue owner and a deadline to resolved the issue. The outcome of the issue is also recorded.