Chapter 4 - Integration Management Flashcards

1
Q

Primary role of PM

A

Perform integration management

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

Integration management

A

Pulling all the pieces of a project, i.e., knowledge areas, together into a cohesive whole

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

Why is it important to know a project’s history in order to manage it effectively, and achieve aspired results?

A
  • The reason a project is selected and the value it is expected to bring indicate its signifcance to the company
  • The PM needs to know if the project was selected because it will establish a new area of business, if it’s being implemented to meet compliance requirements, least expensive, etc.
  • The reason a project was selected can impact which constraints are most flexible, and knowing this info will influence how the PM plans and manages the project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Benefit measurement methods

A

Comparative project selection approach. Examples include:

  • Murder board (panel of people who try to shoot down a new project idea)
  • Peer review
  • Scoring models
  • Economic measures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Constrained optimization methods

A

Mathematical project selection approach. Examples include:

  • Linear programming
  • Integer programming
  • Dynamic programming
  • Multiobjective programming
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Return On Investment (ROI)

A

Calculation of benefits received in relation to the cost

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

Present Value (PV) definition

A
  • The value today of future cash flows
  • Do NOT confuse with Planned Value (PV)
  • If the question is discussing how the project was evluated for selection/funding, PV represents present value
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Present Value (PV) Formula

A

PV = FV / (1+r)<em>n</em>

  • FV = Future Value
  • r = interest rate
  • n = number of time periods
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Net Present Value (NPV) Definition

A
  • Present value of the total benefits (income or revenue) minus the costs over many time periods
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

NPV > 1: should we invest?

A

Investment is a good choice because NPV is greater than 1

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

NPV < 1: should we invest?

A

Investment is a bad choice because NPV is less than 1

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

Given more than one NPV choice, how do you know which project to select?

A

Choose the NPV with the highest value

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

Internal Rate of Return (IRR) Definition

A
  • The percent return the company will receive for a given project
  • The interest rateat which the projectrevenuesandcostsareequal
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Given more than one IRR choice, how do you know which project to select?

A

Choose the project with the highest IRR

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

Payback period

A

The length of time it takes for the organization to recover its investment in a project before it starts accumulating profit

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

Given more than one payback period choice, how do you know which project to select?

A

Generally speaking, go with the shorter payback period

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

Cost-benefit analysis

A
  • Analysis that compares the expected costs to the potential beenfits (revenue)
  • The analysis results in a benefit-cost ratio, which can be expressed as a decimal or a ratio
  • The ratio defined means that the benefits the project brings to the organization is X.X times the cost of the initiatives
  • Also used to determine the best solution aporoach once a project is selected
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Economic Value Added (EVA)

A
  • Concerned with whether the project returns to the company more value than the initiative costs
  • Do NOT confuse with Earned Value Analysis (EVA), which appears frequently
  • Economic Value Added rarely appears on the exam
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Opportunity cost

A
  • The opportunity given up by selecting one project over another
  • The opportunity cost is the value of the project not selected
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Sunk costs

A

Expended costs, i.e. costs that have already been incurred

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

When should sunk costs be considered?

A

NEVER!

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

Law of diminishing returns

A

After a certain point, adding more input will NOT produce a proportional increase in productivity

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

Working capital

A

An organization’s current asses minus its current liabilities, i.e., the amount of money the company has available to invest

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

Depreciation

A

Large assets, such as equipment, lose value over time

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

Straight line depreciation

A

The same amount of depreciation is taken each year

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

Accelerated depreciation

A
  • Depreciation that occurs faster than straight line

Two types:

  • Double declining
  • Sum of the years
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

What is the first part of integration management?

A

Developing a project charter

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

Business documents

A

Business documents provide critical info to the PM and team, and include information such as:

  • Why the project was undertaken
  • A summary of the realtionship between project objectives and strategic goals of the organization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Business case

A
  • Describes the business need (justification), the proposed solution, and the expected value of the change
  • Includes both tangible and intangible costs and benefits of the proposed solution
30
Q

What is the thing you need in order to select a project?

A

A business case

31
Q

Benefits management plan

A
  • A document that captures the organization’s desired benefits from a project, whether economic or intangible, and explains how those benefits will be maximized/sustained
  • Also defines metrics and processes for measuring​ a project’s benefits
32
Q

Constraints

A

Factors that limit the team’s options

33
Q

Where are assumptions and constraints initially documented?

A

As part of the business case, and highlighted in the project charter

34
Q

Assumptions

A

Things that are assumed to be true, but may not be true

35
Q

What must occur if constraints change or assumptions are proven wrong?

A

The PMP must be altered

36
Q

Who creates a project charter?

A
  • Both the buyer and the seller
  • Both charters would have different reasons for working on the project
37
Q

What does the project charter do for the PM?

A
  • Clarifies/encourages understanding of project deliverables and milestones
  • Defines the key roles and responsibilities
  • Formally authorizes existence of the project
  • Gives PM authority to spend money
  • Gives PM authority to commit resources to the project
  • Provides the objectives, high-level requirements, and success criteria for the project
  • Process of creating the charter uncovers assumptions about the project
  • Project charter links the project to the ongoing work of the organization
38
Q

Regardless of the size of the project, developing the project charter requires what actions?

A
  • Identify stakeholders
  • Meet with key stakeholders to confirm high-level requirements, project scope, risks, assumptions, and issues
  • Defining product scope
  • Defining project objectives, constraints, and success criteria
  • Documenting risks
