Glossary - L-P Flashcards Preview

Project Management > Glossary - L-P > Flashcards

Flashcards in Glossary - L-P Deck (89)
Loading flashcards...
1
Q

Project

A

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

2
Q

Project Calendar

A

A calendar of working days or shifts that establishes those dates on which schedule activities are worked and nonworking days that determine those dates on which schedule activities are idle. Typically defines holidays, weekends, and shift hours. See also resource calendar.

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

4
Q

Project Communications Management

A

Project Communications Management includes the processes required to ensure timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information.

5
Q

Project Cost Management

A

Project Cost Management includes the processes involved in estimating, budgeting, and controlling costs so that the project can be completed within the approved budget.

6
Q

Project Human Resource Management

A

Project Human Resource Management includes the processes that organize and manage the project team.

7
Q

Project Initiation

A

Launching a process that can result in the authorization of a new project.

8
Q

Project Integration Management

A

Project Integration Management includes the processes and activities needed to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups.

9
Q

Project Life Cycle

A

A collection of generally sequential project phases whose name and number are determined by the control needs of the organization or organizations involved in the project. A life cycle can be documented with a methodology.

10
Q

Project Management

A

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

11
Q

Project Management Body of Knowledge

A

An inclusive term that describes the sum of knowledge within the profession of project management. As with other professions, such as law, medicine, and accounting, the body of knowledge rests with the practitioners and academics that apply and advance it. The complete project management body of knowledge includes proven traditional practices that are widely applied and innovative practices that are emerging in the profession. The body of knowledge includes both published and unpublished materials. This body of knowledge is constantly evolving. PMI’s PMBOJ

12
Q

Project Management Information System (PMIS)

A

An information system consisting of the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes. It is used to support all aspects of the project from initiating through closing, and can include both manual and automated systems.

13
Q

Project Management Knowledge Area

A

An identified area of project management defined by its knowledge requirements and described in terms of its component processes, practices, inputs, outputs, tools, and techniques.

14
Q

Project Management Office (PMO)

A

An organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain. The responsibilities of a PMO can range from providing project management support functions to actually being responsible for the direct management of a project.

15
Q

Project Management Plan

A

A formal, approved document that defines how the project is executed, monitored, and controlled. It may be a summary or detailed and may be composed of one or more subsidiary management plans and other planning documents.

16
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. Project Management Process Groups are not project phases.

17
Q

Project Management System

A

The aggregation of the processes, tools, techniques, methodologies, resources, and procedures to manage a project.

18
Q

Project Management Team

A

The members of the projectteam who are directly involved in project management activities. On some smaller projects, the project management team may include virtually all of the project team members.

19
Q

Project Manager (PM)

A

The person assigned by the performing organization to achieve the project objectives.

20
Q

Project Organization Chart

A

A document that graphically depicts the project team members and their interrelationships for a specific project.

21
Q

Project Phase

A

A collection of logically related project activities, usually culminating in the completion of a major deliverable. Project phases are mainly completed sequentially, but can overlap in some project situations. A project phase is a component of a project life cycle. A project phase is not a Project Management Process Group.

22
Q

Project Procurement Management

A

Project Procurement Management includes the processes to purchase or acquire the products, services, or results needed from outside the project team to perform the work.

23
Q

Project Quality Management

A

Project Quality Management includes the processes and activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project will satisfy the needs for which it was undertaken.

24
Q

Project Risk Management

A

Project Risk Management includes the processes concerned with conducting risk management planning, identification, analysis, responses, and monitoring and control on a project.

25
Q

Project Schedule

A

The planned dates for performing schedule activities and the planned dates for meeting schedule milestones.

26
Q

Project Schedule Network Diagram

A

Any schematic display of the logical relationships among the project schedule activities. Always drawn from left to right to reflect project work chronology.

27
Q

Project Scope

A

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

28
Q

Project Scope Management

A

Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.

29
Q

Project Scope Statement

A

The narrative description of the project scope, including major deliverables, project assumptions, project constraints, and a description of work, that provides a documented basis for making future project decisions and for confirming or developing a common understanding of project scope among the stakeholders.

