PMP ITO

processes and activities needed to properly coordinate all aspects of the project to meet stakeholder expectations

• Processes:
• 4.1 Develop project charter
• 4.2 Develop project management plan
• 4.3 Direct and manage project execution
• 4.4 Monitor and control project work
• 4.5 Perform integrated change control
• 4.6 Close project or phase

Authorizes a project or phase

• Inputs:
• 1. SOW
• 2. Business Case
• 3. Contract
• 4. EEF
• 5. OPA

• Tools:
• 1. Expert Judgment

• Outputs:
• 1. Project Charter

Collection of all subsidiary plans

• Inputs:
• 1. Project Charter
• 2. Outputs from planning processes
• 3. EEF
• 4. OPA

• Tools:
• 1. Expert Judgment

• Outputs:
• 1. Project Management Plan

PM directs performance of activities in the plan

• Inputs:
• 1. Project Management Plan
• 2. Approved Change Requests
• 3. EEF
• 4. OPA

• Tools
• 1. Expert Judgment
• 2. Project Management Information System

• Outputs:
• 1. Deliverables
• 2. Work performance information
• 3. Change requests
• 4. Project Management Plan updates
• 5. Project Document Updates

constantly measure and report performance; determine appropriate preventative & corrective action

• Inputs:
• 1. Project management plan
• 2. Performance reports
• 3. EEF
• 4. OPA

• Tools:
• 1. Expert Judgment

• Outputs:
• 1. Change requests
• 2. Project management plan updates
• 3. Project document updates

continuously manage changes & maintain a baseline

• Inputs:
• 1. Project management plan
• 2. Work performance information
• 3. Change requests
• 4. EEF
• 5. OPA

• Tools:
• 1. Expert Judgment
• 2. Change control meetings

• Outputs:
• 1. Change request status updates
• 2. Project management plan updates
• 3. Project document updates

procedures to close a project or phase

• Inputs:
• 1. Project management plan
• 2. accepted deliverables
• 3. OPA

• Tools:
• 1. Expert Judgment

• Outputs:
• 1. Final product, service or result transition
• 2. OPA updates

processes needed to ensure the project includes all the work required and ONLY the work required to complete the project successfully; carefully identifies what IS and IS NOT included in the project (ie. project boundaries)

• processes:
• 5.1 Collect requirements
• 5.2 Define Scope
• 5.3 Create WBS
• 5.4 Verify Scope
• 5.5 Control Scope

define and document stakeholder needs to meet project objectives

• Inputs:
• 1. Project charter
• 2. Stakeholder register

• Tools:
• 1. Interviews
• 2. Focus Groups
• 3. Facilitated Workshops
• 4. Group Creativity Techniques
• 5. Group Decision Making techniques
• 6. Questionnaires & surveys
• 7. Observations
• 8. Prototypes

• Outputs:
• 1. Requirements documentation
• 2. Requirements management plan
• 3. Requirements traceability matrix

develops a detailed, written scope statement

• Inputs:
• 1. Project charter
• 2. Requirements documentation
• 3. OPA

• Tools:
• 1. Expert Judgment
• 2. Product analysis
• 3. Alternatives Identification
• 4. Facilitated workshops

• Outputs:
• 1. Project Scope Statement
• 2. Project Document updates

subdivides the work into smaller, more manaageable components

• Inputs:
• 1. Project scope statement
• 2. Requirements documentation
• 3. OPA

• Tools:
• 1. Decomposition

• Outputs:
• 1. WBS
• 2. WBS dictionary
• 3. Scope baseline
• 4. Project document updates

formalizing acceptance of completed project deliverables

• Inputs:
• 1. Project Management Plan
• 2. Requirements Documentation
• 3. Requirements Traceability Matrix
• 4. Validated Deliverables

• Tools:
• 1. Inspection

• Outputs:
• 1. Accepted Deliverables
• 2. Change Requests
• 3. Project Document Updates

monitoring status and controlling changes to the project scope

• Inputs:
• 1. Project management plan
• 2. work performance information
• 3. requirements documentation
• 4. requirements traceability matrix
• 5. OPA

