important project management terms

8/7/2019 Important Project Management Terms

1/6

Important project management terms

Below are some project management terms and techniques important for working with the MS project:

Activity: A component of work that is performed during the course of a project

Activity attributes: Multiple attributes associated with each scheduled activity that can be included

within the activity list. These include: activity codes, predecessor activities, successor activities, logical

relationships, leads and lags, resource requirements, imposed dates, constraints and assumptions.

Activity codes: One or more numerical or text values that identify characteristics of the work or in some

way categorize the schedule activity that allows filtering and ordering of activities within reports.

Actual cost: Total costs actually incurred and recorded in accomplishing work performed for a schedule

activity or recorded in accomplishing work performed for a schedule activity or work breakdown

structure (WBS) component. AC can be direct labor hours alone, direct costs alone, all costs including

indirect costs.

Arrow: The graphic presentation of a schedule activity in the arrow diagramming method or a logical

relationship between schedule activities in the precedence diagramming method.

Backward pass: The calculation of late finish dates and late start dates for the uncompleted portions of

the schedule activities. This is determined by working backwards through the schedule network logic

from the projects end date. The end date may be calculated in a forward pass or set by the customer or

sponsor.

Bar Chart (Tool): This is a graphic display of schedule related information. In the typical bar chart,

schedule activities or WBS components are listed down the left side of the chart, dates are shown across

the top and activity durations are shown as date-placed horizontal bars. Also called a Gantt chart.

Baseline: The approved time phased plan (For a project, a WBS component, a work package or a

schedule activity plus or minus approved project scope, cost, schedule and technical changes. Generally

refers to the current baseline, but may refer to the original or some other baseline. Usually used with a

modifier e.g. cost baseline, schedule baseline, performance measurement baseline and technical

baseline.

Baseline finish date: Finish date of a schedule activity in the approved schedule baseline

Baseline Start date: Start date of a schedule activity in the approved schedule baseline

Calendar Unit: This is the smallest unit of time used in scheduling the project. Generally, in hours, days

or weeks but can also be in quarter years, months, shifts or even in minutes.


2/6

Chart of accounts: Any numbering system used to monitor project costs by category e.g. labor supplies,

materials and equipment). The project chart of accounts is usually based upon the corporate chart of

accounts of the project performing organization.

Code of accounts: any numbering system used to uniquely identify each components of the WBS

contrast with chart of accounts.

Contingency Reserve: the amount of funds, budget or time needed above the estimate to reduce the

risk of overruns of project objectives to a level that is acceptable to the organization.

Control Chart: A graphic display of process data over time and against established control limits and that

has a center line that assists in detecting a trend of plotted values toward either control limit.

Cost performance index (CPI): A measure of cost efficiency on a project. It is the ratio of earned value

(EV) to actual costs (AC) CPI=EV/AC. If the value is 1 or greater, it indicates that there is a favorable

condition while a value that is less than 1 indicates an unfavorable condition.

Critical activity: Schedule activity on a critical path in a project schedule. This is determined by using the

CPM.

Data Date: Date through which the projects reporting system has provided actual status and

accomplishments. Also known as; as of date and time now date.

Deliverables: this refers to unique and verifiable product, result or capability to perform a service that

must be produced to complete a process, phase or project. This term is used more narrowly in reference

to an external deliverable which is a deliverable subject to the approval by the project sponsor or

customer.

Dummy activity: Schedule activity of zero duration used to show logical relationship in the arrow

diagramming method.

Earned value: Value of work performed expressed in terms of the approved budget assigned to that

work for a schedule activity or work breakdown structure component. This is also called budgeted cost

of work performed.

Effort: The number of labor units required to complete a schedule activity or WBS component. Usually

expressed as staff hours, staff days or staff weeks. This is different from duration

Enterprise: A company, business, firm, partnership, corporation or government agency

Fast tracking technique: A specific project schedule compression technique that changes network logic

to overlap phases that would normally be done in sequence, such as the design phase and construction

phase or to perform schedule act in parallel.

Finish to finish: This is the logical relationship where the completion of work of the successor activity

cannot finish until the completion of work of the predecessor activity


3/6

Finish to start: Where initiation of work of the successor activity depends upon the completion of work

of the predecessor.

Flowcharting: the depiction in a diagram format of the inputs, process actions and outputs of one or

more processes within a system.

Forecasts: estimates or predictions of conditions and events in the projects future based on information

and knowledge available at the time of the forecast.

Forward pass: Calculation of early start and early finish dates for the uncompleted portions of all

network activities.

Free float: the amount of time that a schedule activity can be delayed without delaying the early start of

any immediately following schedule activities.

Lessons learned: the learning gained from the process of performing a project. This may be identified at

any point. Also considered a project record to be included in lessons learned knowledge base.

Log: A document used to record, describe or denote selected items identified during execution of a

process or activity. Usually with a modifier such as issue, quality control, action or defect.

Logical relationship: dependency between 2 project schedule activities or between a project schedule

activity and a schedule milestone.

Milestone: a significant point or event in the project

Milestone schedule: a summary-level schedule that identifies the major schedule milestones

Monte Carlo analysis: a technique that computes or iterates the project cost or project schedule manytimes 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.