39
Q

Assumption log

A

A list of all assumptions and constraints

40
Q

Management plans

A
  • Management plans document the strategy and approach for managing the project and processes related to the knowledge areas
  • This means there’s a management plan for each knowledge area!
41
Q

Main points to know about management plans

A
  • Management plans look forward in time
  • Management plans exist for all of the knowledge areas
42
Q

Project Management Plan (PMP)

A
  • The PMP integrates all the individual management plans into a cohesive whole, creating a centralized document to describe what is involved in the project
  • Also includes the baselines for the project
43
Q

Key components of the PMP

A
  • Project life cycle
  • Development approach
  • Management reviews
  • Project management processes that will be used
  • Knolwedge area management plans
  • Baselines
  • Requirements management plan
  • Change management plan
  • Change control system
  • Configuration management plan
  • Configuration management system
    *
44
Q

Project life cycle

A

The project life cycle describes the phases of work on a project required to produce the deliverables

45
Q

Performance measurement basline

A

Records of what the project had planned, scheduled, and budgeted for, and are used to compare the project’s actual performance against planned performance

46
Q

Elements included in the scope baseline

A
  • The project scope statement
  • WBS
  • WBS dictionary
47
Q

Elements included in the schedule baseline

A
  • Agreed-upon schedule (stop and start dates for each activity)
  • Scheduled milestones
48
Q

Elements included in the cost baseline

A
  • Time-phased cost budget (spending plan indicating how much money is approved for the project, and when the funds are required/will be available)
49
Q

What are project deviations often attributed to?sk

A

Incomplete risk identification and risk management

50
Q

Requirements management plan

A

Defines how requirements will be gathered, analyzed, prioritized, evaluated, and documented, as well as how the requirements will be managed and controlled throughout the project

51
Q

Change management plan

A

Describes how changes will be managed and controlled, i.e., who’s involved, who has authority to approve changes, how the changes will be stored and updated, outcomes of changes, etc.

52
Q

Change control system

A

Standardized forms, reports, processes, procedures, and software used to track and control changes

53
Q

Configuration management plan

A
  • A plan that informs the team what version of the scope, schedule, and other components of the PMP is the latest
  • Defines the naming conventions, version control system, and document storage/retrival system, and details how you will manage the changes to the documentation
54
Q

Project documents

A

Any project-related documents that are not part of the PMP

Examples

  • Assumption logs
  • Cost and duration estimates
  • Lessons learned register
  • Project schedule
  • Resource calendars
  • Quality reports
  • Resource requirements
  • Requirements documentation
55
Q

Project Management Information System (PMIS)

A

Used to help PM keep track of aspects of the project, and includes automated tools like:

  • Scheduling software
  • Configuration management system
  • Shared workspaces for file storage or distribution
  • Work authorization software
  • Time tracking software
  • Procurement management software
  • Repositories for historical information
56
Q

What is the purpose of a work authorization system?

A

To make sure work is only started when a formal authorization is given

57
Q

Outputs of the Direct and Manage Project Work process

A
  • New change requests
  • Deliverables
  • WPD
  • Issue logs
  • Implemented previously approved changes, preventive actions, and defect repairs
  • PMP updates
58
Q

Explicit knowledge

A

Fact-based, and can be easily communicated through words and symbols

59
Q

Tacit knowledge

A
  • Includes emotions, experience, and ability, which are more difficult to communicate clearly
  • Lessons learned fall under this category
60
Q

Lesson learned category: technical aspects

A

What was right and wrong about how we completed the work to produce the product?

61
Q

Lesson learned category: project management

A

How did we do with WBS creation, risk planning, etc.? What can be used in the future?

62
Q

Lesson learned category: management

A

How did I do with comms and leadership as a PM?

63
Q

What to do if a project activity takes longer than estimated?

A
  • Request corrective action to make up for delay
  • Do NOT ask for more time!
64
Q

Corrective action

A
  • Any action taken to bring expected future project performance in line with the PMP based on actual, current deviations
65
Q

Preventive action

A

Dealing with anticipated or possible deviations from the PMP

66
Q

Defect repair

A
  • Another way to say “rework”
  • May be requested when a component of the project does not meet specifications
67
Q

Key focus of integrated change control

A
  • Look at impact of each change on all project constraints
  • This helps to reduce risk of not fulfilling project objectives!
68
Q

What’s necessary to have when evaluating impacts of a change?

A
  • A realistic PMP to measure against
  • A complete product and project scope
69
Q

When should you implement changes? When is it costlier to implement changes?

A
  • Should implement changes as early as possible
  • Much costlier to implement changes later in the project
70
Q

What type of project does NOT have a change control board?

A

Change-driven projects

71
Q

Steps to answer questions that ask about process for making changes

A
  1. Evaluate the impact
  2. Identify options
  3. Get the change request approved internally
  4. Get customer buy-in (if required)
72
Q

Detailed process for making changes

A
  1. Prevent the root cause of the changes
  2. Identify the need for a change
  3. Evaluate the impact of a change within a knowledge area
  4. Create a change request
  5. Perform ICC by:
    • Assessing the change
    • Identifying options
    • Approving, rejecting, or derring the request
    • Updating the status of the change in the change log
    • Adjust the PMP, project docs, and baselines as necessary
  6. Manage stakeholders’ expectations by communicating chanegs to them
  7. Manage the project to the revised PMP and project docs