Chapter 5 - Integration Management Flashcards
Integration Management
The unification of all the other knowledge areas
Combination or summary of the other 9 knowledge areas
Integration Management Process Groups
Initiating: Develop project charter
Planning: Develop project management plan
Executing: Direct and manage project work and Manage project knowledge
Monitoring and Controlling: Monitor and control project work and Perform integrated change control
Closing: Close project or phase
Integration Knowledge Area
Most important of the 10 knowledge areas
Incorporates and summarizes all of the work the project manager will need in order to successfully complete each phase of the project
Develop Project Charter
Developing a document that formally authorizes the project or phase
Documents the initial requirements to satisfy the stakeholders
Senior management approves
In an agile or hybrid project the project charter will not be as detailed because most of the project is not know at this time
Inputs
Business Documents
1) business case
2) benefits management plan
Business Case
Says what the business should do the project
- market demand
- organizational need
- customer request
- technological advance
- legal requirement
- environmental impacts
- social need
Business Methods to Select a Project
Benefit-cost ratio (return/cost)
Internal rate of return (looks at the return as an interest rate)
Opportunity cost (what you choose not to do in order to do something else)
Payback period (how long it will take to return the investment)
Economic value add (profit after taxes minus average cost of capital)
Present value and Net present value (money will loose value over time due to inflation)
Return on investment (how much money you will get back on the project)
Project Benefits Management Plan
Used to describe the main benefits that the project will produce once it is completed
Product, service, or result the organization is looking to obtain after the project is done
Cost-benefit analysis
Continually maintained
Project Charter Details
Project justification and purpose
Name of the project manager
Assignment of authority to the PM
Signature of the sponsor or others authorizing the project
High-level requirements (scope, budget, milestones view)
High-level risks
Stakeholder list
Exit criteria
Develop Project Management Plan
Includes all the subsidiary plans and baselines
All management plans
Approved by the sponsor
Once the plan is completed and baselined, only an approved change request can be used to update the plan
Project Kick-off Meeting
Planning is complete and the team comes together to execute the project.
Project Management Plan
Formal document that is used to describe how the project will be executed, monitored and controlled, and closed.
** Input to all executing, monitoring and controlling, and closing processes.
4 baselines and 14 subsidiary plans
Summary or detailed based on the project
Management Plan vs Baseline
Management plan: how to, explain how you are going to manage that section of the project
Baseline: used to track the performance of the project
Change Management Plan
Outline how change requests will be collected, assessed, authorized, and incorporated into the project
Configuration Management Plan
Outline how the various components of a project can be configured
You will need a plan that describes how to configure each computer to ensure that the software works correctly.