Integration Management Flashcards
Project Charter
Formally recognizes the existence of a project
Give the PM authority to spend money and commit resources to the project
Provides objectives, high level requirements and success criteria
Identifies constraints and high level risks
Provides assumptions
Links the project to ongoing work of the org
Business case
Captures the business need; explains why the project was selected how it fits into the organizations strategic goals and how it will bring business value to the organization
PMs need to keep the business case in mine throughout the project to make sure the achieves the objectives for which it was selected
Benefit measurement methods
Murder board
Peer review
Scoring models
Economic models
Constrained optimization methods
Linear programming
Integer programming
Dynamic programming
Multi-objective programming
Constraints
Factors that limit the teams options
Example: limits on resources, budget, schedule and scope (project must be completed with only 5 resources)
Assumptions
Things that we assumed to be true but they may not be true
Example: it is assumed we will not need engineering department approval before we start the activity
Statement of Work (SOW)
Created by the customer or sponsor and describes their needs, the product scope and how the project fits into the organizations strategic plan.
Management Plan
Document the strategy for managing the project and the processes related to each knowledge area.
A set of documents with processes, procedures, practices, standards, and metrics to follow to ensure consistent results
Management plans look forward in time and there are management plans for each knowledge areas
Project management plan
Integration function
Integrates all the individual management plans into a cohesive whole creating a centralized document to describe what is involved in the project
Project management processes Knowledge area management plans Scope, schedule and cost baseline Requirements management plan Change management plan Configuration management plan Process improvement plan
Baselines (performance measurement baseline)
Scope - project scope statement, WBS, and WBS dictionary
Schedule - the agreed upon schedule
Cost - the spending plan indicating how much money is approved for the project
***record of what the project had planned scheduled and budgeted for each area listed above
Used to compare the projects actual performance against the planned performance
Deviations from baselines are often due to incomplete risk identification and risk management
Requirements management plan
Describes how requirements will be gathered, analyzed, prioritized, evaluated, managed and controlled
Change management plan
Plan for managing changes and the change process on the project; describes how changes will be managed and controlled
Change control system
System that includes forms, reports, processes and software to track and control changes
Part of PMIS
Configuration management plan
Plan for managing changes to the documentation about the deliverables and and processes of the project including what org tools you will use
Includes a listing of approved configuration identification status of proposed changes to the configuration and the implementation status of approved changes
Plan for making sure everyone knows what version of the scope schedule etc is the latest version
Configuration management system
Contains the org standardized configuration management tools processes and procedures that can be used to track and control evolution of documentation
Part of PMIS
Process improvement plan
How processes that are used on the project to complete the work or perform project management activities will be evaluated or improved
Example: installing software on hundreds of computers; after a few installations are completed the PM should look for ways to improve the process
