PMBOK 7th Edition Definitions Flashcards

1
Q

Acceptance Criteria.

A

A set of conditions that is required to be met before deliverables are accepted.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Accuracy.

A

Within the quality management system, accuracy is an assessment of correctness.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Actual Cost (AC).

A

The realized cost incurred for the work performed on an activity during a specific time period.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Adaptive Approach.

A

A development approach in which the requirements are subject to a high level of uncertainty and volatility and are likely to change throughout the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Affinity Diagram.

A

A diagram that shows large numbers of ideas classified into groups for review and analysis.
(Post it Notes)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Affinity Grouping.

A

The process of classifying items into similar categories or collections on the basis of their likeness.
(Post it Notes)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Agile.

A

A term used to describe a mindset of values and principles as set forth in the Agile Manifesto.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Alternatives Analysis.

A

A method used to evaluate identified options in order to select the options or approaches to use to perform the work of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Ambiguity.

A

A state of being unclear, having difficulty in identifying the cause of events, or having multiple options from which to choose.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Analogous Estimating.

A

A method for estimating the duration or cost of an activity or a project using historical data from a similar activity or project.
(Similar historical data)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Artifact.

A

A template, document, output, or project deliverable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Assumption.

A

A factor in the planning process that is considered to be true, real, or certain, without proof or demonstration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Assumption and Constraint Analysis.

A

An assessment that ensures assumptions and constraints are integrated into the project plans and documents, and that there is consistency among them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Assumption Log.

A

A project document used to record all assumptions and constraints throughout the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Authority.

A

The right to apply project resources, expend funds, make decisions, or give approvals.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Backlog.

A

An ordered list of work to be done.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Backlog Refinement.

A

Progressive elaboration of the content in the backlog and (re)prioritization of it to identify the work that can be accomplished in an upcoming iteration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Baseline.

A

The approved version of a work product, used as a basis for comparison to actual results.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Basis of Estimates.

A

Supporting documentation outlining the details used in establishing project estimates such as assumptions, constraints, level of detail, ranges, and confidence levels.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Benchmarking.

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Benefits Management Plan.

A

The documented explanation defining the processes for creating, maximizing, and sustaining the benefits provided by a project or program.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Bid Documents.

A

All documents used to solicit information, quotations, or proposals from prospective sellers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Bidder Conference.

A

The meetings with prospective sellers prior to the preparation of a bid or proposal to ensure all prospective vendors have a clear and common understanding of the procurement. Also known as contractor conferences, vendor conferences, or pre-bid conferences.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Budget.

A

The approved estimate for the project or any work breakdown structure (WBS) component or any schedule activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Budget at Completion (BAC).

A

The sum of all budgets established for the work to be performed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Burn Chart.

A

A graphical representation of the work remaining in a timebox or the work completed toward the release of a product or project deliverable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Business Case.

A

A value proposition for a proposed project that may include financial and nonfinancial benefits.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Business Model Canvas.

A

A one-page, visual summary that describes the value proposition, infrastructure, customers, and finances. These are often used in Lean Startup situations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Business Value.

A

The net quantifiable benefit derived from a business endeavor that may be tangible, intangible, or both.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

Cadence.

A

A rhythm of activities conducted throughout the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Cause-and-Effect Diagram.

A

A visual representation that helps trace an undesirable effect back to its root cause.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Change.

A

A modification to any formally controlled deliverable, project management plan component, or project document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Change Control.

A

A process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Change Control Board (CCB).

A

A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

Change Control Plan.

A

A component of the project management plan that establishes the change control board, documents the extent of its authority, and describes how the change control system will be implemented.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Change Control System.

A

A set of procedures that describes how modifications to the project deliverables and documentation are managed and controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

Change Log.

A

A comprehensive list of changes submitted during the project and their current status.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

Change Management.

A

A comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from a current state to a future state with intended business benefits.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

Change Request.

A

A formal proposal to modify a document, deliverable, or baseline.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

Check Sheet.

A

A tally sheet that can be used as a checklist when gathering data.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

Closing Process Group.

A

The process(es) performed to formally complete or close a project, phase, or contract.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

Communications Management Plan.

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

Complexity.

A

A characteristic of a program or project or its environment that is difficult to manage due to human behavior, system behavior, and ambiguity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

Confirmation Bias.

A

A type of cognitive bias that confirms preexisting beliefs or hypotheses.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

Conformance.

A

The degree to which the results meet the set quality requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

Constraint.

A

A limiting factor that affects the execution of a project, program, portfolio, or process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

Contingency.

A

An event or occurrence that could affect the execution of the project, which may be accounted for with a reserve.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

Contingency Reserve.

A

Time or money allocated in the schedule or cost baseline for known risks with active response strategies.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

Continuous Delivery.

A

The practice of delivering feature increments immediately to customers, often through the use of small batches of work and automation technology.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