• Tools:
• 1. Variance analysis

• Outputs:
• 1. Work performance measurements
• 2. OPA updates
• 3. Change Requests
• 4. Project Management Plan updates
• 5. Project document updates

processes needed to ensure timely completion of the project

• processes:
• 6.1 Define Activities
• 6.2 Sequence Activities
• 6.3 Estimate Activity Resources
• 6.4 Estimate Activity Durations
• 6.5 Develop Schedule
• 6.6 Control Schedule

identifying the activities that must be performed

• Inputs:
• 1. Scope baseline
• 2. EEF
• 3. OPA

• Tools:
• 1. Decomposition
• 2. Rolling Wave Planning
• 3. Templates
• 4. Expert Judgment

• Outputs:
• 1. Activity List
• 2. Activity Attributes
• 3. Milestone List

identifying activity dependencies

• Inputs:
• 1. activity list
• 2. activity attributes
• 3. milestone list
• 4. project scope statement
• 5. OPA

• Tools:
• 1. Precedence Diagram Method (PDM)
• 2. Dependency determination
• 3. applying leads and lags
• 4. Schedule network templates

• Outputs:
• 1. Project schedule network diagrams
• 2. project document updates

estimating the type & quantity of resources needed

• Inputs:
• 1. activity list
• 2. activity attributes
• 3. resource calendars
• 4. EEF
• 5. OPA

• Tools:
• 1. Expert judgment
• 2. alternatives analysis
• 3. published estimating data
• 4. bottom-up estimating
• 5. project management software

• Outputs:
• 1. Activity resource requirements
• 2. resource breakdown structure (rbs)
• 3. project document updates

estimating durations of individual activities

• Inputs:
• 1. activity list
• 2. activity attributes
• 3. activity resource requirements
• 4. resource calendars
• 5. project scope statement
• 6. EEF
• 7. OPA

• Tools:
• 1. expert judgment
• 2. analogous estimating
• 3. parametric estimating
• 4. bottom-up estimating
• 5. project management software

• Outputs:
• 1. activity duration estimates
• 2. project document updates

analyzing sequences, durations, resource requirements and contstraints to create the project schedule

• Inputs:
• 1. activity list
• 2. activity attributes
• 3. network diagrams
• 4. resource requirements
• 5. resource calendars
• 6. duration estimates
• 7. scope statement
• 8. EEF
• 9. OPA

• Tools:
• 1. network analysis
• 2. critical path method
• 3. critical chain method
• 4. resource leveling
• 5. what-if scenario analysis
• 6. applying leads & lags
• 7. Schedule compression
• 8. Scheduling tool

• Outputs:
• 1. Project schedule
• 2. Schedule baseline
• 3. Schedule data
• 4. Project document updates

monitoring status and managing changes to the schedule baseline

• Inputs:
• 1. Project management plan
• 2. project schedule
• 3. work performance information
• 4. OPA

• Tools:
• 1. Performance reviews
• 2. variance analysis
• 3. project management software
• 4. resource leveling
• 5. what-if scenario analysis
• 6. adjust leads & lags
• 7. schedule compression
• 8. scheduling tool

• Outputs:
• 1. work performance measurements
• 2. OPA updates
• 3. change requests
• 4. project management plan updates
• 5. project document updates

processes for estimating, budgeting & controlling costs so the project can be completed within budget

• processes:
• 7.1 Estimate Costs
• 7.2 Determine Budget
• 7.3 Control Costs

estimating the costs of resources needed to complete project activities

• Inputs:
• 1. Scope baseline
• 2. project schedule
• 3. human resources plan
• 4. risk register
• 5. EEF
• 6. OPA

• Tools:
• 1. Expert Judgment
• 2. Analogous Estimating
• 3. Parametric Estimating
• 4. Bottom-up estimating
• 5. Three-point estimates
• 6. reserve analysis
• 7. cost of quality
• 8. project management estimating software
• 9. vendor bid analysis

