Integration Management Flashcards
Key activities: Develop Project Charter
- 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)
Inputs: Develop Project Charter
- business documents (business case, benefits management plan)
- agreements
- OPAs
- EEFs
Business Case Components
- business need
- why project was selected
- how project fits into strategic goals
- how it brings value to the organization
- assumptions and contsraints
Benefits Management Plan
- identifies desired benefits from a project (economic and intangible)
- explains how benefits will be maximized and sustained.
- defines metrics and processes for measuring benefits
Benefits of Project Charter
- 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
Outputs: Develop Project Charter
- Project Charter
- Assumption Log
Project Management Plan
Defines how the project is executed, monitored, and controlled
Components of Project Management Plan
- Management plans for each knowledge area
- Requirements management plan
- Change management plan
- Confirguration management plan
- Performance measurement baselines (Scope, Schedule, Cost)
- Project Life Cycle description (phases)
- Development approach
Scope Baseline
scope statement, WBS, WBS dictionary
Schedule Baseline
agreed upon schedule, start and stop dates for each activity, and scheduled milestones
Cost Baseline
time-phased cost budget (indicates how much money is approved and when funds are required and available)
Performance Managment Baseline
Scope Baseline, Schedule Baseline & Cost Baseline
What should you do if a project deviates from established baselines?
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
Key activities: Direct & Manage Project Work
- 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
Requirements Management Plan
- defines how requirements will be gathered, analyzed, prioritized, evaluated, and documented
- how requirements will be managed and controlled throughout the project
Change Management Plan
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
Configruation Management Plan
defines naming conventions, the version control system, document storage and retrieval system, and details how to manage changes to documentation
Project Documents
any project-related documents that are not part of the project management plan
Kickoff Meeting
- 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
Inputs: Develop Project Management Plan
- project charter
- outputs from other projects
- EEFs
- OPAs
Outputs: Develop Project Management Plan
Project Management Plan
Inputs: Direct & Manage Project Work
- PM Plan
- Project Docs
- Approved Change Requests
- EFFs
- OPAs
Outputs: Direct & Manage Project Work
- Deliverables
- Work Performance Data
- Issue Log
- Change Requests
- PM Plan Updates
- Project Docs Updates
- OPA updates
PMIS
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
Work Authorization System
PM’s system for authorizing the start of work packages or activities
(part of the PMIS)
Inputs: Manage Project Knowledge
- PM Plan
- Project Docs
- Deliverabbles
- EEFs
- OPAs
Outputs: Manage Project Knowledge
- Lessons learned register
- PM Plan updates
- OPA updates
Types of knowledge
Explicit (fact-based)
Tacit (emotions, experience, ability)
Lessons Learned
- what was done right
- what was done wrong
- what would be done differently if the project could be redone
Knowledge Management vs. Information Management
Knowledge Management: sharing of tacit knowledge between stakeholders
Information Management: ensuring information is available to stakeholders when needed
Inputs: Monitor and Control Project
- PM Plan
- Project Docs
- Work Performance Information
- Agreements
- EEFs
- OPAs
Outputs: Monitor and Control Project
- Work performance reports
- Change Requests
- PM Plan updates
- Project Docs updates
Categories of Change Requests
Corrective Action
Preventive Action
Defect Repair
Corrective Action
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
Preventive Action
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
Inputs: Perform Integrated Change Control
- PM Plan
- Project Docs
- Work Performance Reports
- Change Requests
- EEFs
- OPAs
Outputs: Perform Integrated Change Control
- Approved Change Requests
- PM Plan updates
- Project Docs updates (including change log)
Decision options for Change Request
Approve
Reject
Defer
Change Control Board
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
General steps when a change is requested during the project
- Evaluate the impact
- Identify options
- Get the Change Request approved by sponsor or CCB
Steps after CCB takes decision on request
- Update status in change log
- Update PM Plan, project docs, and baselines as necessary
- Communicate the change to stakeholders
- Manage to revised PM plan
Inputs: Close Project or Phase
- Project Charter
- PM Plan
- Project Docs
- Accepted Deliverables
- Business Docs
- Procurement Documentatin
- OPAs
Outputs: Close Project or Phase
- Final product, service, or result transition
- Final report
- Project Docs updates
- OPA updates
Key Activities in Close Project or Phase
- 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