Contract.

A

A mutually binding agreement that obligates the seller to provide the specified product, service, or result and obligates the buyer to pay for it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

Control.

A

The process of comparing actual performance with planned performance, analyzing variances, assessing trends to effect process improvements, evaluating possible alternatives, and recommending appropriate corrective action as needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

Control Chart.

A

A graphic display of process data over time and against established control limits, which has a centerline that assists in detecting a trend of plotted values toward either control limit.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

Cost Baseline.

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
55
Q

Cost-Benefit Analysis.

A

A financial analysis method used to determine the benefits provided by a project against its costs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
56
Q

Cost Management Plan.

A

A component of a project or program management plan that describes how costs will be planned, structured, and controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q

Cost of Quality (COQ).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
58
Q

Cost Performance Index (CPI).

A

A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
59
Q

Cost Plus Award Fee Contract (CPAF).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
60
Q

Cost Plus Fixed Fee Contract (CPFF).

A

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).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
61
Q

Cost Plus Incentive Fee Contract (CPIF).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
62
Q

Cost-Reimbursable Contract.

A

A type of contract involving payment to the seller for the seller’s actual costs, plus a fee typically representing the seller’s profit.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
63
Q

Cost Variance (CV).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
64
Q

Crashing.

A

A method used to shorten the schedule duration for the least incremental cost by adding resources.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
65
Q

Criteria.

A

Standards, rules, or tests on which a judgment or decision can be based or by which a product, service, result, or process can be evaluated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
66
Q

Critical Path.

A

The sequence of activities that represents the longest path through a project, which determines the shortest possible duration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
67
Q

Critical Path Method (CPM).

A

A method used to estimate the minimum project duration and determine the amount of schedule flexibility on the logical network paths within the schedule model.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
68
Q

Cumulative Flow Diagram (CFD).

A

A chart indicating features completed over time, features in other states of development, and those in the backlog.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
69
Q

Cycle Time.

A

The total elapsed time from the start of a particular activity or work item to its completion.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
70
Q

Cycle Time Chart.

A

A diagram that shows the average cycle time of the work items completed over time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
71
Q

Daily Standup.

A

A brief, daily collaboration meeting in which the team reviews progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
72
Q

Dashboard.

A

A set of charts and graphs showing progress or performance against important measures of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
73
Q

Data Gathering and Analysis Methods.

A

Methods used to collect, assess, and evaluate data and information to gain a deeper understanding of a situation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
74
Q

Decision Tree Analysis.

A

A diagramming and calculation method for evaluating the implications of a chain of multiple options in the presence of uncertainty.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
75
Q

Decomposition.

A

A method used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
76
Q

Definition of Done (DoD).

A

A checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
77
Q

Deliverable.

A

Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
78
Q

Delivery Performance Domain.

A

The performance domain that addresses activities and functions associated with delivering the scope and quality that the project was undertaken to achieve.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
79
Q

Development Approach.

A

A method used to create and evolve the product, service, or result during the project life cycle, such as a predictive, iterative, incremental, agile, or hybrid method.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
80
Q

Development Approach and Life Cycle Performance Domain.

A

The performance domain that addresses activities and functions associated with the development approach, cadence, and life cycle phases of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
81
Q

DevOps.

A

A collection of practices for creating a smooth flow of deliveries by improving collaboration between development and operations staff.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
82
Q

Digital Product.

A

A product or service that is delivered, used, and stored in an electronic format.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
83
Q

Discretionary Dependency.

A

A relationship that is based on best practices or project preferences.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
84
Q

Duration.

A

The total number of work periods required to complete an activity or work breakdown structure component, expressed in hours, days, or weeks. Contrast with effort.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
85
Q

Earned Value (EV).

A

The measure of work performed expressed in terms of the budget authorized for that work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
86
Q

Earned Value Analysis (EVA).

A

An analysis method that uses a set of measures associated with scope, schedule, and cost to determine the cost and schedule performance of a project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
87
Q

Effort.

A

The number of labor units required to complete a schedule activity or work breakdown structure component, often expressed in hours, days, or weeks. Contrast with duration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
88
Q

Emotional Intelligence.

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
89
Q

Enterprise Environmental Factors (EEF).

A

Conditions, not under the immediate control of the team, that influence, constrain, or direct the project, program, or portfolio.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
90
Q

Epic.

A

A large, related body of work intended to hierarchically organize a set of requirements and deliver specific business outcomes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
91
Q

Estimate.

A

A quantitative assessment of the likely amount or outcome of a variable, such as project costs, resources, effort, or durations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
92
Q

Estimate at Completion (EAC).

A

The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
93
Q

Estimate to Complete (ETC).

A

The expected cost to finish all the remaining project work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
94
Q

Estimating Methods.

A