Network path: any continuous series of schedule activities connected with logical relationships in a

project schedule network diagram.

Parametric estimating: an estimating technique that uses a statistical relationship between historical

data and other variables to calculate an estimate for activity (e.g. square footage in construction lines,

lines of code in software development) parameters such as scope, cost budget and duration. This

technique can produce high levels of accuracy depending on the level of sophistication and the

underlying data built into the model. For example, the cost parameter is obtained by multiplying the

planned quantity of work by the historical cost per unit to obtain the estimated cost.

Pareto chart: a histogram ordered by frequency of occurrence that shows how many results were

generated by each identified case.

Organizational chart: A method for depicting interrelationships among a group of persons working

together toward a common objective.


4/6

Organizational breakdownstructure: a hierarchically organized depiction of the projects organization

arranged so as to relate the work package to the performing organization unit.

Planned value: the authorized budget assigned to the scheduled work to be accomplished for a

schedule activity or WBS. Also called budgeted cost of work scheduled.

Planning package: A WBS component below the control account with known work content but without

detailed schedule activities.

Precedence diagramming method: a schedule network diagramming technique in which they are

performed.

Predecessor activity: the schedule activity that determines when the logical successor activity can begin

or end.

Preventive action: documented direction to perform an activity that can reduce the probability of

negative consequences associated with project risks

Progressive elaboration: Continuously improving and detailing a plan as more detailed and specific

information and more accurate estimates become available as the project progresses and thereby

producing more accurate and complete plans that result from the successive iterations of the planning

process.

Project calendar: Working days or shifts that establishes those dates on which scheduled activities are

idle e.g. holidays, weekends and shift hours.

Project charter: 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 organizations to

project activities.

Project life cycle: this is a collection of generally sequential project phases whose names and no are

determined by the control needs of the organization or organizations involved in the project.

Project stakeholders: everyone affected directly or indirectly by a projects activity.

Qualitative analysis: the process of prioritizing risks for subsequent further analysis or action by

assessing and combining their probabilities of occurrence and impact.

Quantitative analysis: the process of numerically analyzing the effect on overall project objectives of

identified risks.

Reserve: a provision in the project management plan to mitigate cost and/or schedule risks often used

with a modifier e.g. (management reserve, contingency reserve) to provide further detail on what type

of risk that is meant to be mitigated. The specific meaning of the modified term varies by application

area. First you have to perform reserve analysis to determine reserve requirements.


5/6

Responsibility assignment matrix: a structure that relates the project organizational breakdown

structure to the work breakdown structure to help ensure that each component of the projects scope

of work is assigned to a responsible person.

Risk category: a group of potential causes of risks, may be grouped into technical, external,

organizational, environmental or project management. A category may include subcategories such astechnical maturity, weather or aggressive estimating.

Risk database: a repository that provides for collection, maintenance and analysis of data gathered and

used in the risk management processes.

Risk identification: determines which risks might affect the project and document their characteristics.

Risk management plan: document describing how project risk management will be structured and

performed on the project. It is contained in the project management plan.

Role: a defined function to be performed by a project team member, such as testing, fil ing, inspecting or

coding.

Schedule compression: shortening the project schedule duration without reducing the project scope.

Schedule control: controlling changes to the project schedule.

Schedule performance index: a measure of schedule efficiency on a project. Ratio of earned value to

planned value. EF/PV=SPI. When SPI=1, it indicates a favorable condition and values less than one

indicate unfavorable condition.

Scope: this is the sum of the products, services and results to be provided as a project.

Scope creep: adding features and functionality without addressing the effect on time, cost, resources or

without customers approval.

Scope verification: process of formalizing acceptance of the completed project deliverables.

Statement of work (SOW): a narrative description of products services or results to be supplied by a

project

Successor activity: the schedule activity that follows a predecessor activity as defined by their logical

relationship.

Triggers: indications that a risk has occurred. This may be described in the risk identification process and

watched in the risk monitoring and control process. It is also known as risk symptoms and warning signs.

Validation: technique of evaluating a component or product during or at the end of a phase or project

to ensure it complies with specified requirements.

Variance: a quantifiable deviation, departure away from a known baseline or expected value.


6/6

Verification: technique of evaluating a component or product at the end of a phase or project to assure

it satisfies conditions imposed.

Work authorization: permission and direction to begin work on a specific schedule activity or work

package.

Work breakdown structure: a deliverable oriented hierarchical decomposition of work to be done by

project team to accomplish the project objectives and create the required deliverables. It organizes and

defines the total scope of the project. Each descriptive level represents an increasingly detailed

definition of the project work done. The WBS is decomposed into work packages and includes both

internal and external deliverables.

Work package: a deliverable or project work at the lowest level of each branch of the WBS. It includes

schedule activities and schedule milestones required to complete the work package deliverable or

project work component.

Work performance information: information and data on the status of the project schedule activitiesbeing performed to accomplish the project work. It is collected as part of the direct and manage project

execution processes information and includes: status of deliverables, implementation status for change

requests, corrective /preventive actions, defect repairs and forecasted estimates to complete reported

% of work that is physically completed, achieved value of technical performance measures, start and

finish dates of schedule activities.

important project management terms

Documents