30
Q

Project Team Directory

A

A documented list of project team members, their project roles, and communication information.

31
Q

Project Time Management

A

Project Time Management includes the processes required to manage the timely completion of a project.

32
Q

Projectized Organization

A

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.

33
Q

Parametric Estimating

A

An estimating technique that uses a statistical relationship between historical data and other variables (e.g., square footage in construction, lines of code in software development) to calculate an estimate for activity parameters, such as scope, cost, budget, and duration. An example for the cost parameter is multiplying the planned quantity of work to be performed by the historical cost per unit to obtain the estimated cost.

34
Q

Pareto Chart

A

A histogram, ordered by frequency of occurrence, that shows how many results were generated by each identified cause.

35
Q

Path Convergence

A

The merging or joining of parallel schedule network paths into the same node in a project schedule network diagram. Path convergence is characterized by a schedule activity with more than one predecessor activity.

36
Q

Path Divergence

A

Extending or generating parallel schedule network paths from the same node in a project schedule network diagram. Path divergence is characterized by a schedule activity with more than one successor activity.

37
Q

Percent Complete

A

An estimate, expressed as a percent, of the amount of work that has been completed on an activity or a work breakdown structure component.

38
Q

Perform Integrated Change Control

A

The process of reviewing all change requests, approving changes, and managing changes to the deliverables, organizational process assets, project documents, and project management plan.

39
Q

Performance Measurement Baseline

A

An approved integrated scope-schedule-cost plan for the project work against which project execution is compared to measure and manage performance. Technical and quality parameters may also be included.

40
Q

Performance Reports

A

Documents and presentations that provide organized and summarized work performance information, earned value management parameters and calculations, and analyses of project work progress and status.

41
Q

Performing Organization

A

The enterprise whose personnel are most directly involved in doing the work of the project.

42
Q

Perform Qualitative Risk Analysis

A

The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.

43
Q

Perform Quality Assurance

A

The process of auditing the quality requirements and the results from quality control measurements to ensure appropriate quality standards and operational definitions are used.

44
Q

Perform Quality Control

A

The process of monitoring and recording results of executing the quality activities to assess performance and recommend necessary changes.

45
Q

Perform Quantitative Risk Analysis

A

The process of numerically analyzing the effect of identified risks on overall project objectives.

46
Q

Phase

A

See project phase.

47
Q

Plan Communications

A

The process of determining project stakeholder information needs and defining a communication approach.

48
Q

Plan Procurements

A

The process of documenting project purchasing decisions, specifying the approach, and identifying potential sellers.

49
Q

Plan Quality

A

The process of identifying quality requirements and/or standards for the project and product, and documenting how the project will demonstrate compliance.

50
Q

Plan Risk Management

A

The process of defining how to conduct risk management activities for a project.

51
Q

Plan Risk Responses

A

The process of developing options and actions to enhance opportunities and to reduce threats to project objectives.

52
Q

Planned Value (PV)

A

The authorized budget assigned to the scheduled work to be accomplished for a schedule activity or work breakdown structure component. Also referred to as the budgeted cost of work scheduled (BeWS).

53
Q

Planning Package

A

A work breakdown structure component below the control account with known work content but without detailed schedule activities. See also control account.

54
Q

Planning Processes

A

Those processes performed to establish the total scope of the effort, define and refine the objectives, and develop the course of action required to attain those objectives.

55
Q

Near-Critical Activity

A

A schedule activity that has low total float. The concept of near-critical is equally applicable to a schedule activity or schedule network path. The limit below which total float is considered near critical is subject to expert judgment and varies from project to project.

56
Q

Network

A

See project schedule network diagram.

57
Q

Network Analysis

A

See schedule network analysis.

58
Q

Network Logic

A

The collection of schedule activity dependencies that makes up a project schedule network diagram.

59
Q

Network Path

A

Any continuous series of schedule activities connected with logical relationships in a project schedule network diagram.

60
Q

Node

A

One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines.

61
Q

Objective

A

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

62
Q

Opportunity

A