Methods used to develop an approximation of work, time, or cost on a project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
95
Q

Executing Process Group.

A

Those processes performed to complete the work defined in the project management plan to satisfy the project requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
96
Q

Expected Monetary Value (EMV).

A

The estimated value of an outcome expressed in monetary terms.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
97
Q

Explicit Knowledge.

A

Knowledge that can be codified using symbols such as words, numbers, and pictures.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
98
Q

External Dependency.

A

A relationship between project activities and non-project activities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
99
Q

Fast Tracking.

A

A schedule compression method in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
100
Q

Feature.

A

A set of related requirements or functionalities that provides value to an organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
101
Q

Firm Fixed Price Contract (FFP).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
102
Q

Fixed Duration.

A

A type of activity where the length of time required to complete the activity remains constant regardless of the number of people or resources assigned to the activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
103
Q

Fixed-Price Contract.

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
104
Q

Fixed Price Incentive Fee Contract (FPIF).

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
105
Q

Fixed Price with Economic Price Adjustment Contract (FPEPA).

A

A fixed-price contract, but with a special provision allowing for predefined final adjustments to the contract price due to changed conditions, such as inflation changes, or cost increases (or decreases) for specific commodities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
106
Q

Flow.

A

The measure of how efficiently work moves through a given process or framework.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
107
Q

Flowchart.

A

The depiction in a diagram format of the inputs, process actions, and outputs of one or more processes within a system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
108
Q

Forecast.

A

An estimate or prediction of conditions and events in the project’s future based on information and knowledge available at the time of the forecast.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
109
Q

Function Point.

A

An estimate of the amount of business functionality in an information system, used to calculate the functional size measurement of a software system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
110
Q

Gantt Chart.

A

A bar chart of schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
111
Q

Governance.

A

The framework for directing and enabling an organization through its established policies, practices, and other relevant documentation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
112
Q

Grade.

A

A category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
113
Q

Hierarchy Chart.

A

A chart that begins with high-level information that is progressively decomposed into lower levels of detail.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
114
Q

Histogram.

A

A bar chart that shows the graphical representation of numerical data.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
115
Q

Hybrid Approach.

A

A combination of two or more agile and nonagile elements, having a nonagile end result.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
116
Q

Impact Mapping.

A

A strategic planning method that serves as a visual roadmap for the organization during product development.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
117
Q

Impediment (Blocker).

A

An obstacle that prevents the team from achieving its objectives as a blocker.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
118
Q

Incremental Approach.

A

An adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
119
Q

Indefinite Delivery Indefinite Quantity (IDIQ).

A

A contract that provides for an indefinite quantity of goods or services, with a stated lower and upper limit, within a fixed time period.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
120
Q

Influence Diagram.

A

A graphical representation of situations showing causal influences, time ordering of events, and other relationships among variables and outcomes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
121
Q

Information Radiator.

A

A visible, physical display that provides information to the rest of the organization, enabling timely knowledge sharing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
122
Q

Initiating Process Group.

A

Those processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
123
Q

Internal Dependency.

A

A relationship between two or more project activities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
124
Q

Interpersonal Skills.

A

Skills used to establish and maintain relationships with other people.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
125
Q

Issue.

A

A current condition or situation that may have an impact on the project objectives.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
126
Q

Issue Log.

A

A project document where information about issues is recorded and monitored.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
127
Q

Iteration.

A

A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is performed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
128
Q

Iteration Plan.

A

A detailed plan for the current iteration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
129
Q

Iteration Planning.

A

A meeting to clarify the details of the backlog items, acceptance criteria, and work effort required to meet an upcoming iteration commitment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
130
Q

Iteration Review.

A

A meeting held at the end of an iteration to demonstrate the work that was accomplished during the iteration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
131
Q

Iterative Approach.

A

A development approach that focuses on an initial, simplified implementation then progressively elaborates adding to the feature set until the final deliverable is complete.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
132
Q

Kanban Board.

A

A visualization tool that shows work in progress to help identify bottlenecks and overcommitments, thereby allowing the team to optimize the workflow.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
133
Q

Kickoff Meeting.

A

A gathering of team members and other key stakeholders at the outset of a project to formally set expectations, gain a common understanding, and commence work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
134
Q

Knowledge.

A

A mixture of experience, values and beliefs, contextual information, intuition, and insight that people use to make sense of new experiences and information.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
135
Q

Lag.

A

The amount of time whereby a successor activity will be delayed with respect to a predecessor activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
136
Q

Last Responsible Moment.

A

The concept of deferring a decision to allow the team to consider multiple options until the cost of further delay would exceed the benefit.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
137
Q

Lead.

A

The amount of time whereby a successor activity can be advanced with respect to a predecessor activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
138
Q

Lead Time.

A

The time between a customer request and the actual delivery.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
139
Q

Lead Time Chart.

