Project Integration Management Flashcards

1
Q

What are the seven project management processes in the Project Integration Management knowledge area and the inputs, tools, techniques, and outputs (ITTOs) for each process?

A

Develop Project Charter
Develop Project Management Plan
Direct and Manage Project Work
Manage Project Knowledge
Monitor and Control Project Work
Perform Integrated Change Control
Close Project or Phase

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

What are the processes and activities included in Project Integration Management and the project manager’s role in implementing those processes and activities?

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

What are the methods, concepts, and procedures for integrating and managing projects and their potential changes?

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

The process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

A

Develop Project Charter

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

The process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan

A

Develop Project Management Plan

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

The process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan

A

Direct and Mange Project Work

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

The process of using existing knowledge and creating new knowledge to achieve the project’s objectives and contribute to organizational learning.

A

Manage Project Knowledge

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

The process of tracking, reviewing, and reporting overall progress to meet the performance objectives defined in the project management plan.

A

Monitor and Control Project Work

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

The process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating the decisions.

A

Perform integrated Change Control

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

The process of finalizing all activities for the project, phase, or contract.

A

Close Project or Phase

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

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.

A

Assumption log

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

This is an example of a benefits comparison model. It examines the benefit-to-cost ratio.

A

Benefit/cost ratio (BCR) models

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

A committee that evaluates the worthiness of a proposed change and either approves or rejects the proposed change.

A

Change control board (CCB)

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

The change control system 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’s product.

A

Change control system (CCS)

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

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.

A

Change log

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

This plan details the project procedures for entertaining change requests: how change requests are managed, documented, approved, or declined.

A

Change management plan

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

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.

A

Closure processes

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

This plan defines who will get what information, how they will receive it, and in what modality the communication will take place.

A

Communications management plan

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

This includes the labeling of the components, how changes are made to the product, and the accountability of the changes.

A

Configuration identification

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

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.

A

Configuration management plan

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

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. Configuration management also documents the characteristics and functions of the project’s products and any changes to a product’s characteristics.

A

Configuration management system

22
Q

The organization of the product materials, details, and prior product documentation.

A

Configuration status accounting

23
Q

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

A

Configuration verification and auditing

24
Q

The formal verification of the contract completeness by the vendor and the performing organization.

A

Contract closure

25
Q

This is the aggregated costs of all of the work packages within the work breakdown structure (WBS).

A

Cost baseline

26
Q

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

A

Cost management plan

27
Q

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

A

Explicit knowledge

28
Q

A benefit comparison model to determine a future value of money. The formula to calculate future value is FV = PV(1 + I)n, where PV is present value, I is the given interest rate, and n is the number of periods.

A

Future value

29
Q

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

A

Integrated change control

30
Q

Issues are points of contention where some question of the project’s direction needs to be resolved. All identified issues are documented in the issue log, along with an issue owner and a deadline to resolve the issue. The outcome of the issue is also recorded.

A

Issue log

31
Q

A project selection method to determine the likelihood of success. These models include linear programming, nonlinear programming, dynamic programming, integer programming, and multiobjective programming.

A

Mathematical model

32
Q

Milestones are significant points or events in the project’s progress that represent accomplishment in the project. Projects usually create milestones as the result of completing phases within the project.

A

Milestone

33
Q

This list details the project milestones and their attributes. It is used for several areas of project planning, but also helps determine how quickly the project may be achieving its objectives.

A

Milestone list

34
Q

These are committees that ask every conceivable negative question about the proposed project. Their goals are to expose the project’s strengths and weaknesses, and to kill the project if it’s deemed unworthy for the organization to commit to. Also known as project steering committees or project selection committees.

A

Murder boards

35
Q

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

A

Net present value

36
Q

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

A

Payback period

37
Q

A benefit comparison model to determine the present value of a future amount of money. The formula to calculate present value is PV = FV ÷ (1 + I)n, where FV is future value, I is the given interest rate, and n is the number of periods.

A

Present value

38
Q

The procurement management plan controls how the project will acquire goods and services.

A

Procurement management plan

39
Q

This document authorizes the project. It defines the initial requirements of the project stakeholders. The project charter is endorsed by an entity outside of the project boundaries.

A

Project charter

40
Q

The documented approach of how a project will be planned, executed, monitored and controlled, and then closed. This document is a collection of subsidiary management plans and related documents.

A

Project management plan

41
Q

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

A

Project scope management plan

42
Q

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

A

Quality baseline

43
Q

This plan defines what quality means for the project, how the project will achieve quality, and how the project will map to organizational procedures pertaining to quality.

A

Quality management plan

44
Q

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

A

Regression analysis

45
Q

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

A

Risk management plan

46
Q

The risk register is a centralized database consisting of the outcome of all the other risk management processes, such as the outcome of risk identification, qualitative analysis, and quantitative analysis.

A

Risk register

47
Q

This subsidiary plan defines the risk responses that are to be used in the project for both positive and negative risks.

A

Risk response plan

48
Q

This is the planned start and finish of the project. The comparison of what was planned and what was experienced is the schedule variance.

A

Schedule baseline

49
Q

Defines how the project schedule will be created and managed.

A

Schedule management plan

50
Q

The scope baseline is a combination of three project documents: the project scope statement, the work breakdown structure, and the WBS dictionary. The creation of the project deliverable will be measured against the scope baseline to show any variances from what was expected and what the project team has created.

A

Scope baseline

51
Q

These models use a common set of values for all of the projects up for selection. For example, values can be profitability, complexity, customer demand, and so on.

A

Scoring models

52
Q

Knowledge that’s more difficult to express because it’s personal beliefs, values, knowledge gain from experience, and “know-how” when doing a task.

A

tacit knowledge