PMP Terms Flashcards
(354 cards)
1
Q
80/20 Rule
A
A general guideline with many applications; in terms of controlling processes, it contends that a relatively large number of problems or defects, typically 80%, are commonly due to a relatively small number of causes, typically 20%.
2
Q
AB Testing
A
A marketing approach used to determine user preferences by showing different sets of users similar services with one independent variable
3
Q
AC (Actual Cost)
A
The realized cost incurred for the work performed on an activity during a specific time period.
4
Q
Accept
A
A strategy for managing negative risks or opportunities that involves acknowledging a risk and not taking any action until the risk occurs
5
Q
Acceptance Criteria
A
A set of conditions that is required to be met before deliverables are accepted.
6
Q
Active Listening
A
A communication technique that involves acknowledging what you hear, and clarifying the message to confirm that what you heard matches the message that the sender intended.
7
Q
Activity Attributes
A
Multiple attributes associated with each schedule activity that can be included within the activity list.
8
Q
Activity Dependency
A
A logical relationship that exists between two project activities. The relationship indicates whether the start of an activity is contingent upon an event or input from outside the activity.
9
Q
Activity Duration Estimates
A
The quantitative assessments of the likely number of time periods that are required to complete an activity.
10
Q
Activity List
A
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.
11
Q
Activity
A
A distinct, scheduled portion of work performed during the course of a project.
12
Q
Administrative Closure
A
Involves verifying and documenting project results to formalize project or phase completion.
13
Q
Affinity Diagram
A
A technique that allows large numbers of ideas to be classified into groups for review and analysis.
14
Q
Agile Life Cycles
A
A project life cycle that is iterative or incremental. Also referred to as change-driven or adaptive, they work well in environments with high levels of change and ongoing stakeholder involvement in a project.
15
Q
Agile Project Management
A
A project management methodology that uses an iterative and incremental approach that focuses on customer value and team empowerment. In agile project management, the product is developed in iterations by small and integrated teams.
16
Q
Agile Release Planning
A
A process in which you determine the number of iterations or Sprints that are needed to complete each release, the features that each iteration will contain, and the target dates of each release.
17
Q
Agreements
A
Any documents or communication that defines the initial intentions of a project. Examples include contracts, memorandums of understanding (MOUs), Service level agreements (SLAs), letters of agreement, letters of intent, verbal agreements, email, or other written agreements.
18
Q
Analogous Estimating
A
A technique for estimating the duration or cost of an activity on a project using historical data from a similar activity or project.
19
Q
Approved Change Requests
A
Change requests that have been reviewed and approved by the change control board (CCB) and are ready to be scheduled for implementation.
20
Q
Assumption and Constraint Analysis
A
A process that explores the validity of the project assumptions within the constraints and identifies risks from any incompleteness or inaccuracy of these project assumptions.
21
Q
Attribute Sampling Data
A
Data that is counted such as the number of product defects or customer complaints.
22
Q
Auditing
A
An examination of a project’s goals and achievements, including adequacy, accuracy, efficiency, effectiveness, and the project’s compliance with applicable methodologies and regulations, It tends to be a formal, one-sided process that can be extremely demoralizing to team members.
23
Q
Autocratic
A
Using this group decision-making method, one member of the group makes the decision. In most cases, this person will consider the larger group’s ideas and decisions, and will then make a decision based on that input.
24
Q
Avoid
A
A strategy for managing negative risks or threats that involves changing the project management plan to remove the risk entirely by extending the schedule, changing the strategy, increasing the funding. or reducing the scope.
25
BAC (Budget at Completion)
The sum of all budgets established for the work to be performed. BAC = Total Project PV
26
Bar Chart
A graphic display of schedule-related information. In the typical bar chart, schedule activities or WBS components are listed down the left side of the chart, dates are shown across the top, and activity durations are shown as date-place horizontal bars. (See Gantt chart).
27
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.
28
Benefit Cost Analysis
A financial analysis tool used to determine the benefits provided by a project against its costs.
29
Benefits Management Plan
The documented explanation defining the processes for creating, maximizing, and sustaining the benefits provided by a project or program.
30
Bidder Conferences
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 called vendor conferences, pre-bid conferences, or contractor conferences.
31
Bottom-up Estimating
A method of estimating project duration or cost by aggregating the estimates of the lower-level component of the WBS.
32
Brainstorming
A technique that involves a facilitator to help a group identify project risks in a free-form session where ideas are generated, built on, and recorded.
33
Breach of Contract
The failure to meet some or all of the obligations of a contract.
34
Burndown Chart
A tool that is used to track the progress of the project by plotting the number of days of Sprint against the number of hours of work remaining.
35
Business Case
A documented economic feasibility study used to establish the validity of the benefits of a selected component lacking sufficient definition and that is used as a basis for the authorization of further project management activities.
36
Business Risk
The inherent risk in any business endeavor that carries the potential for either profit or loss. Types of business risks are competitive, legislative, monetary, and operational.
37
Business Value
The net quantifiable benefit derived from a business endeavor. The benefit may be tangible, intangible, or both.
38
CCB (Change Control Board)
A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decision.
39
Cease and Desist Letter
A document sent to an individual or a business to stop (cease) allegedly illegal activities and to not undertake them again (desist).
40
Change Control Form
A document used to request a project change. They can also be recommendations for taking corrective or preventive actions. See also "change request"
41
Change Control System
A set of procedures that describes how modifications to the project deliverables and documentation are managed and controlled.
42
Change Management
The process of managing project changes in a structured and standardized manner.
43
Change Management Plan
A component of the project management plan that establishes the Change Control Board, documents that extent of its authority, and describes how the change control system will be implemented.
44
Change Request
Request for change sent to the upper management or the Change Control Board (CCB) for its evaluation and approval. See also "change control form."
45
Checklist Analysis
A technique for systematically reviewing materials using a list for accuracy and completeness.
46
CI (Continuous Improvement)
The ongoing effort to improve products, services, or processes.
47
Close Project or Phase Process
The process of finalizing all activities for the project, phase, or contract.
48
Close-out Meetings
Sessions held at the and of a project of phase; they involve discussing the work and capturing lessons learned.
49
Co-Location
An organizational placement strategy where the project team members are physically located close to one another in order to improve communication, working relationships, and productivity.
50
Coaching
The act of giving guidance and direction to another person so that he of she can make better decisions.
51
Code of Accounts
A numbering system used to uniquely identify each component of the WBS.
52
Code of Ethics and Professional Conduct
A PMI publication that describes the ethical and professional behavior expectations of any individual working as a project management professional.
53
Communication Methods
A systematic procedure, technique, or process used to transfer information among project stakeholders.
54
Communication Models
A description, analogy, or schematic used to represent how the communication process will be performed for the project.
55
Communication Requirements Analysis
An analytical technique to determine the information needs of the project stakeholders through interviews, workshops, study of lessons learned from previous projects, etc.
56
Communication Styles Assessment
A technique to identify the preferred communication method, format, and content for stakeholders for planned communication activities.
57
Communication Technology
Specific tools, systems, computer programs, etc., used to transfer information among project stakeholders.
58
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.
59
Completion Contract
A type of contract that is completed when the vendor delivers the product to the buyer and the buyer accepts the product.
60
Configuration Management
A tool used to manage changes to a product or service being produced as well as changes to any of the project documents such as schedule updates.
61
Configuration Management Plan
A component of the project management plan that describes how to identify and account for project artifacts under configuration control, and how to record and report changes to them.
62
Conflict Managment
The application of one or more strategies for dealing with disagreements that may be detrimental to team performance.
63
Context Diagram
A visual depiction of the product scope showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it.
64
Contingency Plan
A risk response strategy developed in advance, before risks occur; it is meant to be used if and when identified risks become reality.
65
Contingency Reserves
Time or money allocated in the schedule or cost baseline for known risks with active response strategies.
66
Contract Change Control System
The system used to collect, track, adjudicate, and communicate changes to a contract.
67
Contract
A mutually binding agreement that obligates the seller to provide the specified project or service or result and obligates the buyer to pay for it.
68
Control Account
A management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement.
69
Control Procurements Process
The process of managing procurement relationships, monitoring contract performance, making changes and corrections as appropriate, and closing out contracts.
70
Controlling PMO
A type of PMO that provides support and requires compliance through various means. Compliance may involve adopting project management frameworks or methodologies; using specific templates, forms, and tools; or conformance to governance.
71
CoQ (Cost of Quality)
All costs incurred over the life of the product by investment in preventing nonconformance to requirements, appraisal or the product or service for conformance to requirements, and failure to meet requirements.
72
Cost Aggregation
Summing the lower-level cost estimates associated with the various work packages for a given level within the project's WBS or for a given cost control account.
73
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.
74
Cost Management Plan
A component of a project or program management plan that describes how costs will be planned, structured, and controlled.
75
Cost of Conformance
The money spent during a project to avoid failures. This includes prevention costs that build a quality product and appraisal costs that assess the quality.
76
Cost of Non-Conformance
The money spent after a project is complete because of failures. This includes internal and external failure costs.
77
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.
78
CPAF Contract (Cost Plus Award Fee Contract)
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. (Type of Cost-Reimbursable contract)
79
CPFF Contract (Cost Plus Fixed Fee Contract)
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). (Type of Cost-Reimbursable contract)
80
CPI (Cost Performance Index)
A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost. (CPI = EV/AC)
CPI greater than 1.0 indicates project under budget
CPI = 1.0 means project is on budget
CPI under 1.0 indicates project is over budget
81
CPIF Contract (Cost Plus Incentive Fee Contract)
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. (Type of Cost-Reimbursable Contract)
82
Critical Path Activity
Any activity on the critical path in a project schedule.
83
Critical Path
The sequence of activities that represents the longest path through a project, which determines the shortest possible duration.
84
Cultural Awareness
Understanding the cultural differences of the individuals, groups, and organizations in the project stakeholder community so you can adapt communication strategies to avoid or reduce miscommunication and misunderstandings.
85
CV (Cost Variance)
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. (CV = EV-AC)
Positive CV indicates project is under budget
Zero CV indicates project is on budget
Negative CV indicates project is over budget
86
Daily Standup
A short, 15-minute meeting in which the complete team gets together for a quick status updates while standing in a circle. Also referred to as a daily scrum.
87
De Facto Regulations
Regulations that are widely accepted and adopted through use.
88
De Jure Regulations
Regulations that are mandated by law or have been approved by a recognized body of experts.
89
Debriefing
A less formal, more cooperative means of discussing the positives and the negatives of the project, what worked, and what will be done differently next time. This discussion includes technology issues, people issues, vendor relationships, and organizational culture.
90
Decision Making
The process of selecting a course of action from among multiple options.
91
Decision Tree Analysis
A diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty.
92
Decomposition
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
93
Deliverables
Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or projects.
94
Directions of Influence
A classification model that groups stakeholders on the basis of how they influence the project: upwards (senior management), downwards (team or specialists), outwards (external), sidewards (project manager's peers), and prioritization.
95
Directive PMO
A type of PMO that takes control of projects by directly managing the projects.
96
Discretionary Dependency
A relationship that is established based on knowledge of best practices within a particular application area or an aspect of the project where a specific sequence is desired.
97
Document Analysis
A technique used to gain project requirements from current documentation evaluation.
98
DoD (Definition of Done)
A team's checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.
99
DoR (Definition of Ready)
A team's checklist for a user-centric requirement that has all the information the team needs to be able to begin working on it.
100
EAC (Estimate at Completion)
The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete. (EAC = BAC/CPI)
101
EEF (Enterprise Environmental Factors)
Conditions, not under the immediate control of the team, that influence, constrain, or direct the project, program, or portfolio.
102
Effect-based Risk Classification
A way of analyzing the major risks inherent to a project that could have an impact on its success. These major risks include time, cost, quality, and scope.
103
Effort
The number of labor units required to complete a scheduled activity or WBS component, often expressed in hours, days, or weeks. Contrast with duration.
104
EI (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. EQ is also a commonly used abbreviation.
105
Elapsed Time
The actual calendar time required for an activity from start to finish.
106
EMV (Expected Monetary Value)
A method of calculating the average outcome when the future is uncertain. Calculated by multiplying the monetary value of a possible outcome by the probability it will occur.
107
Enhance
A strategy for managing positive risks or opportunities that involves increasing the probability that the opportunity will happen, or the impact it will have by identifying and maximizing enablers of these opportunities.
108
Escalate
The strategy in which you determine that a threat is outside the scope of the project or beyond the project manager's authority. You then forward the threat to a person or part of the organization at a higher level.
109
ETC (Estimate to Complete)
The expected cost to finish all the remaining project work. (ETC = EAC-AC)
110
EV (Earned Value)
A measure of work performed expressed in terms of the budget authorized for that work. (EV = %completed x PV)
111
EVM (Earned Value Management)
A methodology that combines scope, schedule, and resource measurements to assess project performance and progress.
112
Expert Judgement
Judgement provided based upon expertise in an application area, knowledge area, discipline, industry, etc., as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education, knowledge, skill, experience, or training.
113
Explicit Knowledge
Knowledge that can be codified using symbols such as words, numbers, and pictures. This type of knowledge can be documented and shared with others.
114
Exploit
A strategy for managing positive risks or opportunities that involves attempting to make sure that the opportunity happens.
115
External Dependency
Types of activity dependencies that exist between project activities and non-project activities and can be out of the project's control.
116
Facilitated Workshops
Organized working sessions held by project managers to determine a project's requirements and to get all stakeholders together to agree on the project's outcomes.
117
Facilitation
A skill used to lead or guide an assembled group toward a successful conclusion such as making a decision or finding a solution.
118
FF (Finish-to-Finish)
A logical relationship in which a successor activity cannot finish until a predecessor activity has finished.
119
FFP Contract (Firm Fixed Price Contract)
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. (type of Fixed Price Contract)
120
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.
121
Float
Also called slack. (see total float and free float)
122
Focus Groups
An elicitation technique that brings together pre-qualified stakeholders and subject matter experts to learn about their expectation and attitudes about a proposed product, service, or result.
123
FPEPA Contract (Fixed Price with Economic Price Adjustment Contract)
A fixed-price contract, but with a special provision allowing for pre-defined final adjustments to the contract price due to changed conditions, such as inflation changes, or cost increases (or decreases) for specific commodities. (Type of Fixed-price Contract)
124
FPIF Contract (Fixed Price Incentive Fee Contract)
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. (Type of fixed-price Contract)
125
Free Float
The amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.
126
FS (Finish-to-Start)
A logical relationship in which a successor activity cannot start until a predecessor activity has finished.
127
Functional Organization
An organizational structure in which staff is grouped by areas of specialization and the project manager has limited authority to assign work and apply resources.
128
Funding Limit Reconciliation
The process of comparing the planned expenditure of project funds against any limits on the commitment of funds for the project to identify any variances between the funding limits and the planned expenditures.
129
Gantt Chart
A bar chart of schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and the activity durations are shown as horizontal bars placed according to start and finish dates.
130
IFB (Invitation for Bid)
Generally, this term is equivalent to request for proposal. However, in some application areas, it may be a narrower or more specific meaning. A type of procurement document that is most commonly used when deliverables are commodities for which there are clear specifications and when the quantities are very large. The invitation is usually advertised and any seller may submit a bid. Negotiation is typically not anticipated. These are sometimes used interchangeably with RFPs.
131
Impediment
An obstacle that prevents the team from achieving its objectives.
132
Increment
A functional, tested, and accepted deliverable that is a subset of the overall project outcome.
133
Incremental Life Cycle
An adaptive project life cycle in which the deliverable is produced through a series of iterations that successively add functionality within a predetermined time frame. The deliverable contains the necessary and sufficient capability to be considered complete only after the final iteration.
134
Influence/Impact Grid
A classification model that groups stakeholders on the basis of their involvement in and impact on the project.
135
Influencing
The act of presenting a good case to explain why an idea, decision, or problem should be handled a certain way, without resistance form other individuals.
136
Information Radiator
The generic term for visual displays placed in a visual location so everyone can quickly see the latest information. In agile practice, also known as Big Visible Chart.
137
Insurable Risk
A risk that has only the potential for loss and no potential for profit or gain. An insurable risk is one for which insurance may be purchased to reduce or offset the possible loss. Types of insurable risks are direct property, indirect property, liability, and personnel-related.
138
Interactive Communication
An exchange of information between two or more people that ensures common understanding for everyone participating in that exchange.
139
Internal Dependency
A type of activity dependency that exists between project activities and is usually under the project's control.
140
Interpersonal Skills
Skills used to establish and maintain relationship with other people
141
Interivew
A formal or informal approach to elicit information from stakeholders by talking with them directly.
142
IRR (Internal Rate of Return)
The interest rate that makes the net present value of all cash flow equal to zero.
143
Issue
A current condition or situation that may have an impact on the project objectives.
144
Issue Log
A document where information about issues is recorded and monitored.
145
Iteration
A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is preformed.
146
Iterative Life Cycle
A project life cycle where the project scope is generally determined early in the project life cycle, but time and cost estimates are routinely modified as the project team's understanding of the product increases. Iterations develop the product through a series of repeated cycles, while increments successively add to the functionality of the product.
147
JAD (Joint Application Design)
Specialized workshops that include both SMEs and the development team together to discuss and improve on the software development process.
148
Kanban Board
A visualization tool that enables improvements to the flow of work by making bottlenecks and work quantities visible
149
Knowledge Management
Connecting individuals, in person or virtually, to share knowledge and collaborate together.
150
KPI (Key Performance Indicator)
A set metric used to evaluate a team's performance against the project vision and objectives.
151
Lag
The amount of time whereby a successor activity will be delayed with respect to a predecessor activity.
152
Lead
The amount of time whereby a successor activity can be advanced with respect to predecessor activity.
153
Leadership
The ability to step up and guide others to achieve results. Leadership abilities are gained through experience, building relationships, and taking on initiatives.
154
Lean
An agile method used primarily in manufacturing that focuses on achieving outcomes with little or no waste.
155
Lessons-learned Register
A project document used to record knowledge gained during a project so that it can be used in the current project and entered into the lessons-leaned repository.
156
Lessons-learned Repository
A store of historical information about lessons learned in projects.
157
Majority
A group decision-making method in which a majority of group members agree on the course of action to take.
158
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 project.
159
Make-or-Buy Decisions
Decisions made regarding the external purchase or internal manufacture of a product.
160
Management Reserves
An amount of the project budget or project schedule held outside of the performance measurement baseline (PMB) for management control purposes, that is reserved for unforeseen work that is within the scope of the project.
161
Mandatory Dependency
A relationship that is contractually required or inherent in the nature of the work.
162
Matrix Organization
An organizational structure in which the project manager shares responsibility with the functional managers for assigning priorities and for directing the work of persons assigned to the project.
163
MBI (Minimum Business Increment)
The smallest amount of value that can be added to a product or service that benefits the business.
164
Milestone Charts
A type of project schedule bar chart that only includes milestones or major deliverables as points in time.
165
Milestone List
A document that contains the significant points or events in a project.
166
Milestone
A significant point or event in a project, program, or portfolio
167
Mind Mapping
A technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas.
168
Mitigate
A strategy for managing negative risks or threats that involves taking action to reduce the probability of occurrence or the impact of a risk.
169
Monte Carlo Simulation
A analysis technique where a computer model is iterated many times, with the input values chosen at random for each iteration driven by the input data, including probability distributions and probabilistic branches. Outputs are generated to represent the range of possible outcome for the project.
170
Motivation
The inner drive that keeps people involved and wanting to complete work of high quality in a timely fashion.
171
Multi-criteria Decision Analysis
This technique utilize a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas.
172
MVP (Minimum Viable Product)
The smallest collection of features that can be included in a product for customers to consider it functional. In lean methodologies, it can be referred to as "bare bones" or "no frills" functionality.
173
Negotiated Settlements
Are undertaken to arrive at a final equitable settlement of all outstanding issues, claims, and disputes by negotiation.
174
Negotiation
An approach used by more than one individual to come to an agreement or resolution.
175
Nominal Group Technique
A technique that enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization.
176
NPS (Net Promoter Score)
Measures a customer's willingness to recommend a provider's products or services to another on a scale of -100 to 100.
177
NPV (Net Present Value)
The present value of all cash outflows minus the present value of all cash inflows.
178
Observations
The techniques used to gain knowledge of a specific job role, task, or function in order to understand and determine project requirements. This is also known as job shadowing.
179
OPA (Organizational Process Assets)
Plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization.
180
Opportunity
A risk that would have a positive effect on one or more project objectives.
181
Organizational Theory
The study of how people, teams, and organizations behave to look for common themes for the purpose of maximizing efficiency and productivity, problem solving, and meeting the stakeholder requirements of a project.
182
Outsourcing
Moving beyond the organization to secure services and expertise from an outside source on a contract or short-term basis.
183
Overlapping Relationships
A type of phase-to-phase relationship that contains phases that start prior to the previous phase ending.
184
Parametric Estimating
An estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters.
185
Pareto Chart
A histogram that is used to rank causes of problems in a hierarchical format.
186
PDM (Precedence Diagramming Method)
A technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed.
187
Phase Gate
A point 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.
188
Planning Package
A WBS component below the control account with known work content but without detailed schedule activities.
189
Plurality
Decisions made by the largest block in a group, even if a majority is not achieved.
190
PMIS (Project Management Information System)
An information system consisting of the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes.
191
PMO (Project Management Office)
A management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques. PMOs are more common in larger organizations because of the number of projects that can be in process all at the same time.
192
Political Awareness
The ability to recognize the power structure internal to the organization, and the ability to navigate the relationships.
193
Portfolio Management
The centralized management of one or more portfolios to achieve strategic objectives.
194
Portfolio
Project, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives.
195
Power/Influence Grid
A classification model that groups stakeholders on the basis of their levels of authority and interest in the project.
196
Precedence Relationship
A logical dependency used in the precedence diagramming methods.
197
Predictive Life Cycle
A form of project life cycle in which the projects scope, time, and cost are determined in the early phases of the life cycle.
198
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.
199
Probability Distribution
The scattering of values assigned to likelihood in a sample population. It can be visually depicted in the form of probability density function (PDF).
200
Procurement
The acquisition of goods and services from an external organization, vendor, or supplier to enable the deliverables of the project.
201
Procurement Audit
The review of contracts and contracting processes for completeness, accuracy, and effectiveness.
202
Procurement Documents
The documents utilized in bid and proposal activities, which include the buyer's invitation for bid, invitation for negotiations, request for information, request for quotation, request for proposal, and settler's responses.
203
Procurement Management Plan
A component of the project of program management plan that describes how a project team will acquire goods and services from outside of the performing organization.
204
Procurement SOW
Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products, services, or results.
205
Product Analysis
For projects that have a product as the deliverable, it is a tool to define scope that generally means asking questions about a product and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be manufactured.
206
Product Backlog
A prioritized list of customer requirements and the first step of Scrum in which priority is based on the riskiness and business value of the user story.
207
Product Box Exercise
A technique used to explain an overarching solution wherein stakeholders try to describe aspects of a solution in the same way a marketer might describe product features and benefits on a box.
208
Product Owner
An individual or an organization who is responsible for gathering inputs about a product from the customer and translating the requirements into the product vision for the team and stakeholders.
209
Product Roadmap
A high level visual summary of the product or products of the project that includes goals, milestones, and potential deliverables.
210
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.
211
Program
Related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually. A project may or may not be part of a program, but a program will always have projects.
212
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.
213
Project Artifact
Any document related to the management of a project
214
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.
215
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.
216
Project Life Cycle
A series of phases that a project passes through from its start to its completion.
217
Project Management Plan
The document that describes how the project will be executed, monitored and controlled, and closed.
218
Project Management Software
A computer application that helps plan, organize, and manage project resources and develop resource estimates for activities.
219
Project Management
The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.
220
Project Manager
The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives.
221
Project Phase
A collection of logically related project activities that culminates in the completion of one or more deliverables.
222
Project Requirements
For a project, these are the agreed-upon conditions or capabilities of a product, service, or outcome that a project is designed to satisfy.
223
Project Schedule Network Diagram
A graphical representation of the logical relationship among the project schedule and activities.
224
Project Schedule
An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources.
225
Project Scope Statement
The description of the project scope, major deliverables, assumptions, and constraints.
226
Project Scope
The features and functions that characterize a product, service, or result.
227
Project Team
A set of individuals who support the project manager in performing the work of the project to achieve its objectives.
228
Project
A temporary endeavor undertaken to create a unique product, service, or result.
229
Projectized Organization
A structure where a project manager and a core project team operate as a completely separate organizational unit within the parent organization.
230
Prototypes
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.
231
Pull Communications
Messages that require the interested people to access the information based on their own initiative.
232
Push Communications
Messages that are sent out to people who need to receive the information.
233
PV (Present Value)
The current value of a future sum of money or stream of cash flows given a specific rate of return. (PV=FV/(1+r)^n)
234
PV (Planned Value)
The authorized budget assigned to scheduled work.
235
QFD (Quality Function Deployment)
Workshops that are commonly used in the manufacturing field to determine new product development requirements.
236
Qualified Vendors
The vendors who are approved to deliver the products, services, or results based on the procurement requirements identified for a project.
237
Qualified Vendors List
Contains details regarding vendors who meet the organization's requirements and to whom requests can be sent.
238
Qualitative Risk Analysis
A technique used to determine the probability of occurrence and the impact of identified risk.
239
Quality Audit
A structured, independent process to determine if project activities comply with organizational and project policies, processes, and procedures.
240
Quality Gate
A special type of gate located before a phase that is strongly dependent upon the outcome of a previous phase. The quality gate process is a formal way of specifying and recording the transition between stages in the project life cycle.
241
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.
242
Quality Metric
A description of a project of product attribute and how to measure it.
243
Quality
The degree to which a set of inherent characteristics fulfills requirements.
244
Quantitative Risk Analysis
Technique used to assess the risk exposure events to overall project objectives and determine the confidence levels of achieving the project objectives.
245
Questionnaires
Written sets of questions designed to quickly accumulate information from a large number of respondents.
246
RACI Chart (Responsible, Accountable, Consulted, and Informed)
A common type of Responsibility Assignment Matrix (RAM) that uses responsible, accountable, consult, and inform statuses to define the involvement of stakeholders in project activities.
247
RAM (Responsibility Assignment Matrix)
A grid that shows the project resources assigned to each work package.
248
RBS (Risk Breakdown Structure)
A hierarchical representation of potential sources of risk.
249
Recognition
A more personalized, intangible, and experiential event that focuses on behavior rather than outcome.
250
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.
251
Relative Authority
The project manager's authority relative to the functional manager's authority over the project and the project team.
252
Requirements Documentation
A description of how individual requirements meet the business need for the project.
253
Requirements Management Plan
A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed.
254
Requirements Traceability Matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
255
Resource Calendar
A calendar that identifies the working days and shifts upon which each specific resource is available.
256
Resource Leveling
A resource optimization technique in which adjustments are made to the project schedule to optimize the allocation of resources and which may affect the critical path.
257
Resource Management Plan
A component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled.
258
Resource Requirements
The types and quantities of resources required for each activity in a work package.
259
Reward
A tangible, consumable item that is given to a person based on a specific outcome or an achievement.
260
Reward and Recognition Plan
A formalized way to reinforce performance or behavior.
261
RFI (Request for Information)
A type of procurement document whereby the buyer requests a potential seller to provide various pieces of information related to a product or service or seller capability.
262
RFP (Request for Proposal)
A type of procurement document used to request proposals from prospective sellers of products or services. In some application areas, it may have a narrower or more specific meaning.
263
RFQ (Request for Quotation)
A type of procurement document used to request price quotations from prospective sellers of common or standard products or services. Sometimes used in place of request for proposal and, in some application areas, it may have a narrower or more specific meaning.
264
Risk Appetite
The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward.
265
Risk Categorization
Organization by sources of risk (e.g., using the RBS), the area of the project affected (e.g., using the WBS), or other useful category (e.g., project phase) to determine the areas of the project most exposed to the effects of uncertainty.
266
Risk Impact
The likely effect on project objectives if a risk event occurs.
267
Risk Management Plan
A component of the project, program, or portfolio management plan that describes how risk management activities will be structured and performed.
268
Risk Probability
The likelihood that a risk event will occur or prove true during the project.
269
Risk Register
A repository in which outputs of risk management processes or recorded.
270
Risk Threshold
The level or risk exposure above which risks are addressed and blow which risks may be accepted.
271
Risk Tolerance
The maximum amount of risk, and the potential impact of that risk occurring, that a project manager or key stakeholder is willing to accept.
272
Risk Workshop
A technique that uses a special meeting conducted for the purpose of identifying project risks. In addition to the project team members, this workshop might also include the project sponsor, SMEs, customer representatives, and other stakeholders, depending on the size of the project.
273
Risk
An uncertain event or condition that , if it occurs, has a positive or negative effect on one or more project objectives.
274
ROI (Return on Investment)
A financial metric of profitability that measures the gain or loss from an investment relative to the amount of money invested. (ROI = (B-C)/C)
275
Root Cause Analysis
An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. A root cause may underlie more than one variance or defect or risk.
276
SAFe (Scaled Agile Framework)
A knowledge base of integrated patterns for enterprise-scale lean-agile development.
277
Salience Model
A classification model that groups stakeholders on the basis of their level of authority, their immediate needs, and how appropriate their involvement is in terms of the project.
278
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.
279
Scope Baseline
The approved version of a scope statement, WBS, and it associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results.
280
Scope Creep
The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.
281
Scope Management Plan
A component of the project management plan or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.
282
Scrum Master
The coach of the development team and process owner in the Scrum framework. Removes obstacles, facilitates productive events, and defends the team from disruptions.
283
Scrum Team
Dedicated, self-managing, cross-functional, fully empowered individuals who deliver the finished work required by the customer.
284
Scrum
An agile framework for developing and sustaining complex products, with specific roles, events, and artifacts.
285
Sequential Relationships
A type of phase-to-phase relationship that contains consecutive phases that only start when the previous phase is complete.
286
Servant Leadership
A type of leadership style used in agile and other types of projects which encourages the self-definition, self-discovery, and self-awareness of team members by listening, coaching, and providing an environment which allows them to grow.
287
SF (Start-to-Finish)
A logical relationship in which a predecessor activity cannot finish until a successor activity has started.
288
Share
A strategy for managing positive risks or opportunities that involves allocating some or all of the ownership of the opportunity to a third party.
289
Simulation
An analytical technique that models the combined effect of uncertainties to evaluate their potential impact on objectives.
290
SLA (Service Level Agreement)
A contract between a service provider (either internal or external) and the end user that defines the level of service expected from the service provider.
291
SoS (Scrum of Scrums)
A technique to operate Scrum at scale for multiple teams working on the same product, coordinating discussions of progress on their interdependencies, and focusing on how to integrate the delivery of software, especially in areas of overlap.
292
Source of Selection Criteria
A set of attributes desired by the buyer which a seller is required to meet or exceed to be selected for a contract.
293
Source-based Risk Classification
A method of analyzing risk in terms of its origins.
294
SPI (Schedule Performance Index)
A measure of schedule efficiency expressed as the ratio of earned value to planned value. (SPI=EV/PV)
SPI>1.0 indicates ahead of schedule
SPI=1.0 indicates on schedule
SPI<1.0 indicates behind schedule
295
Sprint Backlog
A list of work items identified by the Scrum team to be completed during the Scrum sprint.
296
Sprint Planning
A collaborative event in Scrum in which the Scrum team plans the work for the current sprint.
297
Sprint retrospective
This critical part of the Scrum process is attended by the Product owner, Scrum Master, and the Scrum team to analyze from a process perspective what is working well and what is not and to agree upon changes to implement.
298
Sprint Review
A review at the end of each iteration with the Product Owner and other customer stakeholders to review the progress of the product, get early feedback, and review an acceptance from Product Owner of the stories delivered in the iteration. Also referred to as a Demo.
299
Sprint
A timeboxed iteration in Scrum.
300
SS (Start-to-Start)
A logical relationship in which a successor activity cannot start until a predecessor activity has started.
301
Stakeholder Analysis
A technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project.
302
Stakeholder Cube
A three-dimensional classification model that builds on the previous two-dimensional grids to group stakeholders.
303
Stakeholder Engagement Assessment Matrix
A matrix that compares current and desired stakeholder engagement levels
304
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.
305
Stakeholder Register
A project document including the identification, assessment, and classification of project stakeholders.
306
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.
307
Standard
A document established by an authority, custom, or general consent as a model or example.
308
Statistical Sampling Process
A process that involves dividing sampling data into two categories - attribute and variable - each of which is gathered according to sampling plans. As corrective actions are taken in response to analysis of statistical sampling and other quality control activities, and as trend analysis is performed, defects and process variability should be reduced.
309
Statistical Sampling
Choosing part of a population of interest for inspection.
310
Storyboarding
The prototyping method that uses visuals or images to illustrate a process or represent a project outcome. Storyboards are useful to illustrate how a product, service, or application will function or operate when it's complete.
311
Supportive PMO
A type of PMO that provides a consultative role to projects by supplying templates, best practices, training, access to information, and lessons learned from other projects.
312
SV (Schedule Variance)
A measure of schedule performance expressed as the difference between the earned value and the planned value. (SV = EV-PV)
SV>0 indicates ahead of schedule
SV=0 indicates on schedule
SV<0 indicates behind schedule
313
SWOT analysis
An analysis of strengths, weaknesses, opportunities, and threats of an organization, project, or option.
314
T&M Contract (Time and Material Contract)
A type of contract that is a hybrid contractual arrangement containing aspects of both cost-reimbursable and fixed-price contracts.
315
T-Shaped
Refers to a person with one deep area of specialization and broad ability in the rest of the skills required by the team.
316
Tacit Knowledge
Personal knowledge that can be difficult to articulate and share such as beliefs, experience, and insights.
317
Task Board
Used to visualize the work and enable the team and stakeholders to track their progress as work is performed during an iteration. Examples of task boards include Kanban boards, to-do lists, procedure checklists, and Scrum boards.
318
Team Building
The process of continually supporting and working collaboratively with team members in order to enable a team to work together to solve problems, diffuse interpersonal issues, share information, and tackle project objectives as a unified force.
319
Team Charter
A document that records the team values, agreements, and operating guidelines as well as establishing clear expectations regarding acceptable behavior by project team members.
320
Team Management Plan
A component of the resource management plan that describes when and how team members will be acquired and how long they will be needed.
321
Team Resource Management
The processes necessary to organize, manage, and lead the people on the project team as well as the processes needed to procure and manage physical resources for a project.
322
Team-building Activities
The specific functions or actions taken to help the team to develop into a mature, productive team. They can be formal or informal, brief or extended, and facilitated by the project manager or a group facilitator.
323
Teaming Agreement
A legal contractual agreement between two or more parties to form a joint venture or any other arrangement as defined by the parties to meet the requirements of a business opportunity. The parties can be internal or external to the organization executing the project.
324
Term Contract
A type of contract that engages the vendor to deliver a set amount of service - measured in staff-hours or a similar unit - over a set period of time.
325
Threat
A risk that would have a negative effect on one or more project objectives.
326
Three-point Estimating
A technique 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.
327
Timebox
A fixed period of time; for example, 1 week, 2 weeks, 3 weeks, or 1 month.
328
Tolerance
The quantified description of acceptable variation for a quality requirement.
329
Total Float
The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint.
330
TQM (Total Quality Management)
An approach to improve business results through an emphasis on customer satisfaction, employee development, and processes rather than on functions.
331
Training
An activity in which team members acquire new or enhance skills, knowledge, or attitudes.
332
Transfer
A strategy for managing negative risks or threats that involves shifting the impact and ownership of the risk to a third party and paying a risk premium to the party taking on the liability of the risk.
333
Trend Analysis
An analytical technique that uses mathematical models to forecast future outcomes based on historical results.
334
Trigger Condition
An event or situation that indicates that a risk is about to occur.
335
Unanimity
Agreement by everyone in the group on a single course of action.
336
Unique Identification Code
A specific configuration of a code of accounts that assigns a particular alphanumeric sequence of characters to each element of a WBS.
337
User Story
A brief description of deliverable value for a specific user. It is a promise for a conversation to clarify details.
338
Validate Scope
The process of formalizing acceptance of the completed project deliverables.
339
Value Stream Mapping
A lean enterprise technique used to document, analyze, and improve the flow of information or materials required to produce a product or service for a customer.
340
Value Stream
An organizational construct that focuses on the flow of value to customers through the delivery of specific products or services.
341
Variable Sampling Data
Data from a sample that is measured on a continuous scale such as time, temperature, or weight.
342
Variance Analysis
A technique for determining the cause and degree of difference between the baseline and the actual performance.
343
Variance
A quantifiable deviation, departure, or divergence away from a known baseline or expected value.
344
Version Control
A system that records changes to a file, in a way that allows you to retrieve previous changes made to it.
345
Virtual Team
A group of people with a shared goal who fulfill their roles with little or not time spent meeting face-to-face.
346
Waiver
The giving up of a contract right, even inadvertently.
347
Warranty
A promise, explicit or implied, that goods or services will meet a predetermined standard.
348
WBS dictionary
A document that proves detailed deliverable, activity, and scheduling information about each component in the work breakdown structure.
349
WBS (Work Breakdown Structure)
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.
350
Work Package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
351
Work Performance Data
The raw observations and measurements identified during activities being performed to carry out the project work. They can be recorded in the PMIS and project documents.
352
Work Performance Information
The performance data collected from controlling processes, analyzed in comparison with project management plan components, project documents, and other work performance information.
353
Work Performance Report
The physical or electronic representation of work performance information compiled in project documents, intended to generate decisions, actions, or awareness.
354
Work Shadowing
An on-the-job technique that enables someone to learn about and perform a job while observing and working with another more experienced person, or mentor.