A

A diagram showing the trend over time of the average lead time of the items completed in work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
140
Q

Lean Startup Canvas.

A

A one-page template designed to communicate a business plan with key stakeholders in an efficient and effective manner.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
141
Q

Lessons Learned.

A

The knowledge gained during a project, which shows how project events were addressed or should be addressed in the future, for the purpose of improving future performance.

142
Q

Lessons Learned Register.

A

A project document used to record knowledge gained during a project, phase, or iteration so that it can be used to improve future performance for the team and the organization.

143
Q

Life Cycle Assessment (LCA).

A

A tool used to evaluate the total environmental impact of a product, process, or system.

144
Q

Log.

A

A document used to record and describe or denote selected items identified during execution of a process or activity. Usually used with a modifier, such as issue, change, or assumption.

145
Q

Make-or-Buy Analysis.

A

The process of gathering and organizing data about product requirements and analyzing them against available alternatives including the purchase or internal manufacture of the product.

146
Q

Management Reserve.

A

An amount of the project budget or project schedule held outside of the performance measurement baseline for management control purposes that is reserved for unforeseen work that is within the project scope.

147
Q

Mandatory Dependency.

A

A relationship that is contractually required or inherent in the nature of the work.

148
Q

Measurement Performance Domain.

A

The performance domain that addresses activities and functions associated with assessing project performance and taking appropriate actions to maintain acceptable performance.

149
Q

Measures of Performance.

A

Measures that characterize physical or functional attributes relating to system operation.

150
Q

Method.

A

A means for achieving an outcome, output, result, or project deliverable.

151
Q

Methodology.

A

A system of practices, techniques, procedures, and rules used by those who work in a discipline.

152
Q

Metric.

A

A description of a project or product attribute and how to measure it.

153
Q

Milestone.

A

A significant point or event in a project, program, or portfolio.

154
Q

Milestone Schedule.

A

A type of schedule that presents milestones with planned dates.

155
Q

Minimum Viable Product (MVP).

A

A concept used to define the scope of the first release of a solution to customers by identifying the fewest number of features or requirements that would deliver value.

156
Q

Modeling.

A

Creating simplified representations of systems, solutions, or deliverables, such as prototypes, diagrams, or storyboards.

157
Q

Monitor.

A

Collect project performance data, produce performance measures, and report and disseminate performance information.

158
Q

Monitoring and Controlling Process Group.

A

Those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate corresponding changes.

159
Q

Monte Carlo Simulation.

A

A method of identifying the potential impacts of risk and uncertainty using multiple iterations of a computer model to develop a probability distribution of a range of outcomes that could result from a decision or course of action.

160
Q

Mood Chart.

A

A visualization chart for tracking moods or reactions to identify areas for improvement.

161
Q

Multipoint Estimating.

A

A method used to estimate cost or duration by applying an average or weighted average of optimistic, pessimistic, and most likely estimates when there is uncertainty with the individual activity estimates.

162
Q

Net Promoter Score®.

A

An index that measures the willingness of customers to recommend an organization’s products or services to others.

163
Q

Network Path.

A

A sequence of activities connected by logical relationships in a project schedule network diagram.

164
Q

Objective.

A

Something toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed.

165
Q

Opportunity.

A

A risk that would have a positive effect on one or more project objectives.

166
Q

Organizational Breakdown Structure (OBS).

A

A hierarchical representation of the project organization, which illustrates the relationship between project activities and the organizational units that will perform those activities.

167
Q

Organizational Process Assets (OPA).

A

Plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization.

168
Q

Osmotic Communication.

A

Means of receiving information without direct communication by overhearing and through nonverbal cues.

169
Q

Outcome.

A

An end result or consequence of a process or project.

170
Q

Parametric Estimating.

A

An estimating method in which an algorithm is used to calculate cost or duration based on historical data and project parameters.

171
Q

Performance Measurement Baseline (PMB).

A

Integrated scope, schedule, and cost baselines used for comparison to manage, measure, and control project execution.

172
Q

Phase Gate.

A

A review at the end of a phase in which a decision is made to continue to the next phase, to continue with modification, or to end a project or program.

173
Q

Plan.

A

A proposed means of accomplishing something.

174
Q

Planned Value (PV).

A

The authorized budget assigned to scheduled work.

175
Q

Planning Performance Domain.

A

The performance domain that addresses activities and functions associated with the initial, ongoing, and evolving organization and coordination necessary for delivering project deliverables and results.

176
Q

Planning Process Group.

A

Those processes required to establish the scope of the project, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve.

177
Q

Portfolio.

A

Projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives.

178
Q

Portfolio Management.

A

The centralized management of one or more portfolios to achieve strategic objectives.

179
Q

Precision.

A

Within the quality management system, precision is an assessment of exactness.

180
Q

