Pmbok 07

Front 1

Project Stakeholder

Back 1

Begins with P: See stakeholder.

Front 2

Project Summary Work Breakdown Structure (PSWBS) [Tool]

Back 2

Begins with P: A work breakdown structure for the project that is only developed down to the subproject level of detail within some legs of the WBS, and where the detail of those subprojects are provided by use of contract work breakdown structures.

Front 3

Project Team

Back 3

Begins with P: All the project team members, including the project management team, the project manager and, for some projects, the project sponsor.

Front 4

Project Team Directory

Back 4

Begins with P: A documented list of project team members, their project roles and communication information.

Front 5

Project Team Members

Back 5

Begins with P: The persons who report either directly or indirectly to the project manager, and who are responsible for perforating project work as a regular part of their assigned duties.

Front 6

Project Time Management [Knowledge Area]

Back 6

Begins with P: See Appendix F. Project Work. See work.

Front 7

Projectized Organization

Back 7

Begins with P: Any organizational structure in which the project manager has full authority to assign priorities, apply resources, and direct the work of persons assigned to the project.

Front 8

Qualitative Risk Analysis [Process]

Back 8

Begins with Q: The process of prioritizing risks for subsequent further analysis or action by assessing and combining their probability of occurrence and impact.

Front 9

Quality

Back 9

Begins with Q: The degree to which a set of inherent characteristics fulfills requirements.

Front 10

Quality Management Plan [Outputllnput]

Back 10

Begins with Q: The quality management plan describes how the project management team will implement the performing organization's quality policy. The quality management plan is a component or a subsidiary plan of the project management plan. The quality management plan may be formal or informal, highly detailed, or broadly framed, based on the requirements of the project.

Front 11

Quality Planning [Process]

Back 11

Begins with Q: The process of identifying which quality standards are relevant to the project and determining how to satisfy them.

Front 12

Quantitative Risk Analysis [Process]

Back 12

Begins with Q: The process of numerically analyzing the effect on overall project objectives of identified risks.

Front 13

Regulation

Back 13

Begins with R: Requirements imposed by a governmental body. These requirements can establish product, process or service characteristics

Front 14

Reliability

Back 14

Begins with R: The probability of a product performing its intended function under specific conditions for a given period of time

Front 15

Remaining Duration (RD)

Back 15

Begins with R: The time in calendar units, between the data date of the project schedule and the finish date of a schedule activity that has an actual start date. This represents the time needed to complete a schedule activity where the work is in progress.

Front 16

Request for Information

Back 16

Begins with R: A type of procurement document whereby the buyer requests a potential seller to provide various pieces of information related to a product or service or seller capability.

Front 17

Request for Proposal (REP)

Back 17

Begins with R: A type of procurement document used to request proposals from prospective sellers of products or services. In some application areas, it may have a narrower or more specific meaning.

Front 18

Request for Quotation (RFQ)

Back 18

Begins with R: A type of procurement document used to request price quotations from prospective sellers of common or standard products or services. Sometimes used in place of request for proposal and in some application areas, it may have a narrower or more specific meaning.

Front 19

Request Seller Responses [Process]

Back 19

Begins with R: The process of obtaining information, quotations, bids, offers, or proposals, as appropriate.

Front 20

Requested Change [Output/Input]

Back 20

Begins with R: A formally documented change request that is submitted for approval to the integrated change control process. Contrast with approved change request.

Front 21

Requirement

Back 21

Begins with R: A condition or capability that must be met or possessed by a sti.stem, product, service, result, or component to satisfy a contract, standard, specification, or other

Front 22

formally imposed documents

Back 22

Begins with f: Requirements include the quantified and documented needs, wants, and expectations of the sponsor, customer, and other stakeholders.

Front 23

Reserve

Back 23

Begins with R: A provision in the project management pkm to mitigate cost and/or schedule risk. Often used with a modifier (e.g., management reserve, contingency reserve) to provide further detail on what types of risk are meant to be mitigated. The specific meaning of the modified term varies by application area.

Front 24

Reserve Analysis [Technique]

Back 24

Begins with R: An analytical technique to determine the essential features and relationships of components in the project management plan to establish a reserve for the schedule duration. budget, estimated cost, or,ftmds for a project.

Front 25

Residual Risk

Back 25

Begins with R: A risk that remains after risk responses have been implemented.

Front 26

Resource

Back 26

Begins with R: Skilled human resources (specific disciplines either individually or in crews or teams), equipment, services, supplies, commodities, materiel, budgets, or funds.

Front 27

Resource Breakdown Structure (RBS)

Back 27

Begins with R: A hierarchical structure of resources by resource category and resource type used in resource leveling schedules and to develop resource-limited schedules, and which may be used to identify and analyze project human resource assignments.

Front 28

Resource Calendar

Back 28

