1. Initiating
1.1. Develop Project Charter
1.1.1. Input
1.1.1.1. Enterprise Environmental Factors
1.1.1.1.1. Culture and Structure
1.1.1.1.2. Standards
1.1.1.1.3. Infrastructure
1.1.1.1.4. risk tolerance
1.1.1.1.5. PMIS
1.1.1.1.6. existing human resources
1.1.1.1.7. DB for cost estimating
1.1.1.1.8. DB for risk study information
1.1.1.2. Contract
1.1.1.3. Statement of Work
1.1.1.4. Organizational Process Assets
1.1.1.4.1. policies
1.1.1.4.2. templates
1.1.1.4.3. guidelines
1.1.1.4.4. change control procedures
1.1.1.4.5. risk control procedures
1.1.1.4.6. processes
1.1.1.4.7. procedures
1.1.2. Output
1.1.2.1. Project Charter
1.1.2.1.1. project justification
1.1.2.1.2. current understanding of requirements
1.1.2.1.3. description of the new product or service
1.1.2.1.4. assigned PM and his authority
1.1.2.1.5. milestone schedule
1.1.2.1.6. assumptions and constraints
1.1.2.1.7. participation of functional orgs
1.1.3. Tools
1.1.3.1. Project Selection Methods
1.1.3.1.1. benefit measurement methods
1.1.3.1.2. mathematical models
1.1.3.2. Project Management Methodology
1.1.3.2.1. Collection of templates and procedures that the organization uses
1.1.3.3. PM Information System
1.1.3.3.1. change control / versioning
1.1.3.3.2. project planning
1.1.3.4. Expert Judgement
1.1.4. Objectives
1.1.4.1. Are we working on the right problem?
1.1.4.2. Do we want to work on this problem?
1.2. Develop preliminary project scope statemente
1.2.1. Input
1.2.1.1. Enterprise Environmental Factors
1.2.1.2. Project Charter
1.2.1.3. Organizational Process Assets
1.2.1.4. Statement of Work
1.2.2. Output
1.2.2.1. Preliminary Project Scope Statement
1.2.2.1.1. objectives
1.2.2.1.2. requirements and characteristics
1.2.2.1.3. project boundaries
1.2.2.1.4. assumptions/constraints
1.2.2.1.5. initial WBS
1.2.2.1.6. order of magnitude cost estimate
1.2.3. Tools
1.2.3.1. Project Management Methodology
1.2.3.2. Project Management Information System
1.2.3.3. Expert Judgement
1.2.4. Objectives
1.2.4.1. What are the high-level requirements to successfully deal with the customer's need?
1.2.4.2. How realistic are the customer's expectations with regard to time and cost?
2. Planning
2.1. Develop Project Management Plan
2.1.1. Input
2.1.1.1. Preliminary Project Scope Statement
2.1.1.2. Project Management Processes
2.1.1.3. Enterprise Environmental Factors
2.1.1.4. Organizational Process Assets
2.1.2. Output
2.1.2.1. Project Management Plan
2.1.2.1.1. definition
2.1.2.1.2. contains 9 plans
2.1.2.1.3. further 6 components (may have more than 6)
2.1.3. Tools
2.1.3.1. Project Management Methods
2.1.3.2. Project Management Information System
2.1.3.3. Expert Judgement
2.1.4. Objectives
2.1.4.1. How can we best and most effectively achieve project objectives?
2.1.4.2. Are all aspects of the plan consistent and comprehensive?
2.2. Scope Planning
2.2.1. Input
2.2.1.1. Enterprise Environmental Factors
2.2.1.2. Organizational Process Assets
2.2.1.3. Preliminary Scope Statement
2.2.1.4. Project Management Plan
2.2.1.5. Project Charter
2.2.2. Output
2.2.2.1. Project Scope Management Plan
2.2.2.1.1. describing how the team will prepare the detailed scope statement
2.2.2.1.2. describe how the WBS will be created
2.2.2.1.3. describe how the final deliverables will be verified and accepted
2.2.2.1.4. describe how change requests to the scope statement will be processed
2.2.3. Tools
2.2.3.1. Expert Judgement
2.2.3.2. Templates, Forms and Standards
2.2.4. Objectives
2.2.4.1. How can I best determine the requirements and specifications necessary to satisfy the objectives of this project?
2.2.4.2. How do I best use the available resources to accomplish this?
2.3. Scope Definition
2.3.1. Input
2.3.1.1. Organizational Process Assets
2.3.1.2. Project Charter
2.3.1.3. Preliminary Scope Statement
2.3.1.4. Scope Management Plan
2.3.1.5. Approved Change Requests
2.3.2. Output
2.3.2.1. Project Scope Statement
2.3.2.2. Requested Changes
2.3.2.3. Scope Management Plan (Updates)
2.3.3. Tools
2.3.3.1. Product Analysis
2.3.3.2. Alternatives Identification
2.3.3.3. Stakeholder Analysis
2.3.4. Objectives
2.3.4.1. What exactly will the customer get?
2.3.4.2. What characteristics must the product have if the customer is to be satisfied?
2.4. Create WBS
2.4.1. Input
2.4.1.1. Organizational Process Assets
2.4.1.2. Scope Management Plan
2.4.1.3. Approved Change Requests
2.4.1.4. Project Scope Management Plan
2.4.2. Output
2.4.2.1. Project Scope Statements (Updates)
2.4.2.2. Work Breakdown Structure
2.4.2.2.1. caveat
2.4.2.3. WBS Dictionary
2.4.2.3.1. detailed description of components in the WBS
2.4.2.4. Scope Baseline
2.4.2.4.1. Definition
2.4.2.5. Scope Management Plan (updates)
2.4.2.6. Requested Changes
2.4.3. Tools
2.4.3.1. Work Breakdown Structure Template
2.4.3.2. Decomposition
2.4.4. Objectives
2.4.4.1. What project level deliverables will be required?
2.4.4.2. How exactly will the work be done?
2.5. Activity Definition
2.5.1. Input
2.5.1.1. Enterprise Environmental Factors
2.5.1.2. Organizational Process Assets
2.5.1.3. Project Scope Statement
2.5.1.4. Work Breakdown Structure
2.5.1.5. WBS Dictionary
2.5.1.6. Project Management Plan
2.5.2. Output
2.5.2.1. Activity List
2.5.2.1.1. Definition
2.5.2.2. Activity Attributes
2.5.2.3. Milestone List
2.5.2.3.1. Definition
2.5.2.4. Requested Changes
2.5.3. Tools
2.5.3.1. Decomposition
2.5.3.2. Templates
2.5.3.3. Rolling Wave Planning
2.5.3.3.1. Definition
2.5.3.4. Planning Component
2.5.3.4.1. Definition
2.5.4. Objectives
2.5.4.1. What work needs to be done to produce the specified deliverables?
2.6. Activity Sequencing
2.6.1. Input
2.6.1.1. Project Scope Statement
2.6.1.2. Activity List
2.6.1.3. Milestone List
2.6.1.4. Activity Attributes
2.6.1.5. Approved Change Requests
2.6.2. Output
2.6.2.1. Project Schedule Network Diagram
2.6.2.1.1. Definition
2.6.2.2. Activity List (updates)
2.6.2.3. Activity Attributes (updates)
2.6.2.4. Approved Change Requests
2.6.3. Tools
2.6.3.1. Precedence Diagramming Method (PDM)
2.6.3.1.1. Definition
2.6.3.2. Arrow Diagramming Method (ADM)
2.6.3.2.1. Definition
2.6.3.3. Schedule Network Templates
2.6.3.4. Dependency Determination
2.6.3.4.1. mandatory dependencies
2.6.3.4.2. discretionary dependencies
2.6.3.4.3. external dependencies
2.6.3.5. Applying leads and lags
2.6.3.5.1. lead
2.6.3.5.2. lag
2.6.4. Objectives
2.6.4.1. In what sequence must the activities be conducted?
2.7. Activity Resource Estimating
2.7.1. Input
2.7.1.1. Enterprise Environmental Factors
2.7.1.2. Organizational Process Assets
2.7.1.3. Activity List
2.7.1.4. Activity Attributes
2.7.1.5. Resource Availability
2.7.1.5.1. info on which resources are available
2.7.1.6. Project Management Plan
2.7.2. Output
2.7.2.1. Activity Resource Requirements
2.7.2.1.1. description of types and quantities of resources for each activity in a work package
2.7.2.1.2. contains
2.7.2.2. Activity Attributes (Updates)
2.7.2.2.1. added
2.7.2.3. Resource Breakdown Structure
2.7.2.4. Resource Calendar (Updates)
2.7.2.4.1. documents
2.7.2.5. Requested Changes
2.7.3. Tools
2.7.3.1. Expert Judgement
2.7.3.2. Alternatives Analysis
2.7.3.3. Published Estimating Data
2.7.3.3.1. e.g. production rates and unit costs
2.7.3.4. Project Management Software
2.7.3.5. Bottom-up Estimating
2.7.3.5.1. decompose activity into more detail
2.7.3.5.2. decompose activity into more detail
2.7.3.5.3. aggregate estimates into a total
2.7.4. Objectives
2.7.4.1. what resources (people, material, equipment) are needed and in what quantity?
2.8. Activity Duration Estimating
2.8.1. Input
2.8.1.1. Enterprise Environmental Factors
2.8.1.1.1. duration estimating database available?
2.8.1.2. Organizational Process Assets
2.8.1.2.1. historical information on durations avalaible?
2.8.1.3. Activity List
2.8.1.4. Activity Attributes
2.8.1.5. Project Scope Statement
2.8.1.5.1. constraints and assumptions are considered
2.8.1.6. Activity Resource Requirements
2.8.1.6.1. resources assigned and availability of those resources will affect the duration
2.8.1.7. Resource Calendar
2.8.1.7.1. availability of resources could influence the duration
2.8.1.8. Project Management Plan
2.8.1.8.1. contains
2.8.2. Output
2.8.2.1. Activity Duration Estimates
2.8.2.2. Activity Duration Estimates
2.8.2.2.1. assessment of the likely number of work periods required to complete an activity
2.8.2.2.2. include some indication of the range
2.8.2.2.3. e.g. 2 weeks +/- 2 days
2.8.2.3. Activity Attributes (Updates)
2.8.2.3.1. now include
2.8.3. Tools
2.8.3.1. Expert Judgement
2.8.3.1.1. can be used whenever possible
2.8.3.2. Analogous Estimating
2.8.3.2.1. using the duration of a previous similar activity as a basis for estimating
2.8.3.3. Parametric Estimating
2.8.3.3.1. mathematical model based on the quantity of work
2.8.3.4. Three-Point-Estimates
2.8.3.4.1. three estimates
2.8.3.4.2. estimate = (opt + 4*lik + pes) / 6
2.8.3.5. Reserve Analysis
2.8.3.5.1. aka
2.8.3.5.2. calculated as
2.8.3.5.3. contingency reserve must be documented
2.8.4. Objectives
2.8.4.1. how long will the individual activities take?
2.9. Schedule Development
2.9.1. Input
2.9.1.1. Organizational Process Assets
2.9.1.1.1. e.g. project calendar
2.9.1.2. Project Scope Statement
2.9.1.2.1. Imposed dates on activity starts or finishes
2.9.1.2.2. Key events or major milestones
2.9.1.3. Activity List
2.9.1.4. Activity Attributes
2.9.1.5. Project Schedule Network Diagram
2.9.1.6. Activity Resource Requirements
2.9.1.7. Resource Calendars
2.9.1.8. Activity Duration Estimates
2.9.1.9. Project Management Plan
2.9.2. Output
2.9.2.1. Project Schedule
2.9.2.1.1. includes at least a planned start and finish date for each activity
2.9.2.1.2. created not later than completion of the PMP
2.9.2.1.3. presented in one of these formats
2.9.2.2. Schedule Model Data
2.9.2.2.1. schedule milestones
2.9.2.2.2. schedule activities
2.9.2.2.3. activity attributes
2.9.2.2.4. documentation of assumptions and constraints
2.9.2.2.5. supporting detail
2.9.2.3. Schedule Baseline
2.9.2.3.1. project baseline start and finish dates
2.9.2.4. Resource Requirements (Updates)
2.9.2.5. Activity Attributes (Updates)
2.9.2.6. Project Calendar (Updates)
2.9.2.7. Requested Changes
2.9.2.8. Project Management Plan (Updates)
2.9.3. Tools
2.9.3.1. Schedule Network Analysis
2.9.3.1.1. technique that generates the project schedule
2.9.3.1.2. employs
2.9.3.1.3. early and late start and finish dates are calculated for each activity
2.9.3.2. Critical Path Method
2.9.3.2.1. calculate "float" for tasks
2.9.3.2.2. tasks with zero float are critical activities
2.9.3.2.3. definition
2.9.3.3. Schedule Compression
2.9.3.3.1. shorten the schedule without changing scope
2.9.3.3.2. techniques
2.9.3.4. What-If Scenario Analysis
2.9.3.4.1. used to assess feasability of project schedule under adverse conditions
2.9.3.4.2. objective: prepare contingency and response plans
2.9.3.4.3. most common technique is Monte Carlo Analysis
2.9.3.5. Resource Leveling
2.9.3.5.1. objectives
2.9.3.5.2. techniques
2.9.3.5.3. result is aka
2.9.3.6. Critical Chain Method
2.9.3.6.1. adds duration buffers
2.9.3.6.2. utilizes non-conservative estimates
2.9.3.6.3. manages the buffer durations, not float
2.9.3.7. Project Management Software
2.9.3.8. Applying Calendars
2.9.3.9. Adjusting Leads and Lags
2.9.3.10. Schedule Model
2.9.4. Objectives
2.9.4.1. How long will it take to complete the project?
2.9.4.2. which are my critical activities?
2.10. Cost Estimating
2.10.1. Input
2.10.1.1. Enterprise Environmental Factors
2.10.1.1.1. considers
2.10.1.2. Organizational Process Assets
2.10.1.2.1. cost estimating policies
2.10.1.2.2. cost estimating templates
2.10.1.2.3. historical information
2.10.1.2.4. project files
2.10.1.2.5. project team knowledge
2.10.1.2.6. lessons learned
2.10.1.3. Project Scope Statement
2.10.1.4. WBS
2.10.1.5. WBS Dictionary
2.10.1.6. PMP
2.10.1.6.1. Schedule Management Plan
2.10.1.6.2. Schedule Management Plan
2.10.1.6.3. Staffing Management Plan
2.10.1.6.4. Risk Register
2.10.2. Output
2.10.2.1. Activity Cost Estimates
2.10.2.2. Activity Cost Estimate Supporting Detail
2.10.2.2.1. documentation of the basis of estimate
2.10.2.2.2. documentation of assumptions/constraints
2.10.2.2.3. documentation of the range
2.10.2.3. Requested Changes
2.10.2.4. Cost Management Plan (Updates)
2.10.3. Tools
2.10.3.1. Analogous Estimating
2.10.3.1.1. estimates based on previous, similar projects
2.10.3.2. Determine Resource Cost Rates
2.10.3.3. Bottom Up Estimating
2.10.3.4. Parametric Estimating
2.10.3.5. Project Management Software
2.10.3.5.1. examples
2.10.3.6. Vendor Bid Analysis
2.10.3.6.1. derive cost from vendor bids
2.10.3.7. Reserve Analysis
2.10.3.7.1. as more info becomes available, use, reduce or eliminate reserves
2.10.3.8. Cost Of Quality
2.10.4. Objectives
2.10.4.1. How much will the resources cost that are needed to complete each specified activity?
2.10.4.2. How much will it cost to maintain and use the project's product?
2.11. Cost Budgeting
2.11.1. Inputs
2.11.1.1. Project Scope Statement
2.11.1.2. WBS
2.11.1.3. WBS
2.11.1.4. WBS Dictionary
2.11.1.5. Activity Cost Estimates
2.11.1.5.1. cost estimates for each activity are aggregated
2.11.1.6. Activity Cost Estimate Supporting Detail
2.11.1.6.1. basis for estimation
2.11.1.6.2. constraints/assumptions
2.11.1.7. Project Schedule
2.11.1.8. Resource Calendars
2.11.1.9. Contract
2.11.1.9.1. cost information for purchased products
2.11.1.10. Cost Management Plan
2.11.2. Outputs
2.11.2.1. Cost Baseline
2.11.2.1.1. authorized time-phased budget at completion
2.11.2.1.2. typically displayed in the form of an S-curve
2.11.2.1.3. a component of the PMP
2.11.2.1.4. used to measure, monitor and control overall cost performance
2.11.2.2. Project Funding Requirements
2.11.2.2.1. derived from the cost baseline
2.11.2.2.2. cost baseline + margin
2.11.2.3. Cost Management Plan (Updates)
2.11.2.4. Requested Changes
2.11.3. Tools
2.11.3.1. Cost Aggregation
2.11.3.1.1. cost estimates are aggregated by work packages according to the WBS
2.11.3.2. Reserve Analysis
2.11.3.2.1. create reserves
2.11.3.3. Parametric Estimating
2.11.3.4. Funding Limit Reconciliation
2.11.3.4.1. reconcile expenditure with funding limits
2.11.4. Objectives
2.11.4.1. what will be the total cost of resources required to complete the project?
2.11.4.2. what will be the project funding requirements?
2.12. Quality Planning
2.12.1. Inputs
2.12.1.1. Enterprise Environmental Factors
2.12.1.2. Organizational Process Assets
2.12.1.2.1. quality policy of the performing organization may be adopted
2.12.1.2.2. if an organizational quality policy does not exists, the project needs to create its own policy
2.12.1.3. Project Scope Statement
2.12.1.4. Project Management Plan
2.12.2. Outputs
2.12.2.1. Quality Management Plan
2.12.2.1.1. definition
2.12.2.1.2. must address
2.12.2.2. Quality Metrics
2.12.2.2.1. describes what something is and how the quality control process measures it
2.12.2.3. Quality Checklist
2.12.2.4. Process Improvement Plan
2.12.2.4.1. Subsidiary of the PMP
2.12.2.4.2. steps for identifying activities that do not add any value
2.12.2.4.3. areas to consider
2.12.2.5. Quality Baseline
2.12.2.5.1. records the quality objectives
2.12.2.5.2. basis for measuring and reporting quality performance
2.12.2.6. Project Management Plan (Updates)
2.12.2.6.1. additions
2.12.2.6.2. requested changes
2.12.3. Tools
2.12.3.1. Cost Benefit Analysis
2.12.3.1.1. Consider Cost-Benefits Tradeoffs
2.12.3.1.2. benefits of meeting quality standards
2.12.3.1.3. costs of meeting quality standards
2.12.3.2. Benchmarking
2.12.3.2.1. comparing actual or planned project practices to those of other projects
2.12.3.2.2. generate ideas for improvement
2.12.3.2.3. find basis for measuring performance
2.12.3.3. Design of Experiments
2.12.3.3.1. Determine the type and number of tests
2.12.3.3.2. Detemine the impact of tests on cost of quality
2.12.3.3.3. definition
2.12.3.4. Cost of Quality
2.12.3.4.1. two types of costs
2.12.3.5. Additional Quality Tools
2.12.3.5.1. purpose
2.12.3.5.2. examples
2.12.4. Objectives
2.12.4.1. How will we deliver a product that will delight our customers?
2.13. Human Resource Planning
2.13.1. Inputs
2.13.1.1. enterprise environmental factors
2.13.1.1.1. organizational culture and structure
2.13.1.1.2. existing human resources
2.13.1.1.3. personnel administration policies
2.13.1.1.4. marketplace conditions
2.13.1.2. organizational assets
2.13.1.2.1. standard processes, policies and role descriptions
2.13.1.2.2. standard policies, processes and role descriptions
2.13.1.2.3. templates for org charts and position descriptions
2.13.1.2.4. historical information on organizational structures that have worked in previous projects
2.13.1.3. project management plan
2.13.1.3.1. Activity Resource Requirements
2.13.2. Tools
2.13.2.1. organizational charts and position descriptions
2.13.2.1.1. document team member roles and responsibilities
2.13.2.1.2. objectives
2.13.2.1.3. three types
2.13.2.2. networking
2.13.2.2.1. definition
2.13.2.2.2. constructive way to understand human factors that influence the effectiveness of staffing management options
2.13.2.3. organizational theory
2.13.2.3.1. Organizational theory provides information regarding the ways that people, teams, and organizational units behave
2.13.3. Outputs
2.13.3.1. roles and responsibilities
2.13.3.1.1. role
2.13.3.1.2. responsibility
2.13.3.1.3. authority
2.13.3.1.4. competency
2.13.3.2. project organizational charts
2.13.3.2.1. A project organization chart is a graphic display of project team members and their reporting relationships
2.13.3.3. staffing management plan
2.13.3.3.1. describes when and how human resource requirements will be met
2.13.3.3.2. items to consider
2.13.4. Objectives
2.13.4.1. how will we aquire and manage the people required to complete this project
2.14. Communications Planning
2.14.1. Inputs
2.14.1.1. enterprise environmental factors
2.14.1.2. organizational process assets
2.14.1.2.1. especially historical information and lessons learned
2.14.1.3. project scope statement
2.14.1.3.1. stakeholder analysis is part of the project scope
2.14.1.4. project management plan
2.14.1.4.1. constraints
2.14.1.4.2. assumptions
2.14.2. Tools
2.14.2.1. communications requirements analysis
2.14.2.1.1. results in the sum of the information needs of the project stakeholders
2.14.2.1.2. communicate only when necessary to avoid overwhelming stakeholders with minutiae
2.14.2.1.3. who will communicate with whom
2.14.2.2. communications technology
2.14.3. Outputs
2.14.3.1. communications management plan
2.14.3.1.1. stakeholder communication requirements
2.14.3.1.2. information to be communicated
2.14.3.1.3. person sending the info
2.14.3.1.4. person receiving the info
2.14.3.1.5. method of sending the info
2.14.3.1.6. frequency of communication
2.14.3.1.7. escalation process
2.14.3.1.8. methods of updating and refining the communications management plan
2.14.3.1.9. glossary of common technology
2.14.4. Objectives
2.14.4.1. how can we ensure that all information of interest to each stakeholder is provided in a timely manner and in a meaningful form?
2.15. Risk Management Planning
2.15.1. Inputs
2.15.1.1. Enterprise Environmental Factors
2.15.1.1.1. Risk attitudes and risk tolerance
2.15.1.2. Organizational Process Assets
2.15.1.2.1. risk categories
2.15.1.2.2. concepts and terms
2.15.1.2.3. standard templates
2.15.1.2.4. roles and responsibilities
2.15.1.2.5. authority levels
2.15.1.3. Project Scope Statement
2.15.1.4. Project Management Plan
2.15.2. Tools
2.15.2.1. Planning Meetings and Analysis
2.15.2.1.1. basic plans for conducting the risk management activities are defined
2.15.2.1.2. risk cost elements and schedule activities will be developed
2.15.2.1.3. risk responsibilities will be assigned
2.15.2.1.4. general organizational templates will be tailored
2.15.3. Outputs
2.15.3.1. Risk Management Plan
2.15.3.1.1. describes how risk management will be structured and performed
2.15.3.1.2. includes
2.15.4. Objectives
2.15.4.1. What is needed to manage risk on this project?
2.16. Risk Identification
2.16.1. Inputs
2.16.1.1. Enterprise Environmental Factors
2.16.1.2. Organizational Process Assets
2.16.1.2.1. information on prior projects
2.16.1.3. Project Scope Statement
2.16.1.3.1. project assumptions are found in the scope statement
2.16.1.3.2. project assumptions are found in the scope statement
2.16.1.3.3. uncertainty in assumptions should be evaluated as potential cause for risks
2.16.1.4. Risk Management Plan
2.16.1.5. Project Management Plan
2.16.1.5.1. understanding of schedule, cost and quality
2.16.2. Tools
2.16.2.1. Documentation Review
2.16.2.1.1. a structured review of project documentation
2.16.2.1.2. include plans and assumptions
2.16.2.2. Information Gathering Techniques
2.16.2.2.1. brainstorming
2.16.2.2.2. delphi
2.16.2.2.3. interviewing
2.16.2.2.4. root cause identification
2.16.2.2.5. SWOT analysis
2.16.2.3. Checklist Analysis
2.16.2.3.1. based on historical info and knowledge
2.16.2.3.2. the lowest level of the RBS can be used as a checklist
2.16.2.4. Assumptions Analysis
2.16.2.5. Diagramming Techniques
2.16.2.5.1. cause-and-effect diagrams
2.16.2.5.2. system or process flowcharts
2.16.2.5.3. influence diagrams
2.16.3. Outputs
2.16.3.1. risk register
2.16.3.1.1. list of identified risks
2.16.3.1.2. list of potential responses
2.16.3.1.3. root causes of risk
2.16.3.1.4. updated risk categories
2.16.4. Objectives
2.16.4.1. what risks might affect my project?
2.17. Qualitative Risk Analysis
2.17.1. Inputs
2.17.1.1. Organizational Process Assets
2.17.1.1.1. Data about risks on past projects and lessons learned
2.17.1.2. Project Scope Statement
2.17.1.2.1. projects of a recurrent type tend to have more well-understood risks
2.17.1.3. Risk Management Plan
2.17.1.4. Risk Register
2.17.2. Tools
2.17.2.1. Risk Propability and Impact Assessment
2.17.2.1.1. investigate the likelihood that each specific risk will occur
2.17.2.1.2. investigate the effect on a project objective such as time, cost, scope, quality
2.17.2.2. Propability and Impact Matrix
2.17.2.3. Risk Data Quality Assessment
2.17.2.3.1. The use of low quality risk data may lead to a qualitative risk analysis of little use
2.17.2.4. Risk Categorization
2.17.2.5. Risk Urgency Assessment
2.17.3. Outputs
2.17.3.1. Risk Register (Updates)
2.17.4. Objectives
2.17.4.1. Which risks are so severe that I must deal with them proactively?
2.18. Quantitative Risk Analysis
2.18.1. Inputs
2.18.1.1. Organizational Process Assets
2.18.1.1.1. Information on prior, similar projects
2.18.1.1.2. studies of similar projects by risk specialists
2.18.1.1.3. risk databases that may be available from industry or proprietary sources
2.18.1.2. Project Scope Statement
2.18.1.3. Risk Management Plan
2.18.1.3.1. roles and responsibilities for conducting risk management
2.18.1.3.2. budgets
2.18.1.3.3. activities for risk management
2.18.1.3.4. risk categories
2.18.1.3.5. RBS
2.18.1.3.6. risk tolerances of stakeholders
2.18.1.4. Risk Register
2.18.1.4.1. list of identified risks
2.18.1.4.2. ranking or priority list of risks
2.18.1.4.3. risks grouped by category
2.18.1.5. Project Management Plan
2.18.1.5.1. Project Schedule Management Plan
2.18.1.5.2. Project Cost Management Plan
2.18.2. Tools
2.18.2.1. Data Gathering and Representation Techniques
2.18.2.1.1. Interviewing
2.18.2.1.2. Probability Distributions
2.18.2.1.3. Expert Judgement
2.18.2.2. Quantitative Risk Analysis and Modeling Techniques
2.18.2.2.1. Sensitivity Analysis
2.18.2.2.2. Expected Monetary Value Analysis
2.18.2.2.3. Decision Tree Analysis
2.18.2.2.4. Modeling and Simulation
2.18.3. Outputs
2.18.3.1. Risk Register (Updates)
2.18.4. Objectives
2.18.4.1. How do we deal with risks whose impacts are to complicated to assess using qualitative tools?
2.19. Risk Response Planning
2.19.1. Inputs
2.19.1.1. Risk Management Plan
2.19.1.2. Risk Register
2.19.2. Tools
2.19.2.1. Strategies for negative risks or threats
2.19.2.1.1. avoid
2.19.2.1.2. transfer
2.19.2.1.3. mitigate
2.19.2.2. Strategies for positive risks or opportunities
2.19.2.2.1. exploit
2.19.2.2.2. share
2.19.2.2.3. enhance
2.19.2.3. Strategies for both threats and opportunities
2.19.2.3.1. acceptance
2.19.2.4. Contingent Response Strategy
2.19.2.4.1. make a response plan that will only be executed under certain conditions
2.19.2.4.2. trigger events must be defined and tracked
2.19.3. Outputs
2.19.3.1. Risk Register (Updates)
2.19.3.1.1. adds agreed upon response strategies to each risk
2.19.3.1.2. budgets and schedule activities required to implement the chosen responses
2.19.3.2. Project Management Plan (Updates)
2.19.3.3. Risk Related Contractual Agreements
2.19.3.3.1. specify each party's responsibility for specific risks
2.19.3.3.2. insurance
2.19.3.3.3. services
2.19.4. Objectives
2.19.4.1. What will we do proactively to minimize the impact of high severity risks on our projects?
2.20. Plan Purchases and Aquisitions
2.20.1. Inputs
2.20.1.1. Enterprise Environmental Factors
2.20.1.1.1. Conditions of the Marketplace
2.20.1.1.2. What products, services and results are available in the marketplace
2.20.1.1.3. where and from whom are they available
2.20.1.1.4. What terms and conditions
2.20.1.2. Organizational Process Assets
2.20.1.2.1. Procurement related
2.20.1.2.2. Organizational policies frequently constrain procurement decisions
2.20.1.3. Project Scope Statement
2.20.1.3.1. Requirements withcontractual and legal implications
2.20.1.4. Work Breakdown Structure
2.20.1.5. WBS Dictionary
2.20.1.6. Project Management Plan
2.20.1.6.1. Risk Register
2.20.1.6.2. Risk Related Contractual Agreements
2.20.1.6.3. Resource Requirements
2.20.1.6.4. Project Schedule
2.20.1.6.5. Activity Cost Estimates
2.20.1.6.6. Cost Baseline
2.20.2. Tools
2.20.2.1. Make-or-Buy Analysis
2.20.2.1.1. used to determine whether a product or service should be produced or purchased
2.20.2.1.2. A buy decision may mean purchase or rent
2.20.2.1.3. The analysis includes direct and indirect costs
2.20.2.1.4. Decision also reflects the perspective of the organization
2.20.2.2. Expert Judgement
2.20.2.3. Contract Types
2.20.2.3.1. Fixed Price Contracts
2.20.2.3.2. Cost Reimbursable Contracts
2.20.2.3.3. Time And Material (T&M) Contracts
2.20.3. Outputs
2.20.3.1. Procurement Management Plan
2.20.3.1.1. describes how the procurement processes will be managed
2.20.3.1.2. can include guidance for
2.20.3.2. Contract Statement of Work
2.20.3.2.1. describes the procurement item in sufficient detail to allow the prospective sellers if they are capable of providing the service or product
2.20.3.3. Make-or-Buy Decisions
2.20.3.3.1. documents the decisions. This may also include insurance policies to address some of the identified risks.
2.20.3.4. Requested Changes
2.20.4. Objectives
2.20.4.1. Should we use outside skills and resources?
2.20.4.2. How can we best manage relationship with our suppliers?
2.21. Plan Contracting
2.21.1. Inputs
2.21.1.1. Procurement Management Plan
2.21.1.2. Contract Statement of Work
2.21.1.3. Make-or-Buy decisions
2.21.1.4. Project Management Plan
2.21.1.4.1. Risk Register
2.21.1.4.2. Risk Related Contractual Agreements
2.21.1.4.3. Activity Resource Requirements
2.21.1.4.4. Project Schedule
2.21.1.4.5. Activity Cost Estimates
2.21.1.4.6. Cost Baseline
2.21.2. Tools
2.21.2.1. Standard Forms
2.21.2.1.1. Standard Contracts
2.21.2.1.2. Standard Description of Procurement Items
2.21.2.1.3. Non-disclosure Agreements
2.21.2.1.4. Proposal Evaluation Criteria Checklists
2.21.2.1.5. Standardized Versions of Bid Documents
2.21.2.2. Expert Judgement
2.21.2.3. Types of Offers
2.21.2.3.1. Bid, Tender or Quotation
2.21.2.3.2. Proposal
2.21.3. Outputs
2.21.3.1. Procurement Documents
2.21.3.1.1. they should be
2.21.3.1.2. they should include
2.21.3.1.3. Objectives
2.21.3.1.4. Minimal Content
2.21.3.1.5. Published in
2.21.3.2. Evaluation Criteria
2.21.3.2.1. Developed to rate or score proposals
2.21.3.2.2. Often included as part of the procurement documents
2.21.3.2.3. common selection criteria
2.21.4. Objectives
2.21.4.1. How should we solicit offers?
2.21.4.2. How can we ensure that the offers will be useful?
2.21.4.3. How will we evaluate the offers?
3. Executing
3.1. Direct and Manage Project Execution
3.1.1. Inputs
3.1.1.1. Project Management Plan
3.1.1.2. Approved Corrective Actions
3.1.1.2.1. Documented, authorized directions to bring future performance into conformance with the project management plan
3.1.1.2.2. Plan to deal with a problem
3.1.1.3. Approved Preventive Actions
3.1.1.3.1. directions that reduce the probability of risks
3.1.1.3.2. Plan to mitigate a risk
3.1.1.4. Approved Change Requests
3.1.1.4.1. authorized changes to project scope, policies, procedures, PMP, schedule, cost or budget
3.1.1.5. Approved Defect Repair
3.1.1.5.1. request for a correction of a defect found during quality inspection
3.1.1.6. Validated Defect Repair
3.1.1.6.1. notification that reinspected repaired items have been accepted or rejected
3.1.1.7. Administrative Closure Procedure
3.1.1.7.1. documents activities, interactions, roles and responsibilities need in executing the administrative closure of the project
3.1.2. Tools
3.1.2.1. Project Management Methodology
3.1.2.1.1. defines a process that aids the project team in executing the project management plan
3.1.2.1.2. Defines project management groups, their processes and the related control functions
3.1.2.2. Project Management Information System
3.1.3. Outputs
3.1.3.1. Deliverables
3.1.3.1.1. Any unique and verifiable product, result or capability to perform a service that is identified in the PMP and must be produced and provided to complete the project
3.1.3.2. Requested Changes
3.1.3.3. Implemented Change Requests
3.1.3.4. Implemented Corrective Actions
3.1.3.5. Implemented Preventive Actions
3.1.3.6. Implemented Defect Repair
3.1.3.7. Work Performance Information
3.1.4. Objectives
3.1.4.1. How do I correctly and appropriately implement my project plan?
3.2. Perfom Quality Assurance
3.2.1. Inputs
3.2.1.1. Quality Management Plan
3.2.1.2. Quality Metrics
3.2.1.3. Process Improvement Plan
3.2.1.4. Work Performance Information
3.2.1.5. Approved Change Requests
3.2.1.6. Quality Control Measurements
3.2.1.7. Implemented Change Requests
3.2.1.8. Implemented Corrective Actions
3.2.1.9. Implemented Defect Repair
3.2.1.10. Implemented Preventive Actions
3.2.2. Tools
3.2.2.1. Quality Planning Tools and Techniques
3.2.2.2. Quality Audits
3.2.2.3. Process Analysis
3.2.2.4. Quality Control Tools and Techniques
3.2.3. Outputs
3.2.3.1. Requested Changes
3.2.3.2. Recommented Corrective Actions
3.2.3.3. Organization Process Assets (Updates)
3.2.3.3.1. Quality Standards
3.2.3.4. Project Management Plan (Updates)
3.2.3.4.1. Quality Management Plan
3.2.3.4.2. Schedule Management Plan
3.2.3.4.3. Cost Management Plan
3.2.4. Objectives
3.2.4.1. How can we be sure that we are really executing our quality management plan?
3.3. Aquire Project Team
3.3.1. Inputs
3.3.1.1. Enterprise Environmental Factors
3.3.1.1.1. Characteristics to consider
3.3.1.2. Organizational Process Assets
3.3.1.3. Roles and Responsibilities
3.3.1.3.1. define the position, skills and competencies that the project requires
3.3.1.4. Project Organization Charts
3.3.1.4.1. provide an overview regarding the number of people required by the project
3.3.1.5. Staffing Management Plan
3.3.1.5.1. identifies the time period each team member will be needed
3.3.2. Tools
3.3.2.1. Pre-Assignment
3.3.2.1.1. Team members are known in advance
3.3.2.1.2. Specific people were promised as part of a competitive proposal
3.3.2.1.3. The project is dependant on the expertise of particular persons
3.3.2.1.4. Some staff assignments are defined within the project charter
3.3.2.2. Negotiation
3.3.2.2.1. functional managers
3.3.2.3. Acquisition
3.3.2.3.1. required services can be aquired from outside sources
3.3.2.4. Virtual Teams
3.3.2.4.1. Group of people with a shared goal who spend little or no face-to-face time
3.3.3. Outputs
3.3.3.1. Project Staff Assignments
3.3.3.1.1. Documentation can include
3.3.3.1.2. Assignment often documented in the Responsibility Assignment Matrix (RAM)
3.3.3.1.3. Asignment loading shown through a resource histogram
3.3.3.2. Resource Availability
3.3.3.2.1. documents the availability period of each team member
3.3.3.2.2. requires understanding of
3.3.3.3. Staffing Management Plan (Updates)
3.3.4. Objectives
3.3.4.1. How can we get the right people working on the project?
3.4. Develop Project Team
3.4.1. Inputs
3.4.1.1. Project Staff Assignments
3.4.1.1.1. identifies the specific people that will be involved
3.4.1.1.2. missing in PMBok according to Roger:
3.4.1.2. Staffing Management Plan
3.4.1.2.1. identifies training strategies
3.4.1.2.2. rewards and feedback
3.4.1.2.3. disciplinary action
3.4.1.3. Resource Availability
3.4.1.3.1. identifies times that project team members can participate in team development activities
3.4.2. Tools
3.4.2.1. General Management Skills
3.4.2.1.1. Version 4 calls this Tool "Interpersonal Skill"
3.4.2.1.2. soft skill
3.4.2.1.3. understanding sentiemtns of team members
3.4.2.1.4. anticipate their actions
3.4.2.1.5. goal: Reduce problems and increase interaction
3.4.2.2. Training
3.4.2.2.1. all activities designed to enhance the competencies of the project team members
3.4.2.2.2. can be formal
3.4.2.2.3. can be informal
3.4.2.3. Team-Building Activities
3.4.2.3.1. Objectives
3.4.2.3.2. Early involvement of team members desirable
3.4.2.3.3. Should take place throughout the project life cycle
3.4.2.3.4. One of the most important skills in developing a team environment involves handling team problems and discussing them in the team
3.4.2.3.5. Bruce Tuckman: Model of Team Development
3.4.2.4. Ground Rules
3.4.2.4.1. establish clear expectations regarding expectable behaviour
3.4.2.5. Co-Location
3.4.2.5.1. Placing many or all of the most active team members in the same physical location
3.4.2.5.2. A meeting room, sometimes called a "war room"
3.4.2.5.3. Inconsistent with virtual teams
3.4.2.5.4. Can be temporary
3.4.2.6. Recognition and Rewards
3.4.2.6.1. Award decisions are made through project performance appraisals
3.4.2.6.2. Cultural differences should be considered
3.4.2.6.3. Only desirable behaviour should be rewarded
3.4.2.6.4. Win-Lose rewards that only a limited number of team members can achieve may hurt team cohesiveness
3.4.2.6.5. Rewarding behaviour that everyone can achieve tends to improve support among team members
3.4.2.6.6. Elton Mayo: The Hawthorne Effect
3.4.2.6.7. Frederick Herzberg: Hygiene Factors
3.4.3. Outputs
3.4.3.1. Team Performance Assessment
3.4.3.1.1. An informal or formal assessment of the teams effectiveness on the project
3.4.3.1.2. Can include indicators such as
3.4.4. Objectives
3.4.4.1. How do we move from a group of people to a team?
3.5. Information Distribution
3.5.1. Inputs
3.5.1.1. Communications Management Plan
3.5.2. Tools
3.5.2.1. Communications Skills
3.5.2.1.1. Sender: Make the information clear and complete
3.5.2.1.2. Receiver: Confirm that it is properly understood by active feedback
3.5.2.1.3. Dimensions
3.5.2.1.4. Key skills for Project Managers
3.5.2.2. Information Gathering and Retrieval System
3.5.2.2.1. Electronic databases
3.5.2.2.2. Manual filing systems
3.5.2.2.3. Repository for technical documentation
3.5.2.2.4. Project management software
3.5.2.3. Information Distribution Methods
3.5.2.4. Lessons Learned Process
3.5.2.4.1. Update of the lessons learned database
3.5.2.4.2. Input to knowledge management system
3.5.2.4.3. Updated corporate policies, procedures and processes
3.5.2.4.4. Improved business skills
3.5.2.4.5. Overall product and service improvements
3.5.2.4.6. Updates to the risk management plan
3.5.3. Outputs
3.5.3.1. Organizational Process Assets (Updates)
3.5.3.1.1. Lessons learned documentations
3.5.3.1.2. Project records
3.5.3.1.3. Project reports
3.5.3.1.4. Project presentations
3.5.3.1.5. Feedback from stakeholders
3.5.3.1.6. Stakeholder notifications
3.5.3.2. Requested Changes
3.5.4. Objectives
3.5.4.1. How should we gather and organize all the project information?
3.6. Request Seller Responses
3.6.1. Inputs
3.6.1.1. Organizational Process Assets
3.6.1.1.1. list or files with info on qualified bidders
3.6.1.1.2. contain relevant past experience
3.6.1.2. Procurement Management Plan
3.6.1.3. Procurement Documents
3.6.2. Tools
3.6.2.1. Bidder Conference
3.6.2.1.1. meeting with prospective sellers prior to preparing bids or proposals
3.6.2.1.2. Ensure that all prospective sellers have a clear and common understanding of procurement
3.6.2.1.3. Responses to questions can be incorporated into procurement documents as amendment
3.6.2.2. Advertising
3.6.2.2.1. list of sellers can be expanded by placing advertisements into newspapers on professional journals
3.6.2.2.2. Most government jurisdictions require public advertising of procurements
3.6.2.3. Develop Qualified Seller List
3.6.3. Outputs
3.6.3.1. Qualified Sellers List
3.6.3.1.1. List of sellers asked to submit a proposal or quotation
3.6.3.2. Procurement Document Package
3.6.3.2.1. base upon which sellers prepare bid
3.6.3.3. Proposals
3.6.3.3.1. Constitutes a formal and legal offer
3.6.3.3.2. sometimes seller is requested to supplement proposal by oral presentation
3.6.3.3.3. describe the sellers ability and willingness to provide the requested products or services
3.6.4. Objectives
3.6.4.1. How do we support sellers in providing us with useful offers?
3.7. Select Sellers
3.7.1. Inputs
3.7.1.1. Organizational Process Assets
3.7.1.1.1. formal policies that affect the evaluation of proposals
3.7.1.2. Procurement Management Plan
3.7.1.3. Evaluation Criteria
3.7.1.4. Procurement Document Package
3.7.1.5. Proposals
3.7.1.6. Qualified Sellers List
3.7.1.7. Project Management Plan
3.7.2. Tools
3.7.2.1. Weighting System
3.7.2.1.1. a method of minimizing personal prejudice
3.7.2.1.2. a numerical weight is assigned to each criteria
3.7.2.1.3. proposals are weighted on each criterion
3.7.2.1.4. rating is multiplied by weight
3.7.2.1.5. results are summed up to compute a score
3.7.2.2. Independent Estimates
3.7.2.2.1. prepared as a check on proposed pricing
3.7.2.2.2. done by someone familiar with the needs of the project, but no interest in being the seller
3.7.2.2.3. sometimes referred to as a "should-cost" estimate
3.7.2.2.4. Deviations do not necessarily mean the prospective seller is incompetent
3.7.2.3. Screening System
3.7.2.3.1. used to filter out inadequate proposals
3.7.2.3.2. establihing minimum requirements of performance for one or more criteria
3.7.2.3.3. May also use a weighting system or independent estimates
3.7.2.3.4. Generally used to eliminate clearly inadequate proposals without doing a complete evaluation
3.7.2.4. Contract Negotiation
3.7.2.4.1. Clarifies the structure and requirements of the contract
3.7.2.4.2. Come to a mutual agreement with regard to all contract items
3.7.2.4.3. May be an independent process with inputs and outputs
3.7.2.4.4. If the buyer is a large organization, the terms and conditions may be fixed and non-negotiable ("Boiler-Plate")
3.7.2.4.5. The project manager man not be the lead negotiator, but should be present
3.7.2.5. Seller Ratings System
3.7.2.5.1. Provides an assessment of overall reliability of the seller
3.7.2.5.2. Used together with the screening system for an initial evaluation of prospective sellers
3.7.2.5.3. Include seller's
3.7.2.5.4. If selected, performance info used to update the system
3.7.2.6. Expert Judgement
3.7.2.7. Proposal Evaluation Techniques
3.7.2.7.1. Price or cost as the primary determinant
3.7.2.7.2. Proposals
3.7.3. Outputs
3.7.3.1. Selected Sellers
3.7.3.1.1. offers judged to be acceptable
3.7.3.1.2. negotiated an acceptable draft contract
3.7.3.2. Contract
3.7.3.2.1. aka
3.7.3.2.2. Includes
3.7.3.2.3. is a mutually binding legal agreement
3.7.3.2.4. usually in writing, but does not have to be
3.7.3.2.5. Signing authority
3.7.3.3. Contract Management Plan
3.7.3.3.1. a plan to administer the contract
3.7.3.3.2. based upon specific buyer-specified items within the contract
3.7.3.4. Resource Availability
3.7.3.5. Procurement Management Plan (Updates)
3.7.3.6. Requested Changes
3.7.4. Objectives
3.7.4.1. How do we select the best offer?
4. Monitoring and Controlling
4.1. Monitor and Control Project Work
4.1.1. Inputs
4.1.1.1. Project Management Plan
4.1.1.2. Work Performance Information
4.1.1.3. Rejected Change Requests
4.1.2. Tools
4.1.2.1. Project Management Methodology
4.1.2.2. Project Management Information System
4.1.2.2.1. Used to monitor and control the execution of activities
4.1.2.2.2. Used to create new forecasts
4.1.2.3. Earned Value Technique
4.1.2.3.1. measures performance of the project
4.1.2.3.2. provides a means to forecast future performance
4.1.2.4. Expert Judgement
4.1.3. Outputs
4.1.3.1. Recommended Corrective Action
4.1.3.2. Recommended Preventive Actions
4.1.3.3. Forecasts
4.1.3.4. Recommended Defect Repairs
4.1.3.5. Recommended Changes
4.1.4. Objectives
4.1.4.1. How am I doing compared to my plan?
4.1.4.2. Where will I end up with regard to deliverables, time and cost?
4.2. Integrated Change Control
4.2.1. Inputs
4.2.1.1. Project Management Plan
4.2.1.2. Requested Changes
4.2.1.3. Work Performance Information
4.2.1.4. Recommended Corrective Actions
4.2.1.5. Recommended Preventive Actions
4.2.1.6. Recommended Defect Repair
4.2.1.7. Deliverables
4.2.2. Tools
4.2.2.1. Project Management Methodology
4.2.2.2. Project Management Information System
4.2.2.3. Expert Judgement
4.2.3. Outputs
4.2.3.1. Approved Change Requests
4.2.3.2. Rejected Change Requests
4.2.3.3. Project Management Plan (Updates)
4.2.3.4. Project Scope Statement (Updates)
4.2.3.5. Approved Corrective Actions
4.2.3.6. Approved Preventive Actions
4.2.3.7. Approved Defect Repair
4.2.3.8. Validated Defect Repair
4.2.3.9. Delivarables
4.2.4. Objectives
4.2.4.1. Do the benefits of the proposed change justify its cost?
4.2.4.2. Is the recommended action the best solution when every aspect of the project is considered?
4.3. Scope Verification
4.3.1. Inputs
4.3.1.1. Project Scope Statement
4.3.1.2. WBS Dictionary
4.3.1.3. Project Scope Management Plan
4.3.1.4. Deliverables
4.3.2. Tools
4.3.2.1. Inspection
4.3.2.1.1. Includes
4.3.3. Outputs
4.3.3.1. accepted deliverables
4.3.3.1.1. includes
4.3.3.2. requested changes
4.3.3.3. Recommended Corrective Actions
4.3.4. Objectives
4.3.4.1. How can we get the customer to accept (and pay for) the completed deliverables?
4.3.4.2. How will we deal with any non-acceptance issues?
4.4. Scope Control
4.4.1. Inputs
4.4.1.1. Project Scope Statement
4.4.1.2. Work Breakdown Structure
4.4.1.3. WBS Dictionary
4.4.1.4. Project Scope Management Plan
4.4.1.5. Performance Reports
4.4.1.6. Approved Change Requests
4.4.1.7. Work Performance Information
4.4.1.7.1. Provide info on work performance such as completed interim deliverables
4.4.2. Tools
4.4.2.1. Change Control System
4.4.2.1.1. defines the procedure by which the scope can be changed
4.4.2.1.2. includes
4.4.2.1.3. Objectives
4.4.2.1.4. Elements
4.4.2.2. Variance Analysis
4.4.2.2.1. using performance measurement to assess the magnitude of variation
4.4.2.2.2. determining the cause of variance relative to the scope baseline
4.4.2.2.3. Deciding whether corrective action is required
4.4.2.3. Replanning
4.4.2.3.1. approved change requests may require modifications to
4.4.2.4. Configuration Management System
4.4.2.4.1. definition
4.4.2.4.2. Mein Verständnis
4.4.3. Outputs
4.4.3.1. Project Scope Statement (updates)
4.4.3.2. Work Breakdown Structure (Updates)
4.4.3.3. WBS Dictionary (Updates)
4.4.3.4. Scope Baseline (Updates)
4.4.3.5. Requested Changes (Updates)
4.4.3.6. Recommended Corrective Actions (Updates)
4.4.3.7. Organizational Process Assets (Updates)
4.4.3.8. Project Management Plan (Updates)
4.4.4. Objectives
4.4.4.1. How can we determine if the costs of a proposed change can be justified by its benefits?
4.4.4.2. How can we ensure that our change control process is being followed?
4.5. Schedule Control
4.5.1. Inputs
4.5.1.1. Schedule Management Plan
4.5.1.1.1. Establish how the schedule will be controlled
4.5.1.2. Schedule Baseline
4.5.1.2.1. provides the as-planned information
4.5.1.3. Performance Reports
4.5.1.3.1. provides actual performance information
4.5.1.4. Approved Change Requests
4.5.1.4.1. change requests are used to update the schedule
4.5.2. Tools
4.5.2.1. Progress Reporting
4.5.2.1.1. Activities which have started
4.5.2.1.2. Activities in progress
4.5.2.1.3. Activities which have finished
4.5.2.2. Schedule Change Control System
4.5.2.2.1. defines the procedures by which the schedule can be changed
4.5.2.2.2. it includes the paperwork, tracking system and approval levels
4.5.2.3. Performance Measurement
4.5.2.3.1. magnitude of schedule variation measured by Schedule Performance Index or Schedule Variance
4.5.2.3.2. An important part is to decide if corrective actions are required
4.5.2.4. Project Management Software
4.5.2.4.1. provides the ability to track planned dates vs. actual dates
4.5.2.4.2. helps in forecasting the effect of schedule changes
4.5.2.5. Variance Analysis
4.5.2.5.1. compare planned schedule dates with actual/forecast dates to detect deviations
4.5.2.6. Schedule Comparison Bar Charts
4.5.3. Outputs
4.5.3.1. Schedule Model Data (Updates)
4.5.3.2. Schedule Baseline (Updates)
4.5.3.3. Performance Measurements
4.5.3.3.1. calculate
4.5.3.3.2. document them
4.5.3.3.3. communicate them to stakeholders
4.5.3.4. Requested Changes
4.5.3.5. Recommended Corrective Actions
4.5.3.6. Organizational Process Assets (Updates)
4.5.3.6.1. lessons learned to document the cause of variations
4.5.3.7. Activity List (Updates)
4.5.3.8. Activity Attributes (Updates)
4.5.3.9. Project Scope Management Plan (Updates)
4.5.4. Objectives
4.5.4.1. How can I detect changes from my schedule baseline?
4.5.4.2. If I have a choice on spending more time, how can I ensure that the benefits exceed the cost?
4.6. Cost Control
4.6.1. Inputs
4.6.1.1. Cost Baseline
4.6.1.2. Project Funding Requirements
4.6.1.3. Performance Reports
4.6.1.4. Work Performance Information
4.6.1.4.1. completed deliverables
4.6.1.4.2. activities in progress
4.6.1.4.3. activities not started yet
4.6.1.4.4. costs incurred
4.6.1.5. Approved Change Requests
4.6.1.5.1. may affect costs
4.6.1.6. Project Management Plan
4.6.2. Tools
4.6.2.1. Costs Change Control System
4.6.2.1.1. defines the procedures by which the cost baseline may be changed
4.6.2.1.2. includes
4.6.2.2. Performance Measurement Analysis
4.6.2.2.1. Earned Value Technique
4.6.2.3. Forecasting
4.6.2.3.1. make predictions based on info available at the time of the prediction
4.6.2.3.2. Budget at completion (BAC)
4.6.2.3.3. Estimated to Complete (ETC)
4.6.2.3.4. Estimated at Completion (EAC)
4.6.2.4. Project Performance Reviews
4.6.2.4.1. Meetings held to assess cost status or progress
4.6.2.4.2. Performance Reporting Techniques
4.6.2.5. Project Management Software
4.6.2.5.1. spreadsheet to monitor PV vs AC
4.6.2.6. Variance Management
4.6.2.6.1. Cost Management Plan describes how cost variances will be managed
4.6.2.6.2. For example, different responses to major or minor problems
4.6.2.6.3. Amount of variance tends to decrease as more work is accomplished
4.6.3. Outputs
4.6.3.1. Cost Estimates (Updates)
4.6.3.2. Cost Baseline (Updates)
4.6.3.3. Performance Measurements
4.6.3.4. Forecasted Completion
4.6.3.5. Requested Changes
4.6.3.6. Recommended Corrective Actions
4.6.3.7. Organizational Process Assets (Updates)
4.6.3.7.1. Lessons Learned
4.6.3.8. Project Management Plan (Updates)
4.6.4. Objectives
4.6.4.1. How do I Recognize and Manage Cost Variances in my Project?
4.6.4.2. How can I ensure that changes to my cost baseline are justified by the benefits?
4.7. Perform Quality Control
4.7.1. Inputs
4.7.1.1. Quality Management Plan
4.7.1.2. Quality Metrics
4.7.1.3. Quality Checklists
4.7.1.4. Organizational Process Assets
4.7.1.5. Work Performance Information
4.7.1.5.1. technical performance measures
4.7.1.5.2. deliverables completion status
4.7.1.5.3. implementation of required corrective action
4.7.1.6. Approved Change Requests
4.7.1.6.1. may include
4.7.1.6.2. need to verify timely correct implementation of approved changes
4.7.1.7. Deliverables
4.7.2. Tools
4.7.2.1. Cause and Effect Diagram
4.7.2.1.1. aka
4.7.2.1.2. shows cause-effect chain
4.7.2.2. Control Charts
4.7.2.2.1. Used to determine whether or not a process is stable
4.7.2.2.2. Illustrates how a process behaves over time
4.7.2.2.3. Can be used to assess whether the application of process changes resulted in the desired improvements
4.7.2.2.4. The upper control limit and the lower control limit are usually set at +/- 3 sigma
4.7.2.2.5. Can be used for both project and product life cycle processes
4.7.2.3. Flowcharting
4.7.2.3.1. helps to analyze how problems occur
4.7.2.3.2. flowchart is a graphical representation of the process
4.7.2.4. Histogram
4.7.2.4.1. bar chart showing a distribution of variables
4.7.2.4.2. each column represents an attribute
4.7.2.4.3. the height of the column represents the relative frequency of the characteristic
4.7.2.5. Pareto Charts
4.7.2.5.1. histogram, ordered by frequency of occurence
4.7.2.5.2. used to guide corrective action: fix the problems that are causing the greatest number of defect first
4.7.2.5.3. Related to Pareto's Law (80/20 rule)
4.7.2.6. Run Chart
4.7.2.6.1. a line graph showing data points plotted in the order in which they occur
4.7.2.6.2. shows trends in a process over time
4.7.2.6.3. used to perform trend analysis to forecast future outcome
4.7.2.7. Scatter Diagram
4.7.2.7.1. correlation of two values
4.7.2.7.2. shows the pattern of relationship between two variables
4.7.2.8. Statistical Sampling
4.7.2.8.1. choose a part of a population for inspection
4.7.2.9. Inspection
4.7.2.9.1. Examination of the work product to determine whether it conforms to standards
4.7.2.9.2. Generally includes measurements
4.7.2.9.3. also called
4.7.2.10. Defect Repair Review
4.7.2.10.1. action taken to ensure that product defects are repaired and brought into compliance with requirements or specifications
4.7.3. Outputs
4.7.3.1. Quality Control Measurements
4.7.3.1.1. Results of the application of the various tools and techniques
4.7.3.2. Validated Defect Repair
4.7.3.3. Quality Baseline (Updates)
4.7.3.4. Recommended Corrective Action
4.7.3.5. Recommended Preventive Actions
4.7.3.6. Requested Changes
4.7.3.7. Recommended Defect Repair
4.7.3.8. Organization Process Assets (Updates)
4.7.3.8.1. completed checklists
4.7.3.8.2. lessons learned documentation
4.7.3.8.3. causes of variances
4.7.3.8.4. reasoning behind the corrective action chosen
4.7.3.9. Validated Deliverables
4.7.3.10. Project Management Plan (Updates)
4.7.4. Objectives
4.7.4.1. How will we ensure that we can deliver what we promised?
4.8. Manage Project Team
4.8.1. Input
4.8.1.1. Organizational Process Assets
4.8.1.1.1. Utilize Organization's System for Rewarding Employees
4.8.1.2. Project Staff Assignments
4.8.1.2.1. provide a list of project team members to be evaluated
4.8.1.3. Roles and Responsibilities
4.8.1.4. Project Organization Charts
4.8.1.4.1. provide a picture of the reporting relationships
4.8.1.5. Staffing Management Plan
4.8.1.5.1. lists the time periods that team members are expected to work on the project
4.8.1.6. Team Performance Assessment
4.8.1.7. Work Performance Information
4.8.1.7.1. provides key input with regard to project objectives
4.8.1.7.2. Observation and conversation provides really useful data
4.8.1.8. Performance Reports
4.8.2. Tools
4.8.2.1. Observation and Conversation
4.8.2.1.1. Tracking team member performance
4.8.2.1.2. Providing feedback
4.8.2.1.3. Resolving issues
4.8.2.1.4. Coordinating changes to enhance performance
4.8.2.2. Project Performance Appraisals
4.8.2.2.1. Objectives
4.8.2.2.2. Need depends on
4.8.2.2.3. Provided by
4.8.2.3. Conflict Management
4.8.2.3.1. most frequent sources of conflict
4.8.2.3.2. questions to think about
4.8.2.3.3. reduce amount of conflict by
4.8.2.3.4. Thomas Killman Conflict Model
4.8.2.3.5. facilitation
4.8.2.3.6. guideline to succesfull conflict resolution
4.8.2.4. Issue Log
4.8.2.4.1. Documents who is responsible for a specific issue
4.8.2.4.2. Target Date
4.8.2.4.3. Track progress
4.8.2.4.4. Document completion and lessons learned
4.8.3. Outputs
4.8.3.1. Requested Changes
4.8.3.2. Recommended Corrective Actions
4.8.3.2.1. Staffing changes
4.8.3.2.2. Additional training
4.8.3.2.3. Disciplinary actions
4.8.3.2.4. Moving people to different assignments
4.8.3.2.5. Outsourcing some work
4.8.3.2.6. Replacing team members
4.8.3.2.7. Give out recognition and rewards
4.8.3.3. Recommended Preventive Actions
4.8.3.3.1. Providing cross-training (mitigate team member absences)
4.8.3.3.2. Additional role clarification
4.8.3.3.3. added personal time
4.8.3.4. Organization Process Assets (Updates)
4.8.3.4.1. input to organizational performance appraisals
4.8.3.4.2. lessons learned documentation
4.8.3.5. Project Management Plan (Updates)
4.8.4. Objectives
4.8.4.1. How do we deal with issues that interfere with team cohesiveness and productivity?
4.9. Performance Reporting
4.9.1. Inputs
4.9.1.1. Work Performance Information
4.9.1.1.1. completion status of the deliverables
4.9.1.2. Performance Measurements
4.9.1.3. Forecasted Completion
4.9.1.4. Quality Control Measurements
4.9.1.5. Project Management Plan
4.9.1.5.1. Performance measurement baseline, against which execution is compared
4.9.1.6. Approved Change Requests
4.9.1.7. Deliverables
4.9.2. Tools
4.9.2.1. Information Presentation Tools
4.9.2.1.1. Table Reporting Software (Excel)
4.9.2.1.2. Mapping Software (MindManager)
4.9.2.1.3. Presentation Software (PowerPoint)
4.9.2.1.4. Graphics Software (Visio)
4.9.2.2. Performance Information, Gathering and Compilation
4.9.2.2.1. manual filing systems
4.9.2.2.2. electronic databases
4.9.2.2.3. project management software
4.9.2.2.4. engineering drawings
4.9.2.2.5. design specifications
4.9.2.2.6. test plans
4.9.2.3. Status Review Meetings
4.9.2.3.1. regularly scheduled events to exchange information about the project
4.9.2.3.2. Held at various frequencies and on different levels
4.9.2.3.3. look back one cycle and forward three cycles
4.9.2.4. Time Reporting Systems
4.9.2.4.1. represents an overhead cost
4.9.2.4.2. make as simple as possible consistent with adequate project control
4.9.2.4.3. align reporting units with the way the work will actually be done
4.9.2.4.4. Time spent is just history and is a poor forecast tool
4.9.2.5. Cost Reporting Systems
4.9.2.5.1. often provided outside project team control
4.9.2.5.2. May not be timely enough or in a form that is useful for project control
4.9.2.5.3. may be unnecessary if most of the project cost is for human resources
4.9.3. Outputs
4.9.3.1. Performance Reports
4.9.3.1.1. Organize and summarize the performance data
4.9.3.1.2. Present the results of any analysis relative to the baseline
4.9.3.1.3. Should be tailored to the needs of the individual stakeholders to show the status of project activities being performed.
4.9.3.1.4. Common formats
4.9.3.2. Forecasts
4.9.3.3. Requested Changes
4.9.3.4. Recommended Corrective Actions
4.9.3.5. Organizational Process Assets (Updates)
4.9.4. Objectives
4.9.4.1. How are we doing on the project releative to our baseline plans?
4.9.4.2. What will our final project cost and timing be?
4.10. Manage Stakeholders
4.10.1. Inputs
4.10.1.1. Communications Management Plan
4.10.1.1.1. needs and expectations of stakeholders are identified and analyzed and documented in the communications management plan
4.10.1.2. Organization Process Assets
4.10.1.2.1. templates
4.10.1.2.2. checklists
4.10.2. Tools
4.10.2.1. Communications Methods
4.10.2.1.1. successful communications is when sender and receiver reach a common understanding of both information and perspective
4.10.2.1.2. Sender
4.10.2.1.3. Message
4.10.2.1.4. Channel or Medium
4.10.2.1.5. Receiver
4.10.2.1.6. Feedback
4.10.2.1.7. Context
4.10.2.2. Issue Logs
4.10.2.2.1. used to document and monitor the resolution of issues
4.10.2.2.2. issues are any point or matter
4.10.2.2.3. an issue must be stated in a way that it is clear what is required for its resolution
4.10.2.2.4. an owner is assigned
4.10.2.2.5. a target date is established for closure
4.10.2.2.6. documents closure details
4.10.3. Outputs
4.10.3.1. Resolved Issues
4.10.3.2. Approved Change Requests
4.10.3.3. Approved Corrective Actions
4.10.3.4. Organizational Process Assets (Updates)
4.10.3.5. Project Management Plan (Updates)
4.10.4. Objectives
4.11. Risk Monitoring and Control
4.11.1. Inputs
4.11.1.1. Risk Management Plan
4.11.1.2. Risk Register
4.11.1.3. Approved Change Requests
4.11.1.3.1. Can generate risks
4.11.1.3.2. Changes exposure to identified risks
4.11.1.4. Work Performance Information
4.11.1.5. Performance Reports
4.11.2. Tools
4.11.2.1. Risk Reassessment
4.11.2.1.1. Identification of new risks
4.11.2.1.2. Reassessment of identified risks
4.11.2.1.3. Should be regularly scheduled as an agenda item at project team status meetings
4.11.2.2. Risk Audits
4.11.2.2.1. Examine and document the effectiveness of
4.11.2.3. Variance and Trend Analysis
4.11.2.4. Technical Performance Measurement
4.11.2.4.1. compares technical performance against performance baseline
4.11.2.4.2. Deviations can identify risks to achieving the project's scope
4.11.2.5. Reserve Analysis
4.11.2.5.1. Compares the amount of the contingency reserves remaining to the amount of risk remaining
4.11.2.5.2. Determine if the reserve is adequate
4.11.2.6. Status Meetings
4.11.3. Outputs
4.11.3.1. Risk Register (Updates)
4.11.3.1.1. Outcomes of
4.11.3.2. Requested Changes
4.11.3.2.1. Imlementing contingency plans or workarounds may change risk exposure
4.11.3.2.2. May result in changes to risk response
4.11.3.2.3. Changes should be reviewd through Integrated Change Control
4.11.3.3. Recommended Corrective Actions
4.11.3.4. Recommended Preventive Actions
4.11.3.5. Organizational Process Assets
4.11.3.5.1. Templates for the risk management plan
4.11.3.5.2. Probability and impact matrix
4.11.3.5.3. Risk register
4.11.3.5.4. Lessons learned
4.11.3.5.5. Data on the actual costs and durations of project activities
4.11.3.6. Project Management Plan (Updates)
4.11.4. Objectives
4.11.4.1. How can we ensure that our risk plan is being implemented?
4.11.4.2. What do we need to keep our risk plan current?
4.12. Contract Administration
4.12.1. Inputs
4.12.1.1. Contract
4.12.1.2. Contract Management Plan
4.12.1.3. Selected Sellers
4.12.1.4. Performance Reports
4.12.1.4.1. Seller-developed technical documentation
4.12.1.4.2. Other deliverables information
4.12.1.4.3. Seller performance reports
4.12.1.5. Approved Change Requests
4.12.1.5.1. Contract terms and conditions
4.12.1.5.2. Statement of work
4.12.1.5.3. Pricing
4.12.1.5.4. Description of the products, services or results to be provided
4.12.1.6. Work Performance Information
4.12.1.6.1. Extent to which quality standards are being met
4.12.1.6.2. What costs have been incurred or committed
4.12.1.6.3. Seller invoices
4.12.1.6.4. Which deliverables have been completed
4.12.2. Tools
4.12.2.1. Contract Change Control System
4.12.2.1.1. Defines the process by which the contract can be changed
4.12.2.1.2. Includes
4.12.2.1.3. Integrated with the project Integrated Change Control System
4.12.2.2. Buyer-Conducted Performance Review
4.12.2.2.1. A structured review of the seller's progress to deliver project scope and quality, within cost and on schedule, as compared to the contract
4.12.2.2.2. May include
4.12.2.2.3. Objective is to identify
4.12.2.3. Inspections and Audits
4.12.2.3.1. Used to identify any weaknesses in the seller's work processes or deliverables
4.12.2.3.2. May include buyer procurement personnel
4.12.2.4. Performance Reporting
4.12.2.5. Payment System
4.12.2.5.1. Usually handled by the accounts payable system of the buyer
4.12.2.5.2. Large projects may have its own payment system
4.12.2.5.3. Includes appropriate reviews and approvals by the project management team
4.12.2.5.4. Payments are made in accordance with the terms of contract
4.12.2.6. Claims Administration
4.12.2.6.1. Types of claims
4.12.2.6.2. Handled as specified in the contract
4.12.2.7. Records Management System
4.12.2.7.1. a specific set of
4.12.2.7.2. Automation tools used to manage contract documentation and records
4.12.2.7.3. Maintains an index of contract documents and correspondence
4.12.2.7.4. Assists with retrieving and archiving documentation
4.12.2.8. Information Technology
4.12.3. Outputs
4.12.3.1. Contract Documentation
4.12.3.1.1. Contract
4.12.3.1.2. Supporting Schedules
4.12.3.1.3. Requested unapproved contract changes
4.12.3.1.4. Approved Change Requests
4.12.3.1.5. Any seller developed technical documentation
4.12.3.1.6. Deliverables
4.12.3.1.7. Seller Performance Reports
4.12.3.1.8. Warranties
4.12.3.1.9. Financial Documents
4.12.3.1.10. The result of contract related inspections
4.12.3.1.11. Any other work performance information
4.12.3.2. Requested Changes
4.12.3.3. Recommended Corrective Actions
4.12.3.4. Organization Process Assets
4.12.3.4.1. Correspondence with seller
4.12.3.4.2. Payment schedule and requests
4.12.3.4.3. Seller performance evaluation documentation
4.12.3.5. Project Management Plan (Updates)
4.12.4. Objectives
4.12.4.1. How do we manage supplier performance?
5. Closing
5.1. Close Project
5.1.1. Inputs
5.1.1.1. Project Management Plan
5.1.1.2. Contract Documentation
5.1.1.2.1. This is relevant only if suppliers are involved and is used to perform the contract closure process.
5.1.1.3. Enterprise Environmental Factors
5.1.1.4. Organizational Process Assets
5.1.1.5. Work Performance Information
5.1.1.6. Deliverables
5.1.2. Tools
5.1.2.1. Project Management Methodology
5.1.2.2. Project Management Information System
5.1.2.3. Expert Judgement
5.1.3. Outputs
5.1.3.1. Administrative Closure Procedure
5.1.3.1.1. Actions and activities necessary to
5.1.3.2. Contract Closure Procedure
5.1.3.3. Final Product, Service or Result
5.1.3.4. Organizational Process Assets (Updates)
5.1.4. Objectives
5.1.4.1. Are we ready to accept and pay for the deliverables from our suppliers?
5.1.4.2. Is our customer ready to accept and pay for the project's product?
5.2. Contract Closure
5.2.1. Inputs
5.2.1.1. Procurement Management Plan
5.2.1.2. Contract Management Plan
5.2.1.3. Contract Documentation
5.2.1.4. Contract Closure Procedure
5.2.2. Tools
5.2.2.1. Procurement Audits
5.2.2.1.1. A structured review of the procurement processes
5.2.2.1.2. Seeks to identify procurement successes and failures
5.2.2.2. Records Management System
5.2.3. Outputs
5.2.3.1. Closed Contracts
5.2.3.1.1. The Contract Closure Process
5.2.3.1.2. In multi-phase contracts may close only a phase of the project
5.2.3.1.3. Unresolved claims may be subject to litigation after contract closure
5.2.3.1.4. Early termination
5.2.3.1.5. The buyer provides the seller with a formal written notice that the contract has been completed
5.2.3.2. Organizational Process Assets (Updates)
5.2.3.2.1. Contract File
5.2.3.2.2. Deliverable acceptance
5.2.3.2.3. Lessons learned documentation
5.2.4. Objectives
5.2.4.1. How should we manage the conclusion of the supplier's work?