Predictive Approach.

A

A development approach in which the project scope, time, and cost are determined in the early phases of the life cycle.

181
Q

Prioritization Matrix.

A

A scatter diagram that plots effort against value so as to classify items by priority.

182
Q

Prioritization Schema.

A

Methods used to prioritize portfolio, program, or project components, as well as requirements, risks, features, or other product information.

183
Q

Probabilistic Estimating.

A

A method used to develop a range of estimates along with the associated probabilities within that range.

184
Q

Probability and Impact Matrix.

A

A grid for mapping the probability of occurrence of each risk and its impact on project objectives if that risk occurs.

185
Q

Procurement Management Plan.

A

A component of the project or program management plan that describes how a project team will acquire goods and services from outside of the performing organization.

186
Q

Product.

A

An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item.

187
Q

Product Breakdown Structure.

A

A hierarchical structure reflecting a product’s components and deliverables.

188
Q

Product Life Cycle.

A

A series of phases that represent the evolution of a product, from concept through delivery, growth, maturity, and to retirement.

189
Q

Product Management.

A

The integration of people, data, processes, and business systems to create, maintain, and evolve a product or service throughout its life cycle.

190
Q

Product Owner.

A

A person responsible for maximizing the value of the product and accountable for the end product.

191
Q

Product Scope.

A

The features and functions that characterize a product, service, or result.

192
Q

Program.

A

Related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually.

193
Q

Program Management.

A

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.

194
Q

Progressive Elaboration.

A

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.

195
Q

Project.

A

A temporary endeavor undertaken to create a unique product, service, or result.

196
Q

Project Brief.

A

A calendar that identifies working days and shifts that are ava ilable for scheduled activities. A high-level overview of the goals, deliverables, and processes for the project.

197
Q

Project Calendar.

A

A calendar that identifies working days and shifts that are ava ilable for scheduled activities.

198
Q

Project Charter.

A

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.

199
Q

Project Governance.

A

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.

200
Q

Project Lead.

A

A person who helps the project team to achieve the project objectives, typically by orchestrating the work of the project. See also project manager.

201
Q

Project Life Cycle.

A

The series of phases that a project passes through from its start to its completion.

202
Q

Project Management.

A

The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.

203
Q

Project Management Body of Knowledge (PMBOK).

A

A term that describes the knowledge within the profession of project management.

204
Q

Project Management Office (PMO).

A

A management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques.

205
Q

Project Management Plan.

A

The document that describes how the project will be executed, monitored and controlled, and closed.

206
Q

Project Management Process Group.

A

A logical grouping of project management inputs, tools and techniques, and outputs. The Project Management Process Groups include Initiating processes, Planning processes, Executing processes, Monitoring and Controlling processes, and Closing processes.

207
Q

Project Management Team.

A

The members of the project team who are directly involved in project management activities.

208
Q

Project Manager.

A

The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives. See also project lead.

209
Q

Project Phase.

A

A collection of logically related project activities that culminates in the completion of one or more deliverables.

210
Q

Project Review.

A

An event at the end of a phase or project to assess the status, evaluate the value delivered, and determine if the project is ready to move to the next phase or transition to operations.

211
Q

Project Schedule.

A

An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources.

212
Q

Project Schedule Network Diagram.

A

A graphical representation of the logical relationships among the project schedule activities.

213
Q

Project Scope.

A

The work performed to deliver a product, service, or result with the specified features and functions.

214
Q

Project Scope Statement.

A

The description of the project scope, major deliverables, and exclusions.

215
Q

Project Team.

A

A set of individuals performing the work of the project to achieve its objectives.

216
Q

Project Vision Statement.

A

A concise, high-level description of the project that states the purpose and inspires the team to contribute to the project.

217
Q

Project Work Performance Domain.

A

The performance domain that addresses activities and functions associated with establishing project processes, managing physical resources, and fostering a learning environment.

218
Q

Prototype.

A

A working model used to obtain early feedback on the expected product before actually building it.

219
Q

Quality.

A

The degree to which a set of inherent characteristics fulfills requirements.

220
Q

Quality Management Plan.

A

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.

221
Q

Quality Metrics.

A

A description of a project or product attribute and how to measure it.

222
Q

Quality Policy.

A

The basic principles that should govern the organization’s actions as it implements its system for quality management.

223
Q

Quality Report.

A

A project document that includes quality management issues, recommendations for corrective actions, and a summary of findings from quality control activities and may include recommendations for process, project, and product improvements.

224
Q

Register.

A

A written record of regular entries for evolving aspects of a project, such as risks, stakeholders, or defects.

225
Q

Regression Analysis.

A

An analytical method where a series of input variables are examined in relation to their corresponding output results in order to develop a mathematical or statistical relationship.

226
Q

Regulations.

A

