PMP Terms Flashcards

1
Q

5 Whys Method

A

An effective tool for root cause analysis in which the question “why?” is asked of a problem in succession until the root cause is found.
Developed by Sakichi Toyoda, Lean philosophy.

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

80/20 Rule

A

A general guideline with many applications; in terms of controlling processes, it contends that a relatively large number of problems or defects, typically 80%, are commonly due to a relatively small number of causes, typically 20%. (see also Pareto Chart).

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

A/B Testing

A

A marketing approach used to determine user preferences by showing different sets of users’ similar services - an ‘Alpha’ and a ‘Beta’ version - with one independent variable.

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

Accept

A

A strategy for managing negative risks or opportunities that involves acknowledging risk and not taking any action until the risk occurs.

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

Accepted Deliverables

A

Deliverables that meet the acceptance criteria and have been formally signed off and approved by the customer or sponsor as part of the scope validation process.

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

Active Listening

A

A communication technique that involves acknowledging the speaker’s message and the recipient clarifying the message to confirm that what was heard matches the message that the sender intended.

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

Activity

A

A distinct portion of work, scheduled with a beginning and an end, that must be performed to complete work on the project. Also known as a schedule activity. See also “Task”

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

Activity Attributes

A

Multiple attributes associated with each activity that can be included within the activity list.

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

Activity Cost Estimates

A

Each task is assigned a budget, and the aggregate of these estimates results in the project budget. Activity cost estimates include labor, materials, equipment, and fixed cost items like contractors, services, facilities, financing costs, etc. This information can be presented in a detailed or summarized form.

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

Activity Dependency

A

A logical relationship that exists between two project activities. The relationship indicates whether the start of an activity is contingent upon an event or input from outside the activity.

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

Activity Duration Estimates

A

The quantitative assessments of the likely number of time periods that are required to complete an activity.

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

Activity on Arrow or Activity on Node

A

A graphical diagram on which schedule activities are represented by nodes (rectangular boxes) and their dependencies are depicted by arrows.

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

Activity Resource Estimates

A

Material and human resources that are needed to complete an activity; often expressed by a probability or range.

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

Activity Resource Requirements

A

The resources (physical, human, and organizational) required to complete the activities in the activity list

17
Q

Actual Cost (AC)

A

Earned Value Management term for the realized cost incurred for the work performed on an activity during a specific time.

18
Q

Adaptive

A

A type of project life cycle or methodology that values responding to change over following a set plan. Adaptive methodologies seek solutions that deliver maximum value to the customer.

19
Q

Administrative Closure

A

Involves verifying and documenting project results to formalize project or phase completion.

20
Q

Affinity Diagram

A

A technique that allows large numbers of ideas to be classified into groups for review and analysis.

21
Q

Affinity Estimating

A

Technique designed to rapidly estimate large stories (epics or features) in the backlog. For example: Fibonacci sequence, T-shirt sizing, coffee cup sizes.

22
Q

Agile

A

Refers to a type of project lifecycle (also known as adaptive) or methodology based on a set of values and principles and characterized by an openness towards change for the promotion of value or benefits delivery for the customer.

Also refers to a kind of project or project team that uses a non-binding expectation of what future iteration increments/sprints/iterations (outcomes and/or deliverables) will be combined int releases to the customer.

23
Q

Agile Coach

A

A process role on a project team that helps organizations achieve true agility by coaching teams across the enterprise on how to apply agile practices and choose their best way of working. (Scrum master).

24
Q

Agile Estimating

A

An approach that assists with planning a project appropriately from the beginning to ensure the team can focus on the quality of each deliverable.

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

26
Q

Agile Manifesto

A

2001: 17 SW developers, Snowbird Utah - discuss lightweight software development.
Four core values:
Individuals and Interactions over Processes and Tools
Working SW over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Responding to Change over Following a Plan

27
Q

Agile Modeling

A

A representation of the workflow of a process or system that the team can review before it is implemented in code.

28
Q

Agile Principles

A

A set of 12 Guidelines that support the Agile Manifesto and which practitioners and teams should internalize and act upon.

29
Q

Agile Release Planning

A

A process in which a team determines 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.

30
Q

Agile Space

A

Team space that encourages colocation, collaboration, communication, transparency, and visibility.

31
Q

Agreements

A

Any documents or communication that defines the initial intentions of a project. (contracts, MOUs, SLAs, etc.)

32
Q

Allowable Costs

A

Costs that are allowed under the terms of the contract. Becomes relevant under cost-reimbursable contracts in which the buyer reimburses the seller’s allowable costs.

33
Q

Analogous Estimating

A

A technique for estimating the duration of cost of an activity on a project using historical data from a similar activity or project. (Top Down Estimating)

34
Q

Analytical Techniques

A

Logical approach that looks at the relationship between outcomes and the factors that can influence them.

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

36
Q

Artifact

A

Any project management processes, inputs, tools,techniques, outputs, EEFs, and OPAs that the project management team uses on their specific project. They are subject to configuration managemeent and are maintained and archived by the team.