• Outputs:
• 1. activity cost estimates
• 2. basis of estimates
• 3. project document updates

aggregating estimated costs to establish cost baseline

• Inputs:
• 1. Activity cost estimates
• 2. basis of estimates
• 3. scope baseline
• 4. project schedule
• 5. resource calendars
• 6. contracts
• 7. OPA

• Tools:
• 1. cost aggregation
• 2. reserve analysis
• 3. expert judgment
• 4. historical relationships
• 5. funding limit reconciliation

• Outputs:
• 1. cost performance baseline
• 2. project funding requirements
• 3. project document updates

monitoring status and maanging changes to the cost baseline

• Inputs:
• 1. Project Management Plan
• 2. Project funding requirements
• 3. work performance information
• 4. OPA

• Tools:
• 1. Earned value management
• 2. Forecasting
• 3. To-complete performance index
• 4. performance reviews
• 5. variance analysis
• 6. project management software

• Outputs:
• 1. work performance measurements
• 2. budget forecasts
• 3. OPA updates
• 4. change requests
• 5. project management plan updates
• 6. project document updates

processes to ensure the project will satisfy the needs for which it was undertaken & implement a quality management system

• processes:
• 8.1 Plan Quality
• 8.2 Perform Quality Assurance
• 8.3 Perform Quality Control

identifying relevant quality requirements/standards& documenting how th eproject will demonstrate compliance

• Inputs:
• 1. Scope baseline
• 2. stakeholder register
• 3. cost performance baseline
• 4. schedule baseline
• 5. risk register
• 6. EEF
• 7. OPA

• Tools:
• 1. cost-benefit analysis
• 2. cost of quality
• 3. control charts
• 4. benchmarking
• 5. experiments
• 6. statistical sampling
• 7. flowcharting
• 8. proprietary methodologies
• 9. additional quality planning tools

• Outputs:
• 1. Quality management plan
• 2. Quality metrics
• 3. Quality checklists
• 4. Process improvement plan
• 5. Project document updates

ensuring the project uses all processes needed to meet requirements. the ultimate purpose of QA is quality improvement

• Inputs:
• 1. project management plan
• 2. quality metrics
• 3. work performance information
• 4. QC measurements

• Tools:
• 1. Plan quality & perform quality control tools
• 2. quality audits
• 3. process analysis

• Outputs:
• 1. OPA updates
• 2. Change requests
• 3. Project management plan updates
• 4. Project document updates

monitoring results for compliance & recommending necessary changes

• Inputs:
• 1. project management plan
• 2. quality metrics
• 3. quality checklists
• 4. work performance measurements
• 5. approved change requests
• 6. deliverables
• 7. OPA

• Tools:
• 1. cause/effect diagram
• 2. control charts
• 3. flowcharting
• 4. histogram
• 5. pareto chart
• 6. run chart
• 7. scatter diagram
• 8. statistical sampling
• 9. inspection
• 10. approved change requests review

• Outputs:
• 1. QC measurements
• 2. Validated changes
• 3. Validated deliverables
• 4. OPA updates
• 5. change requests
• 6. Project management plan updates

processes that organize and manage the project team

• Processes:
• 9.1 Develop HR plan
• 9.2 Acquire Project Team
• 9.3 Develop Project Team
• 9.4 Manage Project Team

establishing roles, responsibilities, reporting relationships & creating a staffing management plan

• Inputs:
• 1. Activity resource requirements
• 2. EEF
• 3. OPA

• Tools:
• 1. Org charts & position descriptions
• 2. Networking
• 3. Organizational Theory

• Outputs
• 1. Human Resources Plan

getting the human resources needed to complete the project

• Inputs:
• 1. Project management plan
• 2. EEF
• 3. OPA

• Tools:
• 1. Pre-assignment
• 2. negotiation
• 3. acquisition
• 4. virtual teams

• Outputs:
• 1. staff assignments
• 2. resource calendars
• 3. project management plan updates

improving competencies, interaction of the team & overall team environment

• Inputs:
• 1. staff assignments
• 2. project management plan
• 3. resource calendars