Requirements imposed by a governmental body. These requirements can establish product, process, or service characteristics, including applicable administrative provisions that have government-mandated compliance.

227
Q

Relative Estimating.

A

A method for creating estimates that are derived from performing a comparison against a similar body of work, taking effort, complexity, and uncertainty into consideration.

228
Q

Release.

A

One or more components of one or more products, which are intended to be put into production at the same time.

229
Q

Release Plan.

A

The plan that sets expectations for the dates, features, and/or outcomes expected to be delivered over the course of multiple iterations.

230
Q

Release Planning.

A

The process of identifying a high-level plan for releasing or transitioning a product, deliverable, or increment of value A formal record or summary of information.

231
Q

Report.

A

A formal record or summary of information..

232
Q

Requirement.

A

A condition or capability that is necessary to be present in a product, service, or result to satisfy a business need.

233
Q

Requirements Documentation.

A

A record of product requirements and other product information, along with whatever is recorded to manage it.

234
Q

Requirements Management Plan.

A

A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed.

235
Q

Requirements Traceability Matrix.

A

A grid that links product requirements from their origin to the deliverables that satisfy them.

236
Q

Reserve.

A

A grid that links product requirements from their origin to the deliverables that satisfy them. A grid that links product requirements from their origin to the deliverables that satisfy them.

237
Q

Reserve Analysis.

A

A method used to evaluate the amount of risk on the project and the amount of schedule and budget reserve to determine whether the reserve is sufficient for the remaining risk.

238
Q

Resource Breakdown Structure.

A

A hierarchical representation of resources by category and type.

239
Q

Resource Management Plan.

A

A component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled.

240
Q

Responsibility.

A

An assignment that can be delegated within a project management plan such that the assigned resource incurs a duty to perform the requirements of the assignment.

241
Q

Responsibility Assignment Matrix (RAM).

A

A grid that shows the project resources assigned to each work package.

242
Q

Result.

A

An output from performing project management processes and activities. See also deliverable.

243
Q

Retrospective.

A

A regularly occurring workshop in which participants explore their work and results in order to improve both the process and product.

244
Q

Rework.

A

Action taken to bring a defective or nonconforming component into compliance with requirements or specifications.

245
Q

Risk.

A

An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives and not take any action unless the risk occurs.

246
Q

Risk Acceptance.

A

A risk response strategy whereby the project team decides to acknowledge the risk.

247
Q

Risk-Adjusted Backlog.

A

A backlog that includes product work and actions to address threats and opportunities.

248
Q

Risk Appetite.

A

The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward.

249
Q

Risk Avoidance.

A

A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact.

250
Q

Risk Breakdown Structure (RBS).

A

A hierarchical representation of potential sources of risks.

251
Q

Risk Enhancement.

A

A risk response strategy whereby the project team acts to increase the probability of occurrence or impact of an opportunity.

252
Q

Risk Escalation.

A

A risk response strategy whereby the team acknowledges that a risk is outside of its sphere of influence and shifts the ownership of the risk to a higher level of the organization where it is more effectively managed.

253
Q

Risk Exploiting.

A

A risk response strategy whereby the project team acts to ensure that an opportunity occurs.

254
Q

Risk Exposure.

A

An aggregate measure of the potential impact of all risks at any given point in time in a project, program, or portfolio.

255
Q

Risk Management Plan.

A

A component of the project, program, or portfolio management plan that describes how risk management activities will be structured and performed.

256
Q

Risk Mitigation.

A

A risk response strategy whereby the project team acts to decrease the probability of occurrence or impact of a threat.

257
Q

Risk Register.

A

A repository in which outputs of risk management processes are recorded.

258
Q

Risk Report.

A

A project document that summarizes information on individual project risks and the level of overall project risk.

259
Q

Risk Review.

A

The process of analyzing the status of existing risks and identifying new risks. May also be known as risk reassessment.

260
Q

Risk Sharing.

A

A risk response strategy whereby the project team allocates ownership of an opportunity to a third party who is best able to capture the benefit of that opportunity.

261
Q

Risk Threshold of the organization and stakeholders.

A

The measure of acceptable variation around an objective that reflects the risk appetite.

262
Q

Risk Transference.

A

A risk response strategy whereby the project team shifts the impact of a threat to a third party, together with ownership of the response.

263
Q

Roadmap.

A

A high-level time line that depicts such things as milestones, significant events, reviews, and decision points.

264
Q

Role.

A

A defined function to be performed by a project team member, such as testing, filing, inspecting, or coding.

265
Q

Rolling Wave Planning.

A

An iterative planning method in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level.

266
Q

Root Cause Analysis.

A

An analytical method used to determine the basic underlying reason that causes a variance or a defect or a risk.

267
Q

Scatter Diagram.

A

A graph that shows the relationship between two variables..

268
Q

Schedule Baseline.

A