A condition or situation favorable to the project, a positive set of circumstances, a positive set of events, a risk that will have a positive impact on project objectives, or a possibility for positive changes. Contrast with threat.

63
Q

Organizational Breakdown Structure (OBS)

A

A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.

64
Q

Organizational Process Assets

A

Any or all process related assets, from any or all of the organizations involved in the project that are or can be used to influence the project’s success. These process assets include formal and informal plans, policies, procedures, and guidelines. The process assets also include the organizations’ knowledge bases such as lessons learned and historical information.

65
Q

Output

A

A product, result, or service generated by a process. May be an input to a successor process.

66
Q

Lag

A

A modification of a logical relationship that directs a delay in the successor activity. For example, in a finish-to-start dependency with a ten-day lag, the successor activity cannot start until ten days after the predecessor activity has finished. See also lead.

67
Q

Late Finish Date (LF)

A

In the critical path method, the latest possible point in time that a schedule activity may be completed based upon the schedule network logic, the project completion date, and any constraints assigned to the schedule activities without violating a schedule constraint or delaying the project completion date. The late finish dates are determined during the backward pass calculation of the project schedule network.

68
Q

Late Start Date (LS)

A

In the critical path method, the latest possible point in time that a schedule activity may begin based upon the schedule network logic, the project completion date, and any constraints assigned to the schedule activities without violating a schedule constraint or delaying the project completion date. The late start dates are determined during the backward pass calculation of the project schedule network.

69
Q

Lead

A

A modification of a logical relationship that allows an acceleration of the successor activity. For example, in a finish-to-start dependency with a ten-day lead, the successor activity can start ten days before the predecessor activity has finished. A negative lead is equivalent to a positive lag. See also lag.

70
Q

Lessons Learned

A

The learning gained from the process of performing the project. Lessons learned may be identified at any point. Also considered a project record, to be included in the lessons learned knowledge base.

71
Q

Lessons Learned Knowledge Base

A

A store of historical information and lessons learned about both the outcomes of previous project selection decisions and previous project performance.

72
Q

Leveling

A

See resource leveling.

73
Q

Life Cycle

A

See project life cycle.

74
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, quality control, action, or defect.

75
Q

Logical Relationship

A

A dependency between two project schedule activities, or between a project schedule activity and a schedule milestone. The four possible types of logical relationships are: Finish-to-Start; Finish-toFinish; Start-to-Start; and Start-to-Finish. See also precedence relationship.

76
Q

Manage Project Team

A

The process of tracking team member performance, providing feedback, resolving issues, and managing changes to optimize project performance.

77
Q

Manage Stakeholder Expectations

A

The process of communicating and working with stakeholders to meet their needs and addressing issues as they occur.

78
Q

Master Schedule

A

A summary-level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones. See also milestone schedule.

79
Q

Material

A

The aggregate of things used by an organization in any undertaking, such as equipment, apparatus, tools, machinery, gear, material, and supplies.

80
Q

Matrix Organization

A

Any organizational structure in which the project manager shares responsibility with the functional managers for assigning priorities and for directing the work of persons assigned to the project.

81
Q

Methodology

A

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

82
Q

Milestone

A

A significant point or event in the project.

83
Q

Milestone Schedule

A

A summary-level schedule that identifies the major schedule milestones. See also master schedule.

84
Q

Monitor

A

Collect project performance data with respect to a plan, produce performance measures, and report and disseminate performance information.

85
Q

Monitor and Control Project Work

A

The process of tracking, reviewing, and regulating the progress to meet the performance objectives defined in the project management plan.

86
Q

Monitor and Control Risks

A

The process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process throughout the project.

87
Q

Monitoring and Controlling Processes

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 the corresponding changes.

88
Q

Monte Carlo Analysis

A

A technique that computes or iterates, the project cost or project schedule many times using input values selected at random from probability distributions of possible costs or durations, to calculate a distribution of possible total project cost or completion dates.

89
Q

Monte Carlo Simulation

A

A process which generates hundreds or thousands of probable performance outcomes based on probability distributions for cost and schedule on individual tasks. The outcomes are then used to generate a probability distribution for the project as a whole.