Chapter Notes - Foundational Terms and Concepts - PMP
Chapter Notes - Foundational Terms and Concepts - PMP
Process:
- Something that does or creates something necessary and valuable for the project
- There are 49 total processes
- Consist of three things: Inputs, Tools and Outputs
- May be performed more than one time in a single project
Phase:
- Larger projects are broken down into smaller units
- Each phase should produce one or more deliverables; each deliverable is then evaluated to determine if the
next phase may begin
- Decision is known as an “exit gate”
- Kill points are used at the same point as exit gates, but will determine if the project will be terminated
Project:
- A temporary endeavor undertaken to create a unique product, service or result
- For something to be a project, it must be time-limited and unique
Program:
- Group of related projects that are coordinated together
- Not every project will belong to a program, but all programs are made up of project
Progressive Elaboration:
- Not all characteristics of a project are known at the beginning
- Characteristics may be revisited and refined often
Historical Information:
- Also known as “Organizational Process Assets
- Found within your organization
- Used to help predict trends and avoid mistakes
- Used heavily during planning activities
Baseline:
- Version of the plan that exists once the plan is stabilized
- The original plan plus all approved changes
- If charges are approved, the new plan becomes the baseline
Lesson Learned:
- Focused on variances between the plan and the results
Regulations:
- Compliance is mandatory
- Issued by government or other official organizations
Standards:
- Compliance is not mandatory, but may be helpful
Project Manager:
- Ultimately responsible for the outcome
- Empowered to use organizational resources
- Authorized to spend budget
- Authorized to make decisions
Project Coordinator:
- Significantly weaker than a Project Manager
- May bot be allowed to make budget or overall project decisions
- Authorized to reassign resources
Project Expeditor:
- Staff assistant who has little or no formal authority
- Responsible for ensuring things arrive on time and tasks are completed
Stakeholder:
- People whose interests may be positively or negatively affected as a result of execution/completion
Program Manager:
- A project manager manages all the details of a project and report status information to this person
Project Context:
- Organizational environment where the project is carried out
Types of Organizations:
- Organic Teams naturally form
- Functional Team members work for a department
- Matrix Members have a functional manager and a Project Manager
- Projectized Structured according to projects not functions
- Virtual Distributed team
- Composite Mix of functional and projectized structures
Triple Constraint:
- Concept that scope, time and costs are closely related
- Once can not change without affecting at least one other factor
Project Charter:
- Created during the Develop Project Charter process
- Created based on need
- Usually written by the sponsor or customer
- Signed by performing organizations sponsor
- Names the Project Manager and gives authority to spend money
- Documents risks
- High level project requirements
- High level milestones view of project
- Summary level preliminary project budget
Waterfall Methodologies:
- Rely on a heavy up-front analysis and documentation of the need and problems along with proposed
resolutions