The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources
1/388
Project Management Process Group
A logical grouping of project management inputs, tools and techniques, and outputs. The Project Management Process Groups include Initiating processes, Planning processes, Executing processes, Monitoring and Controlling processes, and Closing processes
2/388
Planning Performance Domain
The performance domain that addresses activities and functions associated with the initial, ongoing, and evolving organization and coordination necessary for delivering project deliverables and results
3/388
S-Curve
A graph that displays cumulative costs over a specified period of time
4/388
Scatter Diagram
A graph that shows the relationship between two variables
5/388
Lead
The amount of time whereby a successor activity can be advanced with respect to a predecessor activity
6/388
Estimate to Complete (ETC)
The expected cost to finish all the remaining project work
7/388
Fixed Price Incentive Fee Contract (FPIF)
A type of contract where the buyer pays the seller a set amount (as defined by the contract), and the seller can earn an additional amount if the seller meets defined performance criteria
8/388
Project Lead
A person who helps the project team to achieve the project objectives, typically by orchestrating the work of the project
9/388
Product Management
The integration of people, data, processes, and business systems to create, maintain, and evolve a product or service throughout its life cycle.
10/388
Iterative Approach
A development approach that focuses on an initial, simplified implementation then progressively elaborates adding to the feature set until the final deliverable is complete
11/388
Artifact
A template, document, output, or project deliverable
12/388
Stakeholder Register
A project document that includes information about project stakeholders including an assessment and classification of project stakeholders
13/388
Backlog
An ordered list of work to be done
14/388
Variance at Completion (VAC)
A projection of the amount of budget deficit or surplus, expressed as the difference between the budget at completion and the estimate at completion
15/388
Assumption and Constraint Analysis
An assessment that ensures assumptions and constraints are integrated into the project plans and documents, and that there is consistency among them
16/388
Throughput Chart
A diagram that shows the accepted deliverables over time
17/388
Regression Analysis
An analytical method where a series of input variables are examined in relation to their corresponding output results in order to develop a mathematical or statistical relationship
18/388
Analogous Estimating
A method for estimating the duration or cost of an activity or a project using historical data from a similar activity or project
19/388
Objective
Something toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed
20/388
Flow
The measure of how efficiently work moves through a given process or framework
21/388
Development Approach
A method used to create and evolve the product, service, or result during the project life cycle such as an adaptive, predictive, or hybrid method.
22/388
Project Life Cycle
The series of phases that a project passes through from its start to its completion
23/388
Communications Management Plan
A component of the project, program, or portfolio management plan that describes how, when, and by whom information about the project will be administered and disseminated
24/388
Make-or-Buy Analysis
The process of gathering and organizing data about product requirements and analyzing them against available alternatives including the purchase or internal manufacture of the product
25/388
Fast Tracking
A schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. See also crashing and schedule compression.
26/388
Project Schedule
An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources
27/388
Visual Data and Information
Artifacts that organize and present data and information in a visual format, such as charts, graphs, matrices, and diagrams
28/388
Project Management Team
The members of the project team who are directly involved in project management activities
29/388
Retrospective
A regularly occurring workshop in which participants explore their work and results in order to improve both the process and product
30/388
Ambiguity
A state of being unclear, having difficulty in identifying the cause of events, or having multiple options from which to choose
31/388
Measures of Performance
Measures that characterize physical or functional attributes relating to system operation
32/388
Critical Path Method (CPM)
A method used to estimate the minimum project duration and determine the amount of schedule flexibility on the logical network paths within the schedule model
33/388
Business Value
The net quantifiable benefit derived from a business endeavor that may be tangible, intangible, or both
34/388
Change Control
A process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected
35/388
Prioritization Schema
Methods used to prioritize portfolio, program, or project components, as well as requirements, risks, features, or other product information
36/388
Self-Organizing Team
A cross-functional team in which people assume leadership as needed to achieve the team’s objectives
37/388
Digital Product
A product or service that is delivered, used, and stored in an electronic format
38/388
Role
A defined function to be performed by a project team member, such as testing, filing, inspecting, or coding.
39/388
Discretionary Dependency
A relationship that is based on best practices or project preferences
40/388
Schedule Compression
A method used to shorten the schedule duration without reducing the project scope
41/388
Waste
Activities that consume resources and/or time without adding value
42/388
Work Package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed
43/388
Budget
The approved estimate for the project or any work breakdown structure (WBS) component or any schedule activity
44/388
Scope Baseline
The approved version of formal scope documents that can be changed using formal change control procedures and is used as the basis for comparison to actual results. See also baseline, cost baseline, performance measurement baseline, and schedule baseline.
45/388
Timebox
A short, fixed period of time in which work is to be completed
46/388
Project Life Cycle
The series of phases that a project passes through from its start to its completion.
47/388
Development Approach
A method used to create and evolve the product, service, or result during the project life cycle, such as a predictive, iterative, incremental, agile, or hybrid method
48/388
Risk Review
The process of analyzing the status of existing risks and identifying new risks. May also be known as risk reassessment
49/388
Criteria
Standards, rules, or tests on which a judgment or decision can be based or by which a product, service, result, or process can be evaluated
50/388
Data Gathering and Analysis Methods
Methods used to collect, assess, and evaluate data and information to gain a deeper understanding of a situation
51/388
Risk Threshold
The measure of acceptable variation around an objective that reflects the risk appetite of the organization and stakeholders. See also risk appetite
52/388
Delivery Performance Domain
The performance domain that addresses activities and functions associated with delivering the scope and quality that the project was undertaken to achieve
53/388
Deliverable
Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project
54/388
Requirements Traceability Matrix
A grid that links product requirements from their origin to the deliverables that satisfy them
55/388
Project Manager
The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives. See also portfolio manager and program manager.
56/388
Quality Management Plan
A component of the project or program management plan that describes how applicable policies, procedures, and guidelines will be implemented to achieve the quality objectives
57/388
Definition of Done (DoD)
A checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use
58/388
Threat
A risk that would have a negative effect on one or more project objectives
59/388
Lead Time Chart
A diagram showing the trend over time of the average lead time of the items completed in work
60/388
Cost Plus Award Fee Contract (CPAF)
A category of contract that involves payments to the seller for all legitimate actual costs incurred for completed work, plus an award fee representing seller profit
61/388
Authority
The right to apply project resources, expend funds, make decisions, or give approvals
62/388
Histogram
A bar chart that shows the graphical representation of numerical data
63/388
Cumulative Flow Diagram (CFD)
A chart indicating features completed over time, features in other states of development, and those in the backlog
64/388
Issue
A current condition or situation that may have an impact on the project objectives
65/388
Crashing
A method used to shorten the schedule duration for the least incremental cost by adding resources
66/388
Lag
The amount of time whereby a successor activity will be delayed with respect to a predecessor activity
67/388
Flowchart
The depiction in a diagram format of the inputs, process actions, and outputs of one or more processes within a system
68/388
Epic
A large, related body of work intended to hierarchically organize a set of requirements and deliver specific business outcomes
69/388
Project Work Performance Domain
The performance domain that addresses activities and functions associated with establishing project processes, managing physical resources, and fostering a learning environment
70/388
Project Review
An event at the end of a phase or project to assess the status, evaluate the value delivered, and determine if the project is ready to move to the next phase or transition to operations
71/388
Schedule Model
A representation of the plan for executing the project’s activities including durations, dependencies, and other planning information, used to produce a project schedule along with other scheduling artifacts
72/388
Cause-and-Effect Diagram
A visual representation that helps trace an undesirable effect back to its root cause
73/388
Iteration Planning
A meeting to clarify the details of the backlog items, acceptance criteria, and work effort required to meet an upcoming iteration commitment
74/388
Lean Startup Canvas
A one-page template designed to communicate a business plan with key stakeholders in an efficient and effective manner
75/388
Roadmap
A high-level time line that depicts such things as milestones, significant events, reviews, and decision points
76/388
Tacit Knowledge
Personal knowledge that can be difficult to articulate and share such as beliefs, experience, and insights
77/388
Agile
A term used to describe a mindset of values and principles as set forth in the Agile Manifesto
78/388
Verification
The evaluation of whether or not a product, service, or result complies with a regulation, requirement, specification, or imposed condition. See also validation
79/388
Affinity Grouping
The process of classifying items into similar categories or collections on the basis of their likeness
80/388
Stakeholder Engagement Plan
A component of the program or project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in program or project decision-making and execution. See also project management plan.
81/388
Earned Value (EV)
The measure of work performed expressed in terms of the budget authorized for that work
82/388
Procurement Management Plan
A component of the project or program management plan that describes how a project team will acquire goods and services from outside of the performing organization
83/388
Project Team
A set of individuals performing the work of the project to achieve its objectives
84/388
Risk Escalation
A risk response strategy whereby the team acknowledges that a risk is outside of its sphere of influence and shifts the ownership of the risk to a higher level of the organization where it is more effectively managed
85/388
Risk Exploiting
A risk response strategy whereby the project team acts to ensure that an opportunity occurs
86/388
Internal Dependency
A relationship between two or more project activities
87/388
Bidder Conference
The meetings with prospective sellers prior to the preparation of a bid or proposal to ensure all prospective vendors have a clear and common understanding of the procurement. Also known as contractor conferences, vendor conferences, or pre-bid conferences
88/388
Wideband Delphi
An estimating method in which subject matter experts go through multiple rounds of producing estimates individually, with a team discussion after each round, until a consensus is achieved
89/388
Budget at Completion (BAC)
The sum of all budgets established for the work to be performed
90/388
Value Proposition
The value of a product or service that an organization communicates to its customers
91/388
Project Management Office (PMO)
A management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques
92/388
Stakeholder Analysis
A method of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project
93/388
Osmotic Communication
Means of receiving information without direct communication by overhearing and through nonverbal cues
94/388
Explicit Knowledge
Knowledge that can be codified using symbols such as words, numbers, and pictures
95/388
Estimating Methods
Methods used to develop an approximation of work, time, or cost on a project
96/388
Emotional Intelligence
The ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people
97/388
Minimum Viable Product (MVP)
A concept used to define the scope of the first release of a solution to customers by identifying the fewest number of features or requirements that would deliver value
98/388
Outcome
An end result or consequence of a process or project
99/388
Constraint
A limiting factor that affects the execution of a project, program, portfolio, or process
100/388
Release Plan
The plan that sets expectations for the dates, features, and/or outcomes expected to be delivered over the course of multiple iterations
101/388
Team Performance Domain
The performance domain that addresses activities and functions associated with the people who are responsible for producing project deliverables that realize business outcomes
102/388
Impact Mapping
A strategic planning method that serves as a visual roadmap for the organization during product development
103/388
Control
The process of comparing actual performance with planned performance, analyzing variances, assessing trends to effect process improvements, evaluating possible alternatives, and recommending appropriate corrective action as needed
104/388
Iteration Plan
A detailed plan for the current iteration
105/388
Value Stream Map
A display of the critical steps in a process and the time taken in each step used to identify waste
106/388
Project Management Plan
The document that describes how the project will be executed, monitored and controlled, and closed
107/388
Value Stream Mapping
A lean enterprise method used to document, analyze, and improve the flow of information or materials required to produce a product or service for a customer
108/388
Single-Point Estimating
An estimating method that involves using data to calculate a single value which reflects a best guess estimate
109/388
Change Control Board (CCB)
A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions
110/388
Sensitivity Analysis
An analysis method to determine which individual project risks or other sources of uncertainty have the most potential impact on project outcomes by correlating variations in project outcomes with variations in elements of a quantitative risk analysis model
111/388
Role
A defined function to be performed by a project team member, such as testing, filing, inspecting, or coding
112/388
Probabilistic Estimating
A method used to develop a range of estimates along with the associated probabilities within that range
113/388
Sponsor
A person or group who provides resources and support for the project, program, or portfolio and is accountable for enabling success
114/388
Volatility
The possibility for rapid and unpredictable change
115/388
Schedule Management Plan
A component of the project or program management plan that establishes the criteria and the activities for developing, monitoring, and controlling the schedule
116/388
Initiating Process Group
Those processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase
117/388
Methodology
A system of practices, techniques, procedures, and rules used by those who work in a discipline
118/388
Trend Analysis
An analytical method that uses mathematical models to forecast future outcomes based on historical results
119/388
Gantt Chart
A bar chart of schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates
120/388
What-If-Scenario Analysis
The process of evaluating scenarios in order to predict their effect on project objectives
121/388
Assumption
A factor in the planning process that is considered to be true, real, or certain, without proof or demonstration
122/388
Probability and Impact Matrix
A grid for mapping the probability of occurrence of each risk and its impact on project objectives if that risk occurs
123/388
Story Map
A visual model of all the features and functionality desired for a given product, created to give the team a holistic view of what they are building and why
124/388
Issue Log
A project document where information about issues is recorded and monitored
125/388
Actual Cost (AC)
The realized cost incurred for the work performed on an activity during a specific time period. See also budget at completion (BAC), earned value (EV), estimate at completion (EAC), estimate to complete (ETC), and planned value (PV).
126/388
Stakeholder Engagement Assessment Matrix
A matrix that compares current and desired stakeholder engagement levels
127/388
Rework
Action taken to bring a defective or nonconforming component into compliance with requirements or specifications
128/388
Metric
A description of a project or product attribute and how to measure it
129/388
Blocker
An obstacle that prevents the team from achieving its objectives. Also known as an impediment
130/388
Reserve Analysis
A method used to evaluate the amount of risk on the project and the amount of schedule and budget reserve to determine whether the reserve is sufficient for the remaining risk
131/388
Incremental Approach
An adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete.
132/388
Lead Time
The time between a customer request and the actual delivery
133/388
Risk
An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives
134/388
Change Control System
A set of procedures that describes how modifications to the project deliverables and documentation are managed and controlled. See also change control and change control board (CCB).
135/388
Project Schedule Network Diagram
A graphical representation of the logical relationships among the project schedule activities
136/388
Virtual Team
A group of people with a shared goal who work in different locations and who engage with each other primarily through phone and other electronic communications
137/388
Monitor
Collect project performance data, produce performance measures, and report and disseminate performance information
138/388
Rolling Wave Planning
An iterative planning method in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level
139/388
Throughput
The number of items passing through a process
140/388
Project Management Body of Knowledge (PMBOK)
A term that describes the knowledge within the profession of project management
141/388
Requirement
A condition or capability that is necessary to be present in a product, service, or result to satisfy a business need
142/388
Standard
A document established by an authority, custom, or general consent as a model or example
143/388
Kanban Board
A visualization tool that shows work in progress to help identify bottlenecks and overcommitments, thereby allowing the team to optimize the workflow.
144/388
Precision
Within the quality management system, precision is an assessment of exactness
145/388
Measurement Performance Domain
The performance domain that addresses activities and functions associated with assessing project performance and taking appropriate actions to maintain acceptable performance
146/388
Root Cause Analysis
An analytical method used to determine the basic underlying reason that causes a variance or a defect or a risk
147/388
Progressive Elaboration
The iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available
148/388
Risk Appetite
The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward
149/388
Planning Process Group
Those processes required to establish the scope of the project, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve
150/388
Uncertainty
A lack of understanding and awareness of issues, events, path to follow, or solutions to pursue
151/388
Risk Mitigation
A risk response strategy whereby the project team acts to decrease the probability of occurrence or impact of a threat
152/388
Throughput Chart
A diagram that shows the accepted deliverables over time
153/388
Stakeholder Register
A project document that includes information about project stakeholders including an assessment and classification of project stakeholders.
154/388
Change
A modification to any formally controlled deliverable, project management plan component, or project document
155/388
Stakeholder
An individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio
156/388
Schedule Forecasts
Estimates or predictions of conditions and events in the project’s future based on information and knowledge available at the time the schedule is calculated
157/388
Portfolio Management
The centralized management of one or more portfolios to achieve strategic objectives
158/388
Baseline
The approved version of a work product, used as a basis for comparison to actual results
159/388
Resource Management Plan
A component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled
160/388
Project
A temporary endeavor undertaken to create a unique product, service, or result
161/388
Lessons Learned Register
A project document used to record knowledge gained during a project, phase, or iteration so that it can be used to improve future performance for the team and the organization
162/388
Steering Committee
An advisory body of senior stakeholders who provide direction and support for the portfolio, program, or project team and make decisions outside of the team’s authority.
163/388
Planned Value (PV)
The authorized budget assigned to scheduled work
164/388
Standard
A document established by an authority, custom, or general consent as a model or example.
165/388
Milestone
A significant point or event in a portfolio, program, or project.
166/388
Risk Avoidance
A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact
167/388
Grade
A category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality
168/388
Story Point
A unit used to estimate the relative level of effort needed to implement a user story
169/388
Tolerance
The quantified description of acceptable variation for a quality requirement
170/388
Strategic Plan
A high-level document that explains an organization’s vision and mission plus the approach that will be adopted to achieve this mission and vision, including the specific goals and objectives to be achieved during the period covered by the document
171/388
Duration
The total number of work periods required to complete an activity or work breakdown structure component, expressed in hours, days, or weeks. Contrast with effort
172/388
Project Scope
The work performed to deliver a product, service, or result with the specified features and functions
173/388
Risk Acceptance
A risk response strategy whereby the project team decides to acknowledge the risk and not take any action unless the risk occurs
174/388
Estimate at Completion (EAC)
The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete
175/388
External Dependency
A relationship between project activities and non-project activities
176/388
Retrospective
A regularly occurring workshop in which participants explore their work and results in order to improve both the process and product.
177/388
Cost Baseline
The approved version of the time-phased project budget, excluding any management reserves, which can be changed only through formal change control procedures and is used as a basis for comparison to actual results
178/388
Confirmation Bias
A type of cognitive bias that confirms preexisting beliefs or hypotheses
179/388
Velocity Chart
A chart that tracks the rate at which the deliverables are produced, validated, and accepted within a predefined interval
180/388
Iteration
A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is performed
181/388
Influence Diagram
A graphical representation of situations showing causal influences, time ordering of events, and other relationships among variables and outcomes
182/388
Enterprise Environmental Factors (EEF)
Conditions, not under the immediate control of the team, that influence, constrain, or direct the project, program, or portfolio
183/388
Change Control Plan
A component of the project management plan that establishes the change control board, documents the extent of its authority, and describes how the change control system will be implemented
184/388
Report
A formal record or summary of information
185/388
Schedule Performance Index (SPI)
A measure of schedule efficiency expressed as the ratio of earned value to planned value
186/388
Milestone Schedule
A type of schedule that presents milestones with planned dates
187/388
Life Cycle Assessment (LCA)
A tool used to evaluate the total environmental impact of a product, process, or system
188/388
Portfolio
Projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives
189/388
Cycle Time
The total elapsed time from the start of a particular activity or work item to its completion
190/388
Impediment
An obstacle that prevents the team from achieving its objectives. Also known as a blocker
191/388
Alternatives Analysis
A method used to evaluate identified options in order to select the options or approaches to use to perform the work of the project
192/388
WBS Dictionary
A document that provides detailed deliverable, activity, and scheduling information about each component in the work breakdown structure
193/388
Value Delivery Office (VDO)
A project delivery support structure that focuses on coaching teams; building agile skills and capabilities throughout the organization; and mentoring sponsors and product owners to be more effective in those roles
194/388
Backlog Refinement
Progressive elaboration of the content in the backlog and (re)prioritization of it to identify the work that can be accomplished in an upcoming iteration
195/388
Assumption Log
A project document used to record all assumptions and constraints throughout the project.
196/388
Plan
A proposed means of accomplishing something
197/388
Status Report
A report on the current status of the project
198/388
Net Promoter Score®
An index that measures the willingness of customers to recommend an organization’s products or services to others
199/388
Change Management
A comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from a current state to a future state with intended business benefits
200/388
Function Point
An estimate of the amount of business functionality in an information system, used to calculate the functional size measurement of a software system
201/388
Team Charter
A document that records the team values, agreements, and operating guidelines, as well as establishes clear expectations regarding acceptable behavior by project team members
202/388
Prototype
A working model used to obtain early feedback on the expected product before actually building it
203/388
Work Breakdown Structure (WBS)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables
204/388
Cadence
A rhythm of activities conducted throughout the project
205/388
Acceptance Criteria
A set of conditions that is required to be met before deliverables are accepted
206/388
Development Approach and Life Cycle Performance Domain
The performance domain that addresses activities and functions associated with the development approach, cadence, and life cycle phases of the project
207/388
Change Log
A comprehensive list of changes submitted during the project and their current status
208/388
Organizational Breakdown Structure (OBS)
A hierarchical representation of the project organization, which illustrates the relationship between project activities and the organizational units that will perform those activities
209/388
Technical Performance Measures
Quantifiable measures of technical performance that are used to ensure system components meet the technical requirements
210/388
Triple Bottom Line
A framework for considering the full cost of doing business by evaluating a company’s bottom line from the perspective of profit, people, and the planet
211/388
Activity List
A documented tabulation of schedule activities that shows the activity description, activity identifier, and a sufficiently detailed scope of work description so project team members understand what work is to be performed
212/388
Complexity
A characteristic of a program or project or its environment that is difficult to manage due to human behavior, system behavior, and ambiguity
213/388
Organizational Breakdown Structure (OBS)
A hierarchical representation of the project organization that illustrates the relationship between project activities and the organizational units that will perform those activities. See also resource breakdown structure, risk breakdown structure, and work breakdown structure (WBS).
214/388
Burn Chart
A graphical representation of the work remaining in a timebox or the work completed toward the release of a product or project deliverable
215/388
Risk Report
A project document that summarizes information on individual project risks and the level of overall project risk
216/388
Time and Materials Contract (T&M)
A type of contract that is a hybrid contractual arrangement containing aspects of both cost-reimbursable and fixed-price contracts
217/388
Result
An output from performing project management processes and activities. See also deliverable
218/388
Rework
Action taken to bring a defective or nonconforming component into compliance with requirements or specifications.
219/388
Program
Related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually
220/388
Scope Baseline
The approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary that can be changed using formal change control procedures and is used as the basis for comparison to actual results
221/388
Validation
The assurance that a product, service, or result meets the needs of the customer and other identified stakeholders. See also verification
222/388
Risk Sharing
A risk response strategy whereby the project team allocates ownership of an opportunity to a third party who is best able to capture the benefit of that opportunity
223/388
Strategy Artifacts
Documents created prior to or at the start of the project that address strategic, business, or high-level information about the project
224/388
Program Management
The application of knowledge, skills, and principles to a program to achieve the program objectives and obtain benefits and control not available by managing program components individually
225/388
Project Phase
A collection of logically related project activities that culminates in the completion of one or more deliverables. See also phase gate.
226/388
Swarm
A method in which multiple team members focus collectively on resolving a specific problem or task
227/388
Contingency
An event or occurrence that could affect the execution of the project, which may be accounted for with a reserve
228/388
Vision Statement
A summarized, high-level description about the expectations for a product such as target market, users, major benefits, and what differentiates the product from others in the market
229/388
Cost Variance (CV)
The amount of budget deficit or surplus at a given point in time, expressed as the difference between the earned value and the actual cost
230/388
Task Board
A visual representation of the progress of the planned work that allows everyone to see the status of the tasks
231/388
Fixed Duration
A type of activity where the length of time required to complete the activity remains constant regardless of the number of people or resources assigned to the activity.
232/388
Tailoring
The deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand
233/388
Method
A means for achieving an outcome, output, result, or project deliverable
234/388
Project Management
The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements
235/388
Closing Process Group
The process(es) performed to formally complete or close a project, phase, or contract
236/388
Last Responsible Moment
The concept of deferring a decision to allow the team to consider multiple options until the cost of further delay would exceed the benefit
237/388
Release Planning
The process of identifying a high-level plan for releasing or transitioning a product, deliverable, or increment of value
238/388
Life Cycle
The series of phases that a project passes through from its start to its completion. Also known as Project Life Cycle.
239/388
Responsibility
An assignment that can be delegated within a project management plan such that the assigned resource incurs a duty to perform the requirements of the assignment
240/388
Business Case
A value proposition for a proposed project that may include financial and nonfinancial benefits
241/388
Predictive Approach
A development approach in which the project scope, time, and cost are determined in the early phases of the life cycle
242/388
Project Charter
A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
243/388
Variance Analysis
A method for determining the cause and degree of difference between the baseline and actual performance
244/388
Product Breakdown Structure
A hierarchical structure reflecting a product’s components and deliverables
245/388
Schedule Variance (SV)
A measure of schedule performance expressed as the difference between the earned value and the planned value
246/388
DevOps
A collection of practices for creating a smooth flow of deliveries by improving collaboration between development and operations staff
247/388
Product Scope
The features and functions that characterize a product, service, or result
248/388
Cycle Time Chart
A diagram that shows the average cycle time of the work items completed over time
249/388
Opportunity
A risk that would have a positive effect on one or more project objectives
250/388
Earned Value Analysis (EVA)
An analysis method that uses a set of measures associated with scope, schedule, and cost to determine the cost and schedule performance of a project
251/388
Benchmarking
The comparison of actual or planned products, processes, and practices to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance
252/388
Register
A written record of regular entries for evolving aspects of a project, such as risks, stakeholders, or defects
253/388
Charter
A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. Also known as a project charter
254/388
Risk Transference
A risk response strategy whereby the project team shifts the impact of a threat to a third party, together with ownership of the response
255/388
Life Cycle
The series of phases that a project passes through from its start to its completion. Also known as project life cycle
256/388
Lessons Learned Register
A project document or repository used to record knowledge gained during a project, phase, or iteration so that it can be used to improve future performance for the team and the organization.
257/388
Firm Fixed Price Contract (FFP)
A type of fixed-price contract where the buyer pays the seller a set amount (as defined by the contract), regardless of the seller’s costs
258/388
Risk Register
A repository in which outputs of risk management processes are recorded
259/388
Project Brief
A high-level overview of the goals, deliverables, and processes for the project
260/388
Resource Management Plan
A component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled. See also project management plan.
261/388
Adaptive Approach
A development approach in which the requirements are subject to a high level of uncertainty and volatility and are likely to change throughout the project
262/388
Release Plan
The plan that sets expectations for the dates, features, and/or outcomes expected to be delivered over the course of multiple iterations. See also project management plan.
263/388
Quality Report
A project document that includes quality management issues, recommendations for corrective actions, and a summary of findings from quality control activities and may include recommendations for process, project, and product improvements
264/388
Kickoff Meeting
A gathering of team members and other key stakeholders at the outset of a project to formally set expectations, gain a common understanding, and commence work
265/388
Velocity
A measure of a team’s productivity rate at which the deliverables are produced, validated, and accepted within a predefined interval
266/388
Management Reserve
An amount of the project budget or project schedule held outside of the performance measurement baseline for management control purposes that is reserved for unforeseen work that is within the project scope
267/388
Responsibility Assignment Matrix (RAM)
A grid that shows the project resources assigned to each work package
268/388
Executing Process Group
Those processes performed to complete the work defined in the project management plan to satisfy the project requirements
269/388
Lean Startup Canvas
A one-page template designed to communicate a business plan with key stakeholders in an efficient and effective manner
270/388
Vanity Metric
A measure that appears to show some result but does not provide useful information for making decisions
271/388
Cost Management Plan
A component of a project or program management plan that describes how costs will be planned, structured, and controlled
272/388
Indefinite Delivery Indefinite Quantity (IDIQ)
A contract that provides for an indefinite quantity of goods or services, with a stated lower and upper limit, within a fixed time period
273/388
Project Phase
A collection of logically related project activities that culminates in the completion of one or more deliverables
274/388
Stakeholder Performance Domain
The performance domain that addresses activities and functions associated with stakeholders
275/388
Schedule
An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources. Also known as project schedule
276/388
Cost Variance (CV)
The amount of budget deficit or surplus at a given point in time, expressed as the difference between the earned value and the actual cost. See also schedule variance (SV).
277/388
Requirements Management Plan
A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed
278/388
Affinity Diagram
A diagram that shows large numbers of ideas classified into groups for review and analysis
279/388
Quality
The degree to which a set of inherent characteristics fulfills requirements
280/388
Modeling
Creating simplified representations of systems, solutions, or deliverables, such as prototypes, diagrams, or storyboards
281/388
Variance
A quantifiable deviation, departure, or divergence away from a known baseline or expected value
282/388
Monitoring and Controlling Process Group
Those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate corresponding changes
283/388
Project Governance
The framework, functions, and processes that guide project management activities in order to meet or exceed target project objectives.
284/388
Hierarchy Chart
A chart that begins with high-level information that is progressively decomposed into lower levels of detail
285/388
Mandatory Dependency
A relationship that is contractually required or inherent in the nature of the work
286/388
Reserve
A provision in the project management plan to mitigate cost and/or schedule risk, often used with a modifier (e.g. management reserve, contingency reserve) to provide further detail on what types of risk are meant to be mitigated)
287/388
Milestone
A significant point or event in a project, program, or portfolio
288/388
Governance
The framework for directing and enabling an organization through its established policies, practices, and other relevant documentation
289/388
Iteration Review
A meeting held at the end of an iteration to demonstrate the work that was accomplished during the iteration
290/388
Effort
The number of labor units required to complete a schedule activity or work breakdown structure component, often expressed in hours, days, or weeks. Contrast with duration
291/388
SWOT Analysis
Analysis of strengths, weaknesses, opportunities, and threats of an organization, project, or option
292/388
Expected Monetary Value (EMV)
The estimated value of an outcome expressed in monetary terms
293/388
Performance Measurement Baseline (PMB)
Integrated scope, schedule, and cost baselines used for comparison to manage, measure, and control project execution
294/388
Quality Policy
The basic principles that should govern the organization’s actions as it implements its system for quality management
295/388
Cost-Benefit Analysis
A financial analysis method used to determine the benefits provided by a project against its costs
296/388
Resource Breakdown Structure
A hierarchical representation of resources by category and type
297/388
Uncertainty Domain
The performance domain that addresses activities and functions associated with risk and uncertainty
298/388
Product Management
The integration of people, data, processes, and business systems to create, maintain, and evolve a product or service throughout its life cycle
299/388
Prioritization Matrix
A scatter diagram that plots effort against value so as to classify items by priority
300/388
Requirements Documentation
A record of product requirements and other product information, along with whatever is recorded to manage it
301/388
Cost Plus Fixed Fee Contract (CPFF)
A type of cost-reimbursable contract where the buyer reimburses the seller for the seller’s allowable costs (allowable costs are defined by the contract) plus a fixed amount of profit (fee)
302/388
Information Radiator
A visible, physical display that provides information to the rest of the organization, enabling timely knowledge sharing
303/388
Stakeholder Engagement Plan
A component of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project or program decision making and execution
304/388
Contingency Reserve
Time or money allocated in the schedule or cost baseline for known risks with active response strategies
305/388
Knowledge
A mixture of experience, values and beliefs, contextual information, intuition, and insight that people use to make sense of new experiences and information
306/388
Regulations
Requirements imposed by a governmental body. These requirements can establish product, process, or service characteristics, including applicable administrative provisions that have government-mandated compliance.
307/388
Cost Performance Index (CPI)
A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost
308/388
Continuous Delivery
The practice of delivering feature increments immediately to customers, often through the use of small batches of work and automation technology
309/388
Parametric Estimating
An estimating method in which an algorithm is used to calculate cost or duration based on historical data and project parameters
310/388
Dashboard
A set of charts and graphs showing progress or performance against important measures of the project
311/388
Risk Enhancement
A risk response strategy whereby the project team acts to increase the probability of occurrence or impact of an opportunity
312/388
Phase Gate
A review at the end of a phase in which a decision is made to continue to the next phase, to continue with modification, or to end a project or program
313/388
Risk Review
A meeting to examine and document the effectiveness of risk responses in dealing with overall project risk and with identified individual project risks.
314/388
Network Path
A sequence of activities connected by logical relationships in a project schedule network diagram
315/388
Lessons Learned
The knowledge gained during a project, which shows how project events were addressed or should be addressed in the future, for the purpose of improving future performance
316/388
Schedule Baseline
The approved version of a schedule model that can be changed using formal change control procedures and is used as the basis for comparison to actual results
317/388
Product Owner
A person responsible for maximizing the value of the product and accountable for the end product
318/388
Voice of the Customer
A planning method used to provide products, services, and results that truly reflect customer requirements by translating those customer requirements into the appropriate technical requirements for each phase of project or product development
319/388
Contract
A mutually binding agreement that obligates the seller to provide the specified product, service, or result and obligates the buyer to pay for it
320/388
Critical Path
The sequence of activities that represents the longest path through a project, which determines the shortest possible duration
321/388
Fixed Price with Economic Price Adjustment Contract (FPEPA)
A fixed-price contract, but with a special provision allowing for predefined final adjustments to the contract price due to changed conditions, such as inflation changes, or cost increases (or decreases) for specific commodities
322/388
Bid Documents
All documents used to solicit information, quotations, or proposals from prospective sellers
323/388
Fixed-Price Contract
An agreement that sets the fee that will be paid for a defined scope of work regardless of the cost or effort to deliver it
324/388
Project Scope Statement
The description of the project scope, major deliverables, and exclusions
325/388
Monte Carlo Simulation
A method of identifying the potential impacts of risk and uncertainty using multiple iterations of a computer model to develop a probability distribution of a range of outcomes that could result from a decision or course of action
326/388
Project Charter
A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
327/388
Relative Estimating
A method for creating estimates that are derived from performing a comparison against a similar body of work, taking effort, complexity, and uncertainty into consideration
328/388
Simulation
An analytical method that models the combined effect of uncertainties to evaluate their potential impact on objectives
329/388
Interpersonal Skills
Skills used to establish and maintain relationships with other people
330/388
Hybrid Approach
A combination of two or more agile and nonagile elements, having a nonagile end result
331/388
Release
One or more components of one or more products, which are intended to be put into production at the same time
332/388
Cost Plus Incentive Fee Contract (CPIF)
A type of cost-reimbursable contract where the buyer reimburses the seller for the seller’s allowable costs (allowable costs are defined by the contract), and the seller earns its profit if it meets defined performance criteria
333/388
Project Vision Statement
A concise, high-level description of the project that states the purpose and inspires the team to contribute to the project
334/388
Conformance
The degree to which the results meet the set quality requirements
335/388
Status Meeting
A regularly scheduled meeting to exchange and analyze information about the current progress of the project and its performance
336/388
Benefits Management Plan
The documented explanation defining the processes for creating, maximizing, and sustaining the benefits provided by a project or program
337/388
User Story
A brief description of an outcome for a specific user, which is a promise for a conversation to clarify details
338/388
Project Governance
The framework, functions, and processes that guide project management activities in order to create a unique product, service, or result to meet organizational, strategic, and operational goals
339/388
Daily Standup
A brief, daily collaboration meeting in which the team reviews progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated
340/388
Kanban Board
A visualization tool that shows work in progress to help identify bottlenecks and overcommitments, thereby allowing the team to optimize the workflow
341/388
Steering Committee
An advisory body of senior stakeholders who provide direction and support for the project team and make decisions outside the project team’s authority
342/388
Threat
A risk that would have a negative effect on one or more portfolio, program, or project objectives. See also issue, opportunity, and risk.
343/388
Mood Chart
A visualization chart for tracking moods or reactions to identify areas for improvement
344/388
Estimate
A quantitative assessment of the likely amount or outcome of a variable, such as project costs, resources, effort, or durations
345/388
Servant Leadership
The practice of leading the team by focusing on understanding and addressing the needs and development of team members in order to enable the highest possible team performance
346/388
Risk Breakdown Structure (RBS)
A hierarchical representation of potential sources of risks
347/388
Log
A document used to record and describe or denote selected items identified during execution of a process or activity. Usually used with a modifier, such as issue, change, or assumption
348/388
Product
An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item
349/388
Cost of Quality (COQ)
All costs incurred over the life of the product by investment in preventing nonconformance to requirements, appraisal of the product or service for conformance to requirements, and failure to meet requirements.
350/388
Project Calendar
A calendar that identifies working days and shifts that are available for scheduled activities
351/388
Check Sheet
A tally sheet that can be used as a checklist when gathering data
352/388
Risk Management Plan
A component of the project, program, or portfolio management plan that describes how risk management activities will be structured and performed
353/388
Quality Metrics
A description of a project or product attribute and how to measure it
354/388
Feature
A set of related requirements or functionalities that provides value to an organization
355/388
Multipoint Estimating
A method used to estimate cost or duration by applying an average or weighted average of optimistic, pessimistic, and most likely estimates when there is uncertainty with the individual activity estimates
356/388
Business Model Canvas
A one-page, visual summary that describes the value proposition, infrastructure, customers, and finances. These are often used in Lean Startup situations
357/388
Use Case
An artifact for describing and exploring how a user interacts with a system to achieve a specific goal
358/388
Risk-Adjusted Backlog
A backlog that includes product work and actions to address threats and opportunities
359/388
Scope
The sum of the products, services, and results to be provided as a project. See also project scope and product scope
360/388
Test Plan
A document describing deliverables that will be tested, tests that will be conducted, and the processes that will be used in testing
361/388
Value
The worth, importance, or usefulness of something
362/388
Value Delivery System
A collection of strategic business activities aimed at building, sustaining, and/or advancing an organization
363/388
Statement of Work (SOW)
A narrative description of products, services, or results to be delivered by the project
364/388
Project Manager
The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives. See also project lead
365/388
Responsibility Assignment Matrix (RAM)
A grid that shows the project resources assigned to each work package.
366/388
Cost-Reimbursable Contract
A type of contract involving payment to the seller for the seller’s actual costs, plus a fee typically representing the seller’s profit.
367/388
Specification
A precise statement of the needs to be satisfied and the essential characteristics that are required
368/388
Regulations
Requirements imposed by a governmental body. These requirements can establish product, process, or service characteristics, including applicable administrative provisions that have government-mandated compliance
369/388
Scope Management Plan
A component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated
370/388
Variance Analysis
A technique for determining the cause and degree of difference between the baseline and actual performance. See also cost variance (CV), schedule variance (SV), and variance at completion (VAC).
371/388
Risk Exposure
An aggregate measure of the potential impact of all risks at any given point in time in a project, program, or portfolio
372/388
Sprint
A short time interval within a project during which a usable and potentially releasable increment of the product is created. See also iteration
373/388
Product Life Cycle
A series of phases that represent the evolution of a product, from concept through delivery, growth, maturity, and to retirement
374/388
Threshold
A predetermined value of a measurable project variable that represents a limit that requires action to be taken if it is reached
375/388
Basis of Estimates
Supporting documentation outlining the details used in establishing project estimates such as assumptions, constraints, level of detail, ranges, and confidence levels.
376/388
Accuracy
Within the quality management system, it is an assessment of correctness
377/388
Change Request
A formal proposal to modify a document, deliverable, or baseline
378/388
Decomposition
A method used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts
379/388
Value Delivery System
A collection of strategic business activities aimed at building, sustaining, and/or advancing an organization.
380/388
Rolling Wave Planning
An iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. See also progressive elaboration.
381/388
Forecast
An estimate or prediction of conditions and events in the project’s future based on information and knowledge available at the time of the forecast.
382/388
Incremental Approach
An adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete
383/388
Precision
Within the quality management system, precision is an assessment of exactness.
384/388
Template
A partially complete document in a predefined format that provides a defined structure for collecting, organizing, and presenting information and data
385/388
Organizational Process Assets (OPA)
Plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization
386/388
Control Chart
A graphic display of process data over time and against established control limits, which has a centerline that assists in detecting a trend of plotted values toward either control limit
387/388
Decision Tree Analysis
A diagramming and calculation method for evaluating the implications of a chain of multiple options in the presence of uncertainty
388/388
Practice these Flashcards to get confidence for PMP Exam related Terms