Chapter 4 (Project Integration Management) Flashcards

1
Q

Assumption log

A

Something that is believed to be true or false but has not been proven.
False assumptions are a risk.
Log is a location where assumptions are IDed for testing and analysis with outcomes recorded.

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

Benefit/cost ratio models

A

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

A

Committee that evaluates the worthiness of a proposed change and either approves or rejects it.

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

Change control system

A

Communicates the process for controlling changes to the project deliverables.

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

Change log

A

Location where all changes are recorded. Contains things like time, cost, risk, and scope details.

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

Change management plan

A

Procedures for how changes will be managed.

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

Closure processes

A

Final process group of the project. Project documentation is archived and project contacts 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 they will get it, and what mode of communication will take place.

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

Configuration identification

A

Labeling of the components, how changes are made to the project, 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

Input to the control scope process. Defines how changes to the 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

Defines how change requests can be submitted, conditions for approving a change, and how changes are validated in the project scope.

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. Rev control and achieving.

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 deliverables to ensure they align 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 project team.

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

Cost baseline

A

Aggregated costs of all of the work packages within the work breakdown structure.

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

Cost management plan

A

Plan that details how the project costs will be planned for, estimated, budgeted, and then monitored and controlled.

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

Explicit knowlede

A

Knowledge that can be quickly and easily expressed through conversations, documentation, figures, or numbers, is easily communicated.

18
Q

Future value

A

Benefit comparison model to determine a future value of money. FV=PV(1+i)^n

19
Q

Integrated change control

A

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

20
Q

Issues log

A

Issues are things that need to be resolved. Issues log is where they are IDed, with an owner, deadline to resolve, and outcome.

21
Q

Mathematical model

A

Project selection method to determine the likelihood of success.

  • linear programming
  • nonlinear programming
  • dynamic programming
  • integer programming
  • multi-objective programming
22
Q

Milestone

A

Significant points or events in the project’s progress that represent accomplishment in the project.

23
Q

Milestone list

A

Details project milestones and their attributes. Used for project planning and to determine how quickly the project may be achieving its objectives.

24
Q

Murder boards

A

Committee that asks negative questions about a proposed project. Goal is to expose a project’s strengths and weaknesses. Kill the project if it’s unworthy.

25
Q

Net present value

A

Evaluates the money returned for each period of a project.

26
Q

Payback period

A

Estimate of how ling it will take a project to pay back the capital invested.

27
Q

Present value

A

Determines the present value of a future amount of money.

PV=FV/(1+i)^n

28
Q

Procurement management plan

A

Controls how the project will acquire goods and services.

29
Q

Project charter

A

Authorizes the project.
Defines the initial requirements of the project.
Endorsed by an entity outside of the project team.
Usually done at the beginning but can be done multiple times.

30
Q

Project management plan

A

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

31
Q

Project scope management plan

A

Defines how the project scope will be planned, managed, and controlled.

32
Q

Quality baseline

A

Documents the quality objectives for the project, including metrics for acceptance.

33
Q

Quality management plan

A

What quality means for the project.
How the project will achieve quality.
How the project will map to organizational procedure pertaining to quality.

34
Q

Regression analysis

A

Model to examine the relationship among project variables like cost, time, labor, and other project metrics.

35
Q

Risk management plan

A

Risk is an uncertain event or condition that may affect the project outcome. The risk management plan defines how the project will manage risks.

36
Q

Risk register

A

Central database consisting of the outcome of all the other risk management processes such as risk identification, qualitative analysis, and quantitative analysis.

37
Q

Risk response plan

A

Defines the risk responses that are the be used in the project for both positive and negative risks.

38
Q

Schedule baseline

A

Planned start and finish of the project. Comparison of what was planned and what was experience is the schedule variance.

39
Q

Schedule management plan

A

Defines how the schedule will be created and managed.

40
Q

Scope baseline

A

The scope statement, work breakdown structure, and WBS dictionary. Deliverables will be measured against the scope baseline to ID variances.

41
Q

Scoring models

A

Used to compare potential projects.

42
Q

Tacit knowledge

A

Knowledge that is more difficult to express because it’s gained from experience.