The approved version of a schedule model that can be changed using formal change control procedures and is used as the basis for comparison to actual results.

269
Q

Schedule Compression.

A

A method used to shorten the schedule duration without reducing the project scope.

270
Q

Schedule Forecasts.

A

Estimates or predictions of conditions and events in the project’s future based on information and knowledge available at the time the schedule is calculated.

271
Q

Schedule Management Plan.

A

A component of the project or program management plan that establishes the criteria and the activities for developing, monitoring, and controlling the schedule.

272
Q

Schedule Model.

A

A representation of the plan for executing the project’s activities including durations, dependencies, and other planning information, used to produce a project schedule along with other scheduling artifacts.

273
Q

Schedule Performance Index (SPI).

A

A measure of schedule efficiency expressed as the ratio of earned value to planned value.

274
Q

Schedule Variance (SV).

A

A measure of schedule performance expressed as the difference between the earned value and the planned value.

275
Q

Scope.

A

The sum of the products, services, and results to be provided as a project. See also project scope and product scope.

276
Q

Scope Baseline.

A

The approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary that can be changed using formal change control procedures and is used as the basis for comparison to actual results.

277
Q

Scope Creep.

A

The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.

278
Q

Scope Management Plan.

A

A component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.

279
Q

S-Curve.

A

A graph that displays cumulative costs over a specified period of time.

280
Q

Self-Organizing Team.

A

A cross-functional team in which people assume leadership as needed to achieve the team’s objectives.

281
Q

Sensitivity Analysis.

A

An analysis method to determine which individual project risks or other sources of uncertainty have the most potential impact on project outcomes by correlating variations in project outcomes with variations in elements of a quantitative risk analysis model.

282
Q

Servant Leadership.

A

The practice of leading the team by focusing on understanding and addressing the needs and development of team members in order to enable the highest possible team performance.

283
Q

Simulation.

A

An analytical method that models the combined effect of uncertainties to evaluate their potential impact on objectives.

284
Q

Single-Point Estimating.

A

An estimating method that involves using data to calculate a single value which reflects a best guess estimate.

285
Q

Specification.

A

A precise statement of the needs to be satisfied and the essential characteristics that are required.

286
Q

Sponsor.

A

A person or group who provides resources and support for the project, program, or portfolio and is accountable for enabling success.

287
Q

Sprint.

A

A short time interval within a project during which a usable and potentially releasable increment of the product is created. See also iteration.

288
Q

Stakeholder.

A

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.

289
Q

Stakeholder Analysis.

A

A method of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project.

290
Q

Stakeholder Engagement Assessment Matrix.

A

A matrix that compares current and desired stakeholder engagement levels.

291
Q

Stakeholder Engagement Plan.

A

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.

292
Q

Stakeholder Performance Domain.

A

The performance domain that addresses activities and functions associated with stakeholders.

293
Q

Stakeholder Register.

A

A project document that includes information about project stakeholders including an assessment and classification of project stakeholders.

294
Q

Standard.

A

A document established by an authority, custom, or general consent as a model or example.

295
Q

Statement of Work (SOW).

A

A narrative description of products, services, or results to be delivered by the project.

296
Q

Status Meeting.

A

A regularly scheduled meeting to exchange and analyze information about the current progress of the project and its performance.

297
Q

Status Report.

A

A report on the current status of the project.

298
Q

Steering Committee.

A

An advisory body of senior stakeholders who provide direction and support for the project team and make decisions outside the project team’s authority.

299
Q

Story Map.

A

A visual model of all the features and functionality desired for a given product, created to give the team a holistic view of what they are building and why.

300
Q

Story Point.

A

A unit used to estimate the relative level of effort needed to implement a user story.

301
Q

Strategic Plan.

A

A high-level document that explains an organization’s vision and mission plus the approach that will be adopted to achieve this mission and vision, including the specific goals and objectives to be achieved during the period covered by the document.

302
Q

Strategy Artifacts.

A

Documents created prior to or at the start of the project that address strategic, business, or high-level information about the project.

303
Q

Swarm.

A

A method in which multiple team members focus collectively on resolving a specific problem or task.

304
Q

SWOT Analysis.

A

Analysis of strengths, weaknesses, opportunities, and threats of an organization, project, or option.

305
Q

Tacit Knowledge.

A

Personal knowledge that can be difficult to articulate and share such as beliefs, experience, and insights.

306
Q

Tailoring.

A

The deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand.

307
Q

Task Board.

A

A visual representation of the progress of the planned work that allows everyone to see the status of the tasks.

308
Q

Team Charter.

A

A document that records the team values, agreements, and operating guidelines, as well as establishes clear expectations regarding acceptable behavior by project team members.

309
Q

Team Performance Domain.

A

The performance domain that addresses activities and functions associated with the people who are responsible for producing project deliverables that realize business outcomes.