Begins with R: A calendar of working days and nonworking days that determines those dates on which each specific resource is idle or can be active, Typically defines resource specific holidays and resource availability periods. See also project calendar.

Front 29

Resource-Constrained Schedule

Back 29

Begins with R: See resource-limited schedule.

Front 30

Resource Histogram

Back 30

Begins with R: A bar chart showing the amount of time that a resource is scheduled to work over a series of time periods. Resource availability may be depicted as a line for comparison purposes. Contrasting bars may show actual amounts of resource used as the project progresses.

Front 31

Resource Leveling [Technique]

Back 31

Begins with R: Any form of schedule network analysis in which scheduling decisions (start and finish dates) are driven by resource constraints (e.g., limited resource availability or difficult-to-manage changes in resource availability levels).

Front 32

Resource-Limited Schedule

Back 32

Begins with R: A project schedule whose schedule activity, scheduled start dates and scheduled finish dates reflect expected resource availability. A resource-limited schedule does not have any early or late start or finish dates. The resource-limited schedule total float is determined by calculating the difference between the critical path method late finish date` and the resource-limited scheduled finish date. Sometimes called resource-constrained schedule. See also resource leveling.

Front 33

Resource Planning

Back 33

Begins with R: See activity resource estimating.

Front 34

Responsibility Assignment Matrix (RAM) [Tool]

Back 34

Begins with R: A structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project's scope of work is assigned to a responsible person/team.

Front 35

Result

Back 35

Begins with R: An output from performing project management processes and activities. Results include outcomes (e.g., integrated systems, revised process, restructured organi_ation, tests, trained personnel, etc.) and documents (e.g., policies, plans, studies, procedures, specifications, reports, etc.). Contrast with product and service. See also deliverable.

Front 36

Retainage

Back 36

Begins with R: A portion of a contract payment that is withheld until contract completion to ensure full performance of the contract terms.

Front 37

Rework

Back 37

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

Front 38

Risk

Back 38

Begins with R: An uncertain event or condition that, if it occurs, has a positive or negative effect on a project's objectives. See also risk category and risk breakdown structure.

Front 39

Risk Acceptance [Technique]

Back 39

Begins with R: A risk response planning teclnniquue* that indicates that the project team has decided not to change the project management plan to deal with a risk. or is unable to identify any other suitable response strategy.

Front 40

Risk Avoidance [Technique]

Back 40

Begins with R: A risk response planning technique* for a threat that creates changes to the project management plan that are meant to either eliminate the risk or to protect the project objectives from its impact. Generally, risk avoidance involves relaxing the time, cost, scope, or quality objectives.

Front 41

Risk Breakdown Structure (RBS) [Tool]

Back 41

Begins with R: A hierarchically organized depiction of the identified project risks* arranged by risk category and subcategory that identifies the various areas and causes of potential risks. The risk breakdown structure is often tailored to specific project types.

Front 42

Risk Category

Back 42

Begins with R: A group of potential causes of risk. Risk causes may be grouped into categories such as technical, external, organizational, environmental. or project management. A category may include subcategories such as technical maturity, weather, or aggressive estimating. See also risk breakdown structure.

Front 43

Risk Database

Back 43

Begins with R: A repository that provides for collection, maintenance, and analysis of data gathered and used in the risk management processes.

Front 44

Risk Identification [Process]

Back 44

Begins with R: The process of determining which risks might affect the project and documenting their characteristics.

Front 45

Risk Management Plan [Output/Input]

Back 45

Begins with R: The document describing how project risk management will be structured and performed on the project. It is contained in or is a subsidiary plan of the project management plan. The risk management plan can be informal and broadly framed, or formal and highly detailed, based on the needs of the project. Information in the risk management plan varies by application area and project size. The risk management plan is different from the risk register that contains the list of project risks, the results of risk analysis, and the risk responses.

Front 46

Risk Management Planning [Process]

Back 46

Begins with R: The process of deciding how to approach, plan, and execute risk management activities for a project.

Front 47

Risk Mitigation [Technique]

Back 47

Begins with R: A risk response planning technique* associated with threats that seeks to reduce the probability of occurrence or impact of a risk to below an acceptable threshold.

Front 48

Risk Monitoring and Control [Process]

Back 48

Begins with R: The process of tracking identified risks, monitoring residual risks', identifying new risks, executing risk response plans, and evaluating their effectiveness throughout the project life cycle.

Front 49

Risk Register [Output/Input]

Back 49

Begins with R: The document containing the results of' the qualitative risk analysis, quantitative risk analysis, and risk response planning. The risk register details all identified risks, including description, category, cause, probability of occurring, impact(s) on objectives, proposed responses, owners, and current status. The risk register is a component of the project management plan.

Front 50

Risk Response Planning [Process]

Back 50

Begins with R: The process of developing options and actions to enhance opportunities and to reduce threats to project objectives.