PMP Terms Flashcards
1
Q
80/20 rule
A
A general guideline with many applications: states that 80% of problems come from 20% of causes
2
Q
AB testing
A
Marketing approach used to determine user preferences by showing different sets of users similar services with one independent value
3
Q
AC (Actual Cost)
A
The realized cost incurred for the work performed on an activity during a specific time
4
Q
accept
A
Strategy for managing negative risks or opportunities that involves acknowledging a risk and not taking any action until the risk occurs (accepting the risk for what it is)
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 evet 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 schedule of activities that shows the activity description, activity identifier, and a 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
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
PM method 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
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
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 assumption 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
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
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
Budget at Completion (BAC)
Sum of all budgets established for the work to be performed
26
benchmarking
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
27
benefit cost analysis
Financial analysis tool used to determine the benefits provided by a project against its cost
28
benefits management plan
documented explanation defining the processes for creating, maximizing, and sustaining the benefits provided by a project or program
29
bidder conferences (a.k.a. vendor conferences, pre-bid conferences, or contractor 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
30
bottom-up estimating
A method of estimating project duration or cost by aggregating the estimates of the lower-level components of the WBS (more accurate then top-down)
31
breach of contract
The failure to meet some or all the obligations of a contract
32
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
33
business case
Documented economic feasibility study used to establish the validity of the benefits of a selected component lacking sufficient definition and is used as a basis for the authorization of further project management activities
34
business risk (4 kinds)
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
35
business value
The net quantifiable benefit derived from a business endeavor. The benefit may be tangible, intangible, or both
36
Change Control Board (CCB)
Formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions
37
cease and desist letter
Document sent to an individual or business to stop (cease) allegedly illegal activities and to not undertake them again (desist)
38
change control form (a.k.a. change request)
Document used to request a project change. They can also be recommendations for taking corrective or preventative actions. Request goes to Change Control Board (CCB) for approval.
39
change control system
A set of procedures that describes how modifications to the project deliverables and documentation are managed and controlled
40
change management plan
Component of the project management plan that establishes the Change Control Board (CCB), documents the extent of its authority, and describes how the change control system will be implemented
41
Continuous Improvement (CI)
The ongoing effort to improve products, services, or processes
42
Close Project/Phase process
The process of finalizing all activities for the project, phase, or contract
43
close-out meetings
Sessions held at the end of a project or phase; they involve discussing the work and capturing lessons learned
44
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
45
coaching
The act of giving guidance and direction to another person so that they can make better decisions
46
code of accounts
A numbering system used to uniquely identify each component of the Work Breakdown Structure (WBS)
47
Code of Ethics and Professional Conduct
A PMI publication that describes the ethical and professional behavior expectations of an individual working as a project management professional
48
communication models
A description, analogy, or schematic used to represent how the communication process will be performed for the project
49
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.
50
communication styles assessment
A technique to identify the preferred communication method, format, and content for stakeholders for planned communication activities
51
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
52
completion contract
type of contract that is completed when the vendor delivers the product to the buyer and the buyer accepts the product
53
configuration management
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
54
configuration management system
collection of procedures used to track project artifacts and monitor and control changes to these artifacts
55
conflict management
The application of one or more strategies for dealing with disagreements that may be detrimental to team performance
56
context diagram
A visual depiction of the product scope showing a business system (process, equipment, cpu system, etc.), and how people and other systems interact with it
57
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
58
contingency reserves
Time or money allocated in the schedule or cost baseline for known risks with active response strategies
59
contract change control system
The system used to collect, track, adjudicate, and communicate changes to a contract
60
control account
A management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement
61
Control Procurements process
The process of managing procurement relationships, monitoring contract performance, making changes and corrections as appropriate, and closing out contracts
62
controlling PMO (project management office)
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 to governance
63
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
64
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
65
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
66
cost management plan
A component of a project or program management plan that describes how costs will be planned, structured, and controlled
67
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
68
cost of non-conformance
The money spent after a project is complete because of failures. This includes internal and external failure costs
69
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
70
Cost Plus Aware Fee (CPAF) 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
71
Cost Plus Fixed Fee (CPFF) contract
A type of cost-reimbursable contract where the buyer reimburses the seller for the seller's allowable costs plus a fixed amount of profit (fee)
72
Cost Performance Index (CPI)
A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost
73
Cost Plus Incentive Fee (CPIF) contract
A type of cost-reimbursable contract where the buyer reimburses the seller for the sellers allowable costs, and the seller earns its profit if it meets defined performance criteria
74
critical path activity
Any activity on the critical path in a project schedule
75
critical path
The sequence of activities that represents the longest path through a project, which determines the shortest possible duration
76
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 misunderstanding
77
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
78
daily standup
A short, 15-minute meeting in which the complete team gets together for a quick status update while standing in a circle. Also referred to as a daily scrum
79
de facto regulations
Regulations that are widely accepted and adopted through use
80
de jure regulations
Regulations that are mandated by law or have been approved by a recognized body of experts
81
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.
82
decision making
The process of selecting a course of action from among multiple options
83
decision tree analysis
A diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty
84
decomposition
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts
85
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 projects
86
directions of influence
A classification model that groups stakeholders based on how they influence the project: upwards = senior management
downwards = team or specialists
outwards = external
sidewards = project manager's peers
87
directive PMO
A type of PMO that takes control of projects by directly managing the projects
88
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
89
document analysis
A technique used to gain project requirements from current documentation evaluation
90
Definition of Done (DoD)
A team's checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use
91
Definition of Ready (DoR)
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
92
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
93
Enterprise Environmental Factors (EEF)
Conditions that are not under the immediate control of the team, and that influence, constrain, or direct the project, program, or portfolio
94
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 are:
Time
Cost
Quality
Scope
95
effort
The number of labor units required to complete a scheduled activity or WBS component, often expressed in hours, days, or weeks.
96
emotional intelligence (EI)
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. a.k.a. EQ
97
elapsed time
The actual calendar time required for an activity from start to finish
98
Expected Monetary Value (EMV)
A method of calculating the average outcome when the future is uncertain
99
enhance
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
100
escalate
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.
101
Estimate to Complete (ETC)
The expected cost of finishing all the remaining project work
102
Earned Value (EV)
A measure of work performed expressed in terms of the budget authorized for that work
103
Earned Value Management (EVM)
A methodology that combines scope, schedule, and resource measurements to assess project performance and progress
104
expert judgment
Judgment 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
105
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
106
exploit
A strategy for managing positive risks or opportunities that involves attempting to make sure that the opportunity happens
107
external dependency
Types of activity dependencies that exist between project activities and non-project activities and can be out of the project's control
108
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
109
facilitation
A skill used to lead or guide an assembled group toward a successful conclusion such as making a decision or finding a solution
110
Finish-to-Finish (FF)
A logical relationship in which a successor activity cannot finish until a predecessor activity has finished
111
Firm Fixed Price (FFP) 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
112
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
113
focus groups
An elicitation technique that brings together pre-qualified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result
114
Fixed Price with Economic Price Adjustment (FPEPA) 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.
115
Fixed Price Incentive Fee (FPIF) 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
116
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
117
Finish-to-Start
A logical relationship in which a successor activity cannot start until a predecessor activity has finished
118
functional organization
An organizational structure in which staff is grouped by areas of specialization (departments) and the project manager has limited authority to assign work and apply resources
119
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
120
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
121
Invitation for Bid (IFB)
Similar to request for proposal, however, 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.
122
impediment
An obstacle that prevents the team from achieving its objectives
123
increment
A functional, tested, and accepted deliverable that is a subset of the overall project outcome
124
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.
125
influence/impact grid
A classification model that groups stakeholders on the basis of their involvement in and impact on the project
126
influencing
The act of presenting a good case to explain why an idea, decision, or problem should be handled a certain way, without resistance from other individuals
127
information radiator
The generic term for visual displays placed in a visible location so everyone can quickly see the latest information. In agile practice, also known as "Big Visible Chart"
128
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.
129
interactive communication
An exchange of information between two or more people that ensures common understanding for everyone participating in that exchange
130
internal dependency
A type of activity dependency that exists between project activities and is usually under the project's control
131
interpersonal skills
Skills used to establish and maintain relationships with other people
132
interview
A formal or informal approach to elicit information from stakeholders by talking with them directly
133
Internal Rate of Return (IRR)
The interest rate that makes the net present value of all cash flow equal to zero
134
issue
A current condition or situation that may have an impact on the project objectives
135
issue log
A document where information about issues is recorded and monitored
136
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
137
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 successively add to the functionality of the product
138
Joint Application Design (JAD)
Specialized workshops that include both subject matter experts and the development team together to discuss and improve on the software development process
139
Kanban board
A visualization tool that enables improvements to the flow of work by making bottlenecks and work quantities visible
140
knowledge mangement
Connecting individuals, in person or virtually, to share knowledge and collaborate together
141
Key Performance Indicator (KPI)
A set metric used to evaluate a team's performance against the project vision and objectives
142
lag
The amount of time a successor activity will be delayed with respect to a preceding activity
143
lead
The amount of time a successor activity can be advanced with respect to predecessor activity
144
lean
An agile method used primarily in manufacturing that focuses on achieving outcomes with little or no waste
145
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-learned repository
146
lessons-learned repository
A store of historical information about lessons learned in projects
147
majority
A group decision-making method in which a majority of group members agree on the course of action to take
148
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
149
make-or-buy decisions
Decisions regarding the external purchase or internal manufacture of a product
150
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
151
mandatory dependency
A relationship that is contractually required or inherent in nature of the work
152
matrix organization
An organizational structure in which the project manager shares responsibility with the functional (department) managers for assigning priorities and for directing the work of persons assigned to the project
153
Minimum Business Increment (MBI)
The smallest amount of value that can be added to a product or service that benefits the business
154
milestone
A significant point or event in a project, program, or portfolio
155
milestone charts
A type of project schedule bar chart that only includes milestone or major deliverables as points in time
156
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
157
mitigate
A strategy for managing negative risks or threats that involves taking action to reduce the probability of occurrence or the impact of risk
158
Monte Carlo simulation
An 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 outcomes for the project
159
multi-criteria decision analysis
This technique utilizes 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
160
Minimum Viable Product (MVP)
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
161
negotiated settlements
Undertaken to arrive at a final equitable settlement of all outstanding issues, claims, and disputes by negotiation
162
negotiation
An approach used by more than one individual to come to an agreement or resolution
163
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
164
Net Promoter Score (NPS)
Measures a customer's willingness to recommend a provider's products or services to another on a scale of -100 to 100
165
Net Present Value (NPV)
The present value of all cash flows minus the present value of all cash inflows
166
Organizational Process Assets (OPA)
Plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization
167
opportunity
A risk that would have a positive effect on one or more project objectives
168
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
169
outsourcing
Moving beyond the organization to secure services and expertise from an outside source on a contract or short-term basis
170
overlapping relationships
A type of phase-to-phase relationship that contains phases that start prior to the previous phase ending
171
parametric estimating
An estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters
172
Pareto chart
A histogram that is used to rank causes of problems in a hierarchical format
173
Precedence Diagramming Method (PDM)
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 performed
174
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
175
planning package
A WBS component below the control account with known work content but without detailed schedule activites
176
plurality
Decisions made by the largest block in a group, even if a majority is not achieved
177
Project Management Information System (PMIS)
An information system consisting of the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes
178
Project Management Office (PMO)
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
179
political awareness
The ability to recognize the power structure internal to the organization, and the ability to navigate the relationships
180
portfolio management
The centralized management of one or more portfolios to achieve strategic objectives
181
portfolio
Projects, programs, subsidiary portfolios and operations managed as a group to achieve strategic objectives
182
Power/influence grid
A classification model that groups stakeholders on the basis of their levels of authority and involvement in the project
183
Power/interest grid
A classification model that groups stakeholders on the basis of their levels of authority and interest in the project
184
Precedence relationship
A logical dependency used in the precedence diagramming methods
185
predictive life cycle
A form of project life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle
186
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
187
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
188
procurement
The acquisition of goods and services from an external
organization, vendor, or supplier to enable the
deliverables of the project.
189
procurement audit
The review of contracts and contracting processes for completeness, accuracy, and effectiveness
190
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.
191
procurement management plan
A component of the project or program management plan that describes how a project team will acquire good and services from outside of the performing organization
192
procurement Statement of Work (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
193
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
194
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
195
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
196
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
197
product roadmap
A high-level visual summary of the product or products of the project that includes goals, milestones, and potential deliverables
198
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
199
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
200
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
201
project artifact
Any document related to the management of a project
202
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 organization resources to project activities
203
project governance
The framework, functions, and processes that guide project management activities to create a unique product to meet goals
204
project life cycle
A series of phases that a project passes through from its start to its completion
205
project management plan
The document that describes how the project will be executed, monitored, and controlled, and closed
206
project management software
A computer application that helps plan, organize, and manage project resources and develop resource estimates for activities
207
project management
The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements
208
project manager
The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives
209
project phase
A collection of logically related project activities that culminates in the completion of one or more deliverables
210
project requirements
For a project, these are the agree-upon conditions or capabilities of a product, service, or outcome that a project is designed to satisfy
211
project schedule network diagram
A graphical representation of the logical relationships among the project schedule activities. An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources
212
project scope statement
The description of the project scope, major deliverables, assumptions, and constraints
213
project scope
The features and functions that characterize a product service or result
214
project
A temporary endeavor undertaken to create a unique product, service, or result
215
projectized organization
A structure where a project manager and a core project team operate as a separate organizational unit within the parent organization
216
prototypes
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it
217
pull communications
Messages that require the interested people to access the information based on their own initiative
218
push communications
Messages that are sent out to people who need to receive information
219
Present Value
The current value of a future sum of money or stream of cash flows given a specific rate of return
220
Planned Value
The authorized budget assign to scheduled work
221
Quality function deployment (QFD)
Workshops that are commonly used in the manufacturing field to determine new product development requirements
222
qualified vendors
The vendors who are approved to deliver the products, services, or results based on the procurement requirements identified for a project
223
qualified vendors list
Contains details regarding vendors who meet the organizations requirements and to whom requests can be sent
224
qualitative risk analysis
A technique used to determine the probability of occurrence and the impact of identified risk
225
quality audit
A structured, independent process to determine if project activities comply with organizational and project policies, processes, and procedures
226
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
227
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
228
quality metric
A description of a project or product attribute and how to measure it
229
quality
The degree to which a set of inherent characteristics fulfills requirements
230
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
231
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 stakeholder in project activities
232
Responsibility Assignment Matrix (RAM)
A grid that shows the project resources assigned to each work package
233
Risk Breakdown Structure (RBS)
A hierarchical representation of potential sources of risk
234
recognition
A more personalized, intangible, and experiential event that focuses on behavior rather than outcome
235
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
236
relative authority
The project managers authority relative to the functional managers authority over the project and the project team
237
requirements documentation
A description of how individual requirements meet the business need for the project
238
requirements management plan
A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed
239
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them
240
resource calendar
A calendar that identifies the working days and shifts upon which each specific resource is available
241
resource levelling
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
242
resource management plan
A component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled
243
resource requirements
The types and quantities of resources required for each activity in a work package
244
reward and recognition plan
A formalized way to reinforce performance or behavior
245
Request for Information (RFI)
A type of procurement document used to request proposals from prospective sellers of products or services
246
Request for Quotation (RFQ)
A type of procurement document used to request price quotations from prospective sellers of common or standard products or services
247
risk appetite
The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward
248
risk categorizaiton
Organization by sources of risk, the area of project affected, or other useful category to determine the areas of the project most exposed to the effects of uncertainty
249
risk impact
The likely effect on project objectives if a risk event occurs
250
risk management plan
A component of the project, program, or portfolio management plan that describes how risk management activities will be structured and performed
251
risk probability
The likelihood that a risk event will occur or prove true during the project
252
risk register
A repository in which outputs of risk management processes are recorded
253
risk threshold
The level of risk exposure above which risks are addressed and below which risks may be accepted
254
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
255
risk workshop
A technique that uses a special meeting conducted for the purpose of identifying project risks. This meeting can include the project team, project sponsor, Subject Matter Experts, customer representatives, and other stakeholders
256
risk
An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives
257
Return on Investment (ROI)
A financial metric of profitability that measures the gain or loss from an investment relative to the amount of money invested
258
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
259
Scaled Agile Framework (SAFe)
A knowledge base of integrated patterns for enterprise-scale lean-agile development
260
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 the terms of the project
261
schedule management plan
A component of the project and program management plan that establishes the criteria and the activities for developing, monitoring, and controlling the schedule
262
scope baseline
The approved version of a scope statement, WBS, and it's associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results
263
scope creep
The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources
264
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
265
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
266
Scrum team
Dedicated, self-managing, cross-functional, fully empowered individuals who deliver the finished work required by the customer
267
Scrum
An agile framework for developing and sustaining complex products, with specific roles, events, and artifacts
268
sequential relationships
A type of phase-to-phase relationship that contains consecutive phases that only start when the previous phase is complete
269
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
270
Start-to-Finish (SF)
A logical relationship in which a predecessor activity cannot finish until a successor activity has started
271
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
272
simulation
An analytical technique that models the combined effect of uncertainties to evaluate their potential impact on objectives
273
Service Level Agreement (SLA)
A contract between a service provided and the end user that defines the level of service expected from the service provider
274
Scrum of Scrums (SoS)
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
275
source 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
276
source-based risk classification
A method of analyzing risk in terms of its origins
277
Schedule Performance Index (SPI)
A measure of schedule efficiency expressed as the ratio of earned value to planned value
SPI = EV / PV
278
Sprint backlog
A list of work items identified by the Scrum team to be completed during the Scrum sprint
279
Sprint planning
A collaborative event in Scrum in which the Scrum team plans the work for the current sprint
280
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
281
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. aka Demo
282
Sprint
A timeboxed iteration in Scrum
283
Start-to-Start (SS)
A logical relationship in which a successor activity cannot start until a predecessor activity has started
284
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
285
stakeholder cube
A three-dimensional classification model that builds on the previous two-dimensional grids to group stakeholders
286
Stakeholder Engagement Assessment Matrix
A matrix that compares current and desired stakeholder engagement level
287
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
288
stakeholder register
A project document including the identification, assessment, and classification of project stakeholders
289
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.
290
standard
A document established by an authority, custom, or general consent as a model for example
291
Statistical sampling process
A process that involves dividing sampling data into two categories - attribute and variable.
As corrective actions are taken in response to analysis of statistics and other quality control activities, and as trend analysis is performed, defects and process variability should be reduced
292
statistical sampling
Choosing part of a population of interest for inspection
293
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 is complete
294
supportive PMO
The 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
295
Schedule Variance (SV)
A measure of schedule performance expressed as the difference between the earned value and the planned value
SV = EV - PV
296
SWOT analysis
An analysis of Strengths, Weaknesses, Opportunities, and Threats of an organization, project, or option
297
Time and Material (T&M) contract
A type of contract that is hybrid contractual arrangement containing aspect of both cost-reimbursable and fixed-price contracts
298
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
299
tactic knowledge
Personal knowledge that can be difficult to articulate and share such as beliefs, experience, and insights
300
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
301
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.
302
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
303
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
304
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
305
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
306
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
307
threat
A risk that would have a negative effect on one or more project objectives
308
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
309
timebox
A fixed period set of time
310
tolerance
The quantified description of acceptable variation for a quality requirement
311
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
312
Total Quality Management (TQM)
An approach to improve business results through an emphasis on customer satisfaction, employee development, and processes rather than on functions
313
training
An activity in which team members acquire new or enhanced skills, knowledge, or attitudes
314
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
315
trend analysis
An analytical technique that uses mathematical models to forecast future outcomes based on historical results
316
trigger condition
An event or situation that indicates that a risk is about to occur
317
unanimity
Agreement by everyone in the group on a single course of action
318
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
319
user story
A brief description of deliverable value for a specific user. It is a promise for a conversation to clarify details
320
Validate Scope
The process of formalizing acceptance of the completed project deliverables
321
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
322
value stream
An organizational construct that focuses on the flow of value to customers through the delivery of specific products or services
323
variable sampling data
Data from a sample that is measured on a continuous scale such as time, temperature, or weight
324
variance
A quantifiable deviation, departure, or divergence away from a known baseline or expected value
325
variance analysis
A technique for determining the cause and degree of difference between the baseline and the actual performance
326
version control
A system that records changes to a file, in a way that allows you to retrieve previous changes made to it
327
waiver
The giving up of a contract right, even inadvertently
328
warranty
A promise, explicit or implied, that goods or services will meet a predetermined standard
329
WBS dictionary
A document that provides detailed deliverable, activity, and scheduling information about each component in the work breakdown structure
330
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
331
work package
The work defined at the lowest level of the work breakdown structure for which cost, and duration are estimated and managed
332
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 document
333
work performance report
The physical or electronic representation of work performance information compiled in project documents, intended to generate decisions, actions, or awareness