310
Q

Technical Performance Measures.

A

Quantifiable measures of technical performance that are used to ensure system components meet the technical requirements.

311
Q

Template.

A

A partially complete document in a predefined format that provides a defined structure for collecting, organizing, and presenting information and data.

312
Q

Test Plan.

A

A document describing deliverables that will be tested, tests that will be conducted, and the processes that will be used in testing.

313
Q

Threat.

A

A risk that would have a negative effect on one or more project objectives.

314
Q

Threshold.

A

A predetermined value of a measurable project variable that represents a limit that requires action to be taken if it is reached.

315
Q

Throughput.

A

The number of items passing through a process.

316
Q

Throughput Chart.

A

A diagram that shows the accepted deliverables over time.

317
Q

Time and Materials Contract (T&M).

A

A type of contract that is a hybrid contractual arrangement containing aspects of both cost-reimbursable and fixed-price contracts.

318
Q

Timebox.

A

A short, fixed period of time in which work is to be completed.

319
Q

Tolerance.

A

The quantified description of acceptable variation for a quality requirement.

320
Q

Trend Analysis.

A

An analytical method that uses mathematical models to forecast future outcomes based on historical results.

321
Q

Triple Bottom Line.

A

A framework for considering the full cost of doing business by evaluating a company’s bottom line from the perspective of profit, people, and the planet.

322
Q

Uncertainty.

A

A lack of understanding and awareness of issues, events, path to follow, or solutions to pursue.

323
Q

Uncertainty Domain.

A

The performance domain that addresses activities and functions associated with risk and uncertainty.

324
Q

Use Case.

A

An artifact for describing and exploring how a user interacts with a system to achieve a specific goal.

325
Q

User Story.

A

A brief description of an outcome for a specific user, which is a promise for a conversation to clarify details.

326
Q

Validation.

A

The assurance that a product, service, or result meets the needs of the customer and other identified stakeholders. See also verification.

327
Q

Value.

A

The worth, importance, or usefulness of something.

328
Q

Value Delivery Office (VDO).

A

A project delivery support structure that focuses on coaching teams; building agile skills and capabilities throughout the organization; and mentoring sponsors and product owners to be more effective in those roles.

329
Q

Value Delivery System.

A

A collection of strategic business activities aimed at building, sustaining, and/or advancing an organization.

330
Q

Value Proposition.

A

The value of a product or service that an organization communicates to its customers.

331
Q

Value Stream Map.

A

A display of the critical steps in a process and the time taken in each step used to identify waste.

332
Q

Value Stream Mapping.

A

A lean enterprise method used to document, analyze, and improve the flow of information or materials required to produce a product or service for a customer.

333
Q

Vanity Metric.

A

A measure that appears to show some result but does not provide useful information for making decisions.

334
Q

Variance.

A

A quantifiable deviation, departure, or divergence away from a known baseline or expected value.

335
Q

Variance Analysis.

A

A method for determining the cause and degree of difference between the baseline and actual performance.

336
Q

Variance at Completion (VAC).

A

A projection of the amount of budget deficit or surplus, expressed as the difference between the budget at completion and the estimate at completion.

337
Q

Velocity.

A

A measure of a team’s productivity rate at which the deliverables are produced, validated, and accepted within a predefined interval.

338
Q

Velocity Chart.

A

A chart that tracks the rate at which the deliverables are produced, validated, and accepted within a predefined interval.

339
Q

Verification.

A

The evaluation of whether or not a product, service, or result complies with a regulation, requirement, specification, or imposed condition. See also validation.

340
Q

Virtual Team.

A

A group of people with a shared goal who work in different locations and who engage with each other primarily through phone and other electronic communications.

341
Q

Vision Statement.

A

A summarized, high-level description about the expectations for a product such as target market, users, major benefits, and what differentiates the product from others in the market.

342
Q

Visual Data and Information.

A

Artifacts that organize and present data and information in a visual format, such as charts, graphs, matrices, and diagrams.

343
Q

Voice of the Customer.

A

A planning method used to provide products, services, and results that truly reflect customer requirements by translating those customer requirements into the appropriate technical requirements for each phase of project or product development.

344
Q

Volatility.

A

The possibility for rapid and unpredictable change.

345
Q

Waste.

A

Activities that consume resources and/or time without adding value.

346
Q

WBS Dictionary.

A

A document that provides detailed deliverable, activity, and scheduling information about each component in the work breakdown structure.

347
Q

What-If-Scenario Analysis.

A

The process of evaluating scenarios in order to predict their effect on project objectives.

348
Q

Wideband Delphi.

A

An estimating method in which subject matter experts go through multiple rounds of producing estimates individually, with a team discussion after each round, until a consensus is achieved.

349
Q

Work Breakdown Structure (WBS).

A

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
Q

Work Package.

A

The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.