• Tools:
• 1. Interpersonal skills
• 2. Training
• 3. Team building
• 4. Ground rules
• 5. co-location
• 6. recognition and rewards

• Outputs:
• 1. Team performance assessments
• 2. EEF updates

tracking performance, providing feedback, resolving issues & coordinating changes

• Inputs:
• 1. Staff assignments
• 2. project management plan
• 3. team performance assessments
• 4. performance reports
• 5. organizational process assets

• Tools:
• 1. observation & conservation
• 2. performance appraisals
• 3. conflict management
• 4. issue log
• 5. interpersonal skills

• Outputs:
• 1. EEF updates
• 2. OPA updates
• 3. change requests
• 4. project management plan updates

processes to ensure the timely & appropriate generation, collection, distribution, storage & ultimate disposition of the project

processes:

• 10.1 Identify Stakeholders
• 10.2 Plan communications
• 10.3 Distribute information
• 10.4 Manage stakeholder expectations
• 10.5 Report performance

identifying the interests, involvement & influence of people & organizations impacted by the project

• Inputs:
• 1. Project charter
• 2. procurement documents
• 3. EEF
• 4. OPA

• Tools:
• 1. Stakeholder analysis
• 2. expert judgment

• Outputs:
• 1. Stakeholder register
• 2. stakeholder managemetn strategy

determining the information needs of stakeholders

• Inputs:
• 1. stakeholder register
• 2. stakeholder management strategy
• 3. EEF
• 4. OPA

• tools:
• 1. communication requirements analysis
• 2. communication technology
• 3. communication models
• 4. communication methods

• Outputs:
• 1. communications management plan
• 2. project document updates

making information available in a timely manner

• Inputs:
• 1. Project management plan
• 2. performance reports
• 3. OPA

• Tools:
• 1. Communication methods
• 2. Information distribution tools

• Outputs:
• 1. OPA updates

communicating and working with stakeholders to meet their needs and resolve issues

• Inputs:
• 1. Stakeholder register
• 2. Stakeholder management strategy
• 3. Project management plan
• 4. Issue log
• 5. Change log
• 6. OPA

• Tools:
• 1. Communication methods
• 2. Interpersonal skills
• 3. Management skills

• Outputs:
• 1. OPA updates
• 2. Change requests
• 3. Project management plan updates
• 4. Project document updates

collecting & disseminating performance information

• Inputs:
• 1. project management plan
• 2. work performance information
• 3. work performance measurements
• 4. budget forecasts
• 5. OPA

• Tools:
• 1. Variance analysis
• 2. Forecasting methods
• 3. Communication methods
• 4. Reporting Systems

• Outputs:
• 1. Performance reports
• 2. OPA updates
• 3. Change requests

processes concerned with planning, identifying, analyzing, responding and controlling project risks

processes:

• 11.1 Plan risk management
• 11.2 Identify risks
• 11.3 Perform qualitative risk analysis
• 11.4 Perform quantitative risk analysis
• 11.5 Plan risk responses
• 11.6 Monitor & control risks

how to approach, plan & execute risk management

• Inputs:
• 1. Project scope statement
• 2. cost management plan
• 3. schedule management plan
• 4. communications management plan
• 5. EEF
• 6. OPA

• Tools:
• 1. Planning meetings and analysis

• Outputs:
• 1. risk management plan

determining which risks might affect the project

• Inputs:
• 1. risk management plan
• 2. activity cost estimates
• 3. activity duration estimates
• 4. scope baseline
• 5. stakeholder register
• 6. cost management plan
• 7. schedule management plan
• 8. quality management plan
• 9. project documents
• 10. EEF
• 11. OPA

• Tools:
• 1. Documentation reviews
• 2. Information gathering techniques
• 3. checklist analysis
• 4. assumptions analysis
• 5. diagramming techniques
• 6. SWOT analysis
• 7. Expert judgment

• Outputs:
• 1. risk register

prioritizing risks for further analysis or action (probability v. impact)

• Inputs:
• 1. risk register
• 2. risk management plan
• 3. project scope statement
• 4. OPA

• Tools:
• 1. risk probability and impact
• 2. probability and impact matrix
• 3. risk data quality assessment
• 4. risk categorization
• 5. risk urgency assessement
• 6. Expert judgment

• Outputs:
• 1. risk register updates

numerically analyzing the potential effect of identified risks

• Inputs:
• 1. risk register
• 2. risk management plan
• 3. cost management plan
• 4. schedule management plan
• 5. OPA

• Tools:
• 1. data gathering and representation techniques
• 2. quantitative risk analysis and modeling techniques
• 3. expert judgment

• Outputs:
• 1. risk register updates

how to enhance opportunities & reduce threats

• Inputs:
• 1. risk register
• 2. risk management plan

• Tools:
• 1. strategies for negative risks or threats
• 2. strategies for positive risks or opportunities
• 3. contingent response strategies
• 4. expert judgment

• Outputs:
• 1. risk register updates
• 2. risk-related contract decisions
• 3. project plan updates

monitoring identified risks, identifying new risks & evaluating risk response plans

• Inputs:
• 1. risk register
• 2. project management plan
• 3. work performance information
• 4. performance reports

• Tools:
• 1. Risk Reassessment
• 2. Risk Audits
• 3. Variance & Trend Analysis
• 4. Technical performance measurement
• 5. Reserve Analysis
• 6. Status Meetings

• Outputs:
• 1. Risk register updates
• 2. OPA updates
• 3. change requests
• 4. Project plan updates
• 5. Project document updates

processes to acquire products, services or results from outside the project team

• processes:
• 12.1 Plan procurements
• 12.2 Conduct procurements
• 12.3 Administer procurements
• 12.4 Close procurements

documenting purchasing decisions, specifying the approach, and identifying potential sellers

• Inputs:
• 1. Scope baseline
• 2. Requirements documentation
• 3. Teaming agreemetns
• 4. Risk Register
• 5. Risk-related Contract decisions
• 6. Activity resource requirements
• 7. Project schedule
• 8. Activity cost estimates
• 9. Cost performance baseline
• 10. EEF
• 11. OPA

• Tools:
• 1. Make-or-buy analysis
• 2. Expert Judgment
• 3. Contract types

• Outputs:
• 1. Procurement management plan
• 2. Procurement statements of work
• 3. Make-or-buy decisions
• 4. procurement documents
• 5. source selection criteria
• 6. change requests

obtaining seller responses, selecting a seller and awarding a contract

• Inputs:
• 1. Project management plan
• 2. Procurement documents
• 3. Source selection criteria
• 4. Qualified seller list
• 5. Seller proposals
• 6. Project documents
• 7. Make-or-buy decisions
• 8. Teaming agreements
• 9. OPA

• Tools:
• 1. Bidder conferences
• 2. Proposal evaluation techniques
• 3. Independent estimates
• 4. Expert Judgment
• 5. Advertising
• 6. Internet Search
• 7. Procurement negotiations

• Outputs:
• 1. Selected sellers
• 2. Procurement contract award
• 3. Resource calendars
• 4. Change requests
• 5. Project management plan updates
• 6. Project document updates

managing procurement relationships, monitoring contract performance, and making changes as needed

• Inputs:
• 1. Procurement documents
• 2. Project management plan
• 3. Contract
• 4. Performance Reports
• 5. Approved Change Requests
• 6. Work Performance Information

• Tools:
• 1. Contract Change control system
• 2. Procurement performance reviews
• 3. Inspections and audits
• 4. Performance reporting
• 5. Payment systems
• 6. Claims administration
• 7. Records management system

• Outputs:
• 1. Procurement documentation
• 2. OPA updates
• 3. Change requests
• 4. Project management plan updates

completing & settling each contract, including resolution of any open items

• Inputs:
• 1. Project management Plan
• 2. Procurement documentation

• Tools:
• 1. Procurement audits
• 2. Negotiated settlements
• 3. Records management system

• Outputs:
• 1. Closed procurements
• 2. OPA updates