Integration Management Flashcards

1
Q

Key activities: Develop Project Charter

A
  • identify stakeholders
  • define scope
  • define project objectives, constraints, and success criteria
  • documenting risks
  • meet with key stakeholders (confirm high-level requirements, scope, risks, assumptions, and issues)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Inputs: Develop Project Charter

A
  • business documents (business case, benefits management plan)
  • agreements
  • OPAs
  • EEFs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Business Case Components

A
  • business need
  • why project was selected
  • how project fits into strategic goals
  • how it brings value to the organization
  • assumptions and contsraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Benefits Management Plan

A
  • identifies desired benefits from a project (economic and intangible)
  • explains how benefits will be maximized and sustained.
  • defines metrics and processes for measuring benefits
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Benefits of Project Charter

A
  • clarifies understandting re: major deliverables and milestones
  • defines key roles and responsibilities for project
  • gives PM authority to spend money
  • gives PM authority to commit resources
  • provides objectives, high-level requirements, and success criteria for project
  • links project to ongoing work of the organization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Outputs: Develop Project Charter

A
  • Project Charter
  • Assumption Log
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Project Management Plan

A

Defines how the project is executed, monitored, and controlled

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

Components of Project Management Plan

A
  1. Management plans for each knowledge area
  2. Requirements management plan
  3. Change management plan
  4. Confirguration management plan
  5. Performance measurement baselines (Scope, Schedule, Cost)
  6. Project Life Cycle description (phases)
  7. Development approach
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scope Baseline

A

scope statement, WBS, WBS dictionary

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

Schedule Baseline

A

agreed upon schedule, start and stop dates for each activity, and scheduled milestones

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

Cost Baseline

A

time-phased cost budget (indicates how much money is approved and when funds are required and available)

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

Performance Managment Baseline

A

Scope Baseline, Schedule Baseline & Cost Baseline

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

What should you do if a project deviates from established baselines?

A

Correct answer on exam is likley review the project’s risk management process.

Deviation from baselines are often due to incomplete risk identification & risk management

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

Key activities: Direct & Manage Project Work

A
  • complete activities & deliverables in project mgmt plan
  • gathering work performance data
  • creating and using the issue log
  • requesting changes
  • completing the work resulting from approved change requests
  • managing the execution of plans for the specific knowledge areas
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Requirements Management Plan

A
  • defines how requirements will be gathered, analyzed, prioritized, evaluated, and documented
  • how requirements will be managed and controlled throughout the project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Change Management Plan

A

documents how changes will be managed and controlled; includes

  • change control procedures
  • approval levels for authorizing challenges
  • change control board (and board member roles)
  • plan for how changes will be managed and controls
  • org tools for tracking and controlling changes
  • how to report outcome of changes requests
  • emergency change process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Configruation Management Plan

A

defines naming conventions, the version control system, document storage and retrieval system, and details how to manage changes to documentation

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

Project Documents

A

any project-related documents that are not part of the project management plan

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

Kickoff Meeting

A
  • announce the start of the project
  • ensure everyone is familiar with the details (including project objectives, stakeholder roles, and responsibilities)
  • ensure a commitment to the project from everyone
  • typically reviews milestones, risk, comms plan, and meeting schedule
20
Q

Inputs: Develop Project Management Plan

A
  • project charter
  • outputs from other projects
  • EEFs
  • OPAs
21
Q

Outputs: Develop Project Management Plan

A

Project Management Plan

22
Q

Inputs: Direct & Manage Project Work

A
  • PM Plan
  • Project Docs
  • Approved Change Requests
  • EFFs
  • OPAs
23
Q

Outputs: Direct & Manage Project Work

A
  • Deliverables
  • Work Performance Data
  • Issue Log
  • Change Requests
  • PM Plan Updates
  • Project Docs Updates
  • OPA updates
24
Q

PMIS

A

Performance management information system

includes automated tools, such as scheduling software, a configuraiton management system, shared workspaces for file storage or distribution, work authorizaiton software, time-tracking software, procurement management software and repositories for historical information

25
Q

Work Authorization System

A

PM’s system for authorizing the start of work packages or activities

(part of the PMIS)

26
Q

Inputs: Manage Project Knowledge

A
  • PM Plan
  • Project Docs
  • Deliverabbles
  • EEFs
  • OPAs
27
Q

Outputs: Manage Project Knowledge

A
  • Lessons learned register
  • PM Plan updates
  • OPA updates
28
Q

Types of knowledge

A

Explicit (fact-based)

Tacit (emotions, experience, ability)

29
Q

Lessons Learned

A
  • what was done right
  • what was done wrong
  • what would be done differently if the project could be redone
30
Q

Knowledge Management vs. Information Management

A

Knowledge Management: sharing of tacit knowledge between stakeholders

Information Management: ensuring information is available to stakeholders when needed

31
Q

Inputs: Monitor and Control Project

A
  • PM Plan
  • Project Docs
  • Work Performance Information
  • Agreements
  • EEFs
  • OPAs
32
Q

Outputs: Monitor and Control Project

A
  • Work performance reports
  • Change Requests
  • PM Plan updates
  • Project Docs updates
33
Q

Categories of Change Requests

A

Corrective Action

Preventive Action

Defect Repair

34
Q

Corrective Action

A

any action taken to bring expected future project performance in line with the project management plan when actual deviations occur

  • typically do not change baselines
  • should be reviewed through Perform Integrated Change Control
35
Q

Preventive Action

A

any action taken to address anticipated or possible deviations from performance management baseline and other metrics

  • typically do not change baselines
  • should be reviewed through Perform Integrated Change Control
36
Q

Inputs: Perform Integrated Change Control

A
  • PM Plan
  • Project Docs
  • Work Performance Reports
  • Change Requests
  • EEFs
  • OPAs
37
Q

Outputs: Perform Integrated Change Control

A
  • Approved Change Requests
  • PM Plan updates
  • Project Docs updates (including change log)
38
Q

Decision options for Change Request

A

Approve

Reject

Defer

39
Q

Change Control Board

A

Group that reviews changes in Perform Integrated Change Control process

CCB decisions are logged to change log

There is not a CCB for change-driven projects

40
Q

General steps when a change is requested during the project

A
  1. Evaluate the impact
  2. Identify options
  3. Get the Change Request approved by sponsor or CCB
41
Q

Steps after CCB takes decision on request

A
  1. Update status in change log
  2. Update PM Plan, project docs, and baselines as necessary
  3. Communicate the change to stakeholders
  4. Manage to revised PM plan
42
Q

Inputs: Close Project or Phase

A
  • Project Charter
  • PM Plan
  • Project Docs
  • Accepted Deliverables
  • Business Docs
  • Procurement Documentatin
  • OPAs
43
Q

Outputs: Close Project or Phase

A
  • Final product, service, or result transition
  • Final report
  • Project Docs updates
  • OPA updates
44
Q

Key Activities in Close Project or Phase

A
  • Confirm work is done to requirements
  • Complete final procurement closure
  • Gain final acceptance
  • Complete financial closure
  • Hand off completed project
  • Solicit customer feednback
  • Complete final performance reporting
  • Index and archive records
  • Gather final lessons learned, update knowledge base
45
Q
A