Chapter 4 Implementing Project Integration Management Flashcards Preview

PMP Key Terms > Chapter 4 Implementing Project Integration Management > Flashcards

Flashcards in Chapter 4 Implementing Project Integration Management Deck (58):
1

Activity attributes

Activity that have special conditions, requirements, risks, and other conditions should be documented.

2

Activity cost estimates

The cost of resources, including materials, services, and, when warranted, labor should be estimated.

3

Activity list

A shopping list of all the activities the project team must complete in order to satisfy the project. This list is an input to the project network diagram.

4

Assumption log

A document that clearly identifies and tracks assumptions that are made in the project. All assumptions need to be tested for their validity, and the outcome of the test should be recorded.

5

Benefit measurement methods

Project selection methods that compare the benefits of projects to determine which project the organization should invest its funds into.

6

Benefit/cost ratios

Shows the proportion of benefits to costs; for example 4:1 would equate to four benefits and one cost.

7

Change control board

A group of decision makers that review proposed project changes.

8

Change control system

A predefined set of activities, forms, and procedures to entertain project change requests.

9

Change log

As changes to the project time, cost, or scope enter the project, they should be recorded in the change log for future reference.

10

Change management plan

When changes are approved for a project, including time, cost, scope, or contract, there needs to be a plan on how the project team will manage these new changes within the project.

11

Communications management plan

Defines the required communications and how they will be fulfilled; explains the methods used for gathering, storing, and dispersing information to appropriate parties. In addition,mother communications management plan maps out the schedule of when the expected communication needs will be met.

12

Configuration management

The control and documentation of the project's product features and functions.

13

Constrained optimization methods

Complex mathematical models to determine the likelihood of a project's success in order to determine if the organization should invest its funds into the project.

14

Constrains

Anything that limits the project manager's options; for example, time, cost, and scope are always project constrains.

15

Contract

A legally binding agreement between the buyers and sellers that defines the roles and responsibilities of all parties in the agreement.

16

Cost management plan

Explains how variances to the costs of the project will be managed. The plan may be based on a range of acceptable variances and the expected response to variances over a given threshold.

17

Duration estimates

The prediction of how long the project work will take to complete.

18

Earned value management

A suite of formulas to measure the project's overall performance for time and costs.

19

Forecast

Throughout the project, the project manager will creat forecasts about the expected project completion is Future Value = Present Value (1+i)n, where i is the value of return and n is the number of time periods.

20

Historical information

Any information created in the past that can help the current project succeed.

21

Human resources plan

Details on how the project team members will be brought onto and released from the project.

22

Internal rate of return

A benefit measurement formula to calculate when the present value of the cash flow equals the project's original investment.

23

Issue log

Issues are decisions that are usually in disagreement among two or more parties. Issues are recorded in the issue log, along with an issue owner designation, an issue date for resolution, and the eventual outcome of the issue.

24

Lessons learned

Ongoing collection of documentation about what has and has not worked in the project; the project manager and the project team participate in lessons-learned creation.

25

Murder board

A group of decision makers that may determine to "kill" a proposed project before it is officially launched, based on the board's findings on the likelihood of the project's success.

26

Net present value

A benefit measurement formula that provides a precise measurement of the present value of each year the project generates a return on investment.

27

Payback period

The duration of time it takes a project to earn back the original investment.

28

Performance reports

These formal reports define how the project is performing on time,most, scope, quality, and any other relevant information.

29

PMIS

A project management information system is typically a software system, such as Microsoft Project, to assist the project manager in managing the project.

30

Present value

A benefit measurement formula to determine what a future amount of funds is worth today. The formula is present value = future value /(1+i)n, where I is the value of the return and n is the number of time periods.

31

Process improvement plan

Identifies method to track and eliminate waste and non-value-added activities.

32

Procurement documents

All of the documents for purchasing, such as request for quotes, invitation to quotes, invitation to bid, request for proposal, and the responses, are stored as part of the project documentation.

33

Procurement management plan

Describes the procurement process from solicitation to source selection. The plan may also include the requirements for selection as set by the organization.

34

Project baselines

Three baselines in a project are used to measure project performance: cost, schedule, and scope.

35

Project charter

A document that authorizes the project, defines the high-level requirements,n identifies the project manager and the project sponsor, and provides initial information about the project.

36

Project funding requirements

In large projects, this document identifies the timeline of when capital is required for the project to move forward. This document defines the amount of funds a project needs and when the project funds are needed in order to reach its objectives.

37

Project integration management

One of nine knowledge areas that is responsible for coordinating the efforts of the other eight knowledge areas.

38

Project plan

A comprehensive document comprised of several subsidiary plans that communicates the intent and direction of the project.

39

Proposals

Proposals are an exposé on ideas, suggestions, recommendations, and solutions to an opportunity provided by a vendor for a seller. Proposals include a price for the work and document how the vendor would provide the service to the buyer.

40

Quality management plan

Details the quality improvement, quality controls, and how the project will map to the quality assurance program of the performing organization.

41

Requirements traceability matrix

A table that identifies all of the project requirements, when the requirements are due, when the requirements are created, and any other pertinent information about the requirements.

42

Resource breakdown structure

This chart identifies the resources utilized in the project in each section of the WBS.

43

Resource calendar

You'll need to know when people and facilities are available or scheduled to work on the project.

44

Resource requirements

The identification of what resources are needed to complete the project work is needed as a supporting document for planning. This includes people, materials, equipment, facilities, and services.

45

Responsibility assignment matrix

This is a table that maps roles to responsibilities in the project.

46

Risk management plan

Details the identified risks within the project, the risks associated with the constrains and project assumptions, and how the project team will monitor, react, or avoid the risks.

47

Risk register

A risk is an uncertain event or condition that can have appositive or negative effect on the project. All risks, regardless of their probability or impact, are recorded in the issue log and their status is kept current.

48

Roles and responsibilities

Maps project roles to responsibilities within the project; roles are positions on the project team, and responsibilities are project activities.

49

Schedule management plan

Identifies circumstances that may change the project schedule, such as the completion of project phases or the reliance on other projects and outside resources. The schedule management plan details the approval and accountability process for changes within the project.

50

Scope management plan

Details how the project scope should be maintained and protected from change, as well as how a change in scope may be allowed.

51

Scoring models

A project selection method that assigns categories and corresponding values to measure a project's worthiness of investment.

52

Seller list

A listing of the vendors an organization does business with. You might know this document as a preferred vendors list in your company.

53

Source selection criteria

A predefined listing of the criteria to determine how a vendor will be selected - for example, cost, experience, certifications, and the like.

54

Statement of work

A document that defines the project work that is to be completed internally or by a vendor.

55

Supporting detail for estimates

The project manager should document how time and cost estimates were created.

56

Teaming agreement

A contractual agreement that defines the roles, responsibilities, considerations, and partnerships or two or more organizations that work together in a project. It's not unlike a partnership or subcontractor relationship.

57

Work performance information

The current status of the project work; includes the results of activities, corrective and preventive action status, forecasts for activity completion, and other relevant information.

58

Work performance measurements

These are predefined metrics for measuring project performance, such as cost variances, schedule variances, and estimate to complete.