4 - Project Integration Management Flashcards

1
Q

Assumption Log

A

Assumption = something believed to be true or false, but no proof yet.

Assumptions proven wrong can become risks for the project.

All assumptions recorded in Assumption Log for testing and analysis - outcomes are recorded.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Benefit/cost Ratio (BCR) Model

A

An example of a benefits comparison model.

Examines the benefit-to-cost ratio.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Change Control Board (CCB)

A

Committee that evaluates worthiness of proposed change and either approved or rejects the proposed change.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Change Control System (CCS)

A

CCS communicates the process for controlling changes to the project deliverables.

System works with configuration management system and seeks to control and document proposals to change the project’s product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Change log

A

All changes that enter a project recorded here.

Also recorded: characteristics of the change (time, cost, risk, scope details).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Change Management Plan

A

Details the project procedures for entertaining change requests:
- how change requests are managed, documented, approved, declined.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Closure Process

A

Final process group of PM life cycle - responsible for closing the project phase or project.

Project documentation is archived.
Project contracts are closed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Communications Management Plan

A

Defines who will get what info,
How it is received,
Modality of communication.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Configuration Identification (you should review configuration in the PMBOK)

A

Includes labeling of the components, how changes are made to the product, accountability of the changes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Configuration Management Plan

A

An input to control scope.

Defines how changes to the features and functions of the project deliverable and scope may enter the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Configuration Management System

A

Configuration management = managing changes to the product.

From PMBOK: a collection of procedures used to track project artifacts and monitor and control changes to these artifacts.

Defines how stakeholders are allowed to submit change requests, conditions for approval, and how it is validated - in the project scope.

Also documents characteristics and functions of the project’s products and changes to product characteristics.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Configuration Status Accounting

A

Organization of product materials, details, and prior product documentation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Configuration verification and auditing

A

Scope verification and completeness auditing of project or phase deliverables to ensure that they are in alignment with the project plan.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Contract Closure

A

Formal verification of the contract completeness by the vendor and the performing organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Cost Baseline

A

Aggregated costs of all the work packages within the work breakdown structure (WBS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Cost Management Plan

A

Details how costs will be planned for, estimated, budgeted, monitored/controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Explicit knowledge

A

Quickly and easily expressed through conversations, documentation, figures, numbers.

Easy to communicate.

18
Q

Future Value

A

FV = PV(1 + I)^n

Benefit comparison model to determine future value of money.

I = interest rate
n = number of periods
19
Q

Integrated Change Control

A

Process to consider and control the impact of a proposed change on the project’s knowledge areas.

20
Q

Issue log

A

Issue = point of contention - project direction needs to be resolved.

All issues documented in issue log. Also:

  • owner
  • deadline to resolve
  • outcome
21
Q

Mathematical Model

A

Project selection method to determine likelihood of success.

Linear/nonlinear/dynamic/integer/multiobjective programming

22
Q

Milestone

A

Significant point or event in the projects progress that represent accomplishments in the project.

Projects usually create milestones as the result of completing phases within the project.

23
Q

Milestone List

A

Details milestones and their attributes.

Used for several areas of project planning, also helps determine how quickly the project may be achieving its objectives.

24
Q

Murder boards

A

Committees that ask every conceivable negative question about the proposed project.

Goals to expose strengths and weaknesses, and kill it if needed.

AKA project steering/selection ctte.

25
Q

Net Present Value

A

Evaluates monies returned on a project for each period the project lasts.

Greater than zero is good.

Involves finding present value of each period (year), adding that up.

26
Q

Payback Period

A

Estimate to predict how long it will take project to pay back an organization for the project’s investment of capital.

27
Q

Present Value

A

Benefit Comparison Model to determine present value of a future amount of money.

PV = FV / (1 + I) ^n

FV = future value
I = Interest rate
28
Q

Procurement Management Plan

A

Controls how project will acquire goods and services

29
Q

Project Charter

A

Document that authorizes the project.

Defines initial requirements of the stakeholders. Endorsed by entity outside of the project boundaries.

30
Q

Project Management Plan

A

Documented approach of how a project will be planned, executed, monitored/controlled, closed.

Collection of subsidiary management plans and related docs.

31
Q

Project Scope Management Plan

A

Defined how scope will be planned, managed, controlled.

32
Q

Quality Baseline

A

Documents quality objectives for the project, including metrics for stakeholder acceptance of the project deliverable.

33
Q

Quality Management Plan

A

Defines what quality means for the project, how project will achieve quality, how project will map to organizational procedures pertaining to quality.

34
Q

Regression Analysis

A

Mathematical model to examine the relationship among project variables (cost, time, labor, and other metrics).

35
Q

Risk Management Plan

A

Risk is an uncertain event or condition that may affect the project outcome.

RM Plan defines how the project will manage risk

36
Q

Risk Register

A

Centralized database consisting of the outcomes of all other risk management processes, such as outcome of risk identification, qualitative/quantitative analysis.

37
Q

Risk Response Plan

A

Subsidiary plan defines risk reponses that are used for positive and negative risks.

38
Q

Schedule Baseline

A

Planned start and finish.

Comparison of baseline and actual is the schedule variance.

39
Q

Schedule Management Plan

A

Defines how schedule will be created and managed.

40
Q

Scope Baseline

A

Combination of 3 docs:

  • project scope statement
  • work breakdown structure
  • WBS dictionary

Creation of deliverable will be measured against the scope baseline to show any variances from what was expected and what the project team has created.

41
Q

Scoring Models

A

Use common set of values for all of the projects up for selection.

e.g. profitability, complexity, customer demand.

42
Q

Tacit Knowledge

A

Personal beliefs, values, lived experience, “know-how”

More difficult to express.