Home | Sign in | Products | Services | Demonstration | Brochures | Templates | Newsletters | News Room

People, Performance, Portfolios, Processes, Products and Projects
 
Glossary

Glossary

Project Plan

The Glossary in a Project Plan (or any other project deliverable) should contain the following:

  1. All common terms

  2. All common abbreviations and acronyms

  3. Old terms with new term equivalent

Glossary of Terms

The following terms have been used in PMMentor (PMM). Also see the "Glossary Of Project Management Formulae" (below) for additional terms.

Term Meaning
Activity Activities are work that needs to be done in order to produce a final or intermediate deliverable in a project lifecycle phase. They involve one or more tasks, with specified inputs and deliverables.

Activities are performed both iteratively and continuously throughout a project lifecycle phase (not like a task which must be completed before another task can begin). As an example, the Activity "Manage People's Expectations", is not a one-off task, but something you need to be doing all of the time.

There is not necessarily a logical link between an Activity and an Event. Events are checkpoints, whereas Activities are work to be performed. An Activity may be required to achieve an Event or may span several Events.

An Activity is the level at which the project should be managed. Do not micro manage at the task level.

Activities do not need to have a verb as their first word.
Application Architecture
Application System The final deliverable of the project is called the Application System. It is usually the project outcome.

The logical grouping of entities, attributes and Functions which interact in a homogeneous manner to provide a logical solution for a particular Business Area of the Enterprise.

An Application System is on-going and differs from a "project" which has a finite life.

An Application System is a convenient breakup of an Enterprise's operations into components which are more easily assimilated. It also assists in the evaluation of off-the-shelf software packages sourced from outside subcontractors, vendors and suppliers.
Application Portfolio A collection of Application Systems.
Archive To copy data from where it is normally stored (eg, on a file recorded on disk) to removable media (eg, magnetic tape) leaving only a residual pointer to say it has been archived and on which removable media (eg, magnetic tape ID). The data can be retrieved from its archive state but at some inconvenience in terms of delay between the request for the data and actually getting access to it.

This is a convenient way of storing statutory information (ie, for 7 years).

See "Purge".
Attribute An individual logical data item which the Enterprise wishes to know about an entity. During application system development, attributes become fields on computer-based files. This is the smallest item of data.

Examples include:

  • Name Of Client

  • Date Of Last Payment
Audit Trail A record of who added, changed or deleted an entity occurrence, the type of modification together with the date and time of the modification.
Bar Chart See "Gantt Chart".
Baseline The project schedule (tasks, task-to-task dependencies, resources and costs) as you initially planned it (ie, the "Project Budget").
Business Architecture
Business Area We prefer the term "Business Area" to those of "Business Unit", "Cost Centre", "Profit Centre", "Service Centre" or "Organisation Unit" since it is a neutral term which has no emotion to it.

A Business Area may be the whole Enterprise or may be any subdivision of the Enterprise. Thus it includes all manner of things like Division, Department, Branch, Section, Group, etc.
Business Event These are the highest level of the Functions hierarchy. They are triggers which cause things to happen within the Enterprise. They may be generated either internally or (more commonly) externally to the Enterprise. They are sometimes known as "transactions".

Each Business Event will usually appear as a selectable menu item in the application system.

Not all Business Events are necessarily computerised.

Not all Business Events are mandatory.

Examples include:

  • Creditors Invoice

  • Purchase Order

  • Delivery Advice
Business Process See "Process".
Calendar A calendar defines the working days and hours for the project.
Child Task See "Task".
Class A Class contains the definition of the data structure and behaviour of an object instance. An object that is an instantiation of a particular Class will possess the properties and behaviours ("Methods") of that Class.
Classification A way of assigning a type or category to something. Examples include:
  • Client Type

  • Purchase Order Type
Comparison Count The function point count performed alone by the second Function Point Counter.
Configuration Item AKA "Contract Item".

All significant Deliverables to do with the project that we wish to track in terms of availability dates, current status, bill of materials, versions, who has them, ability to "mix and match", where they are in the Systems Development Pipeline, etc. Examples include all:

  • Deliverables

  • Documents

  • Test Plans

  • Test Cases

  • Programs

  • Contracts

  • Products

  • Requirements

  • Scope Changes

  • Functions

  • Specific Equipment Units

  • Check Lists

  • Systems

  • Training Courses

  • Processes

  • System Interfaces

  • Forms

  • Policies

  • Procedures

A Configuration Item is always a Deliverable.
Cost Centre See "Business Area".
Counting Boundary The precise definition of what is to be counted and what is to be excluded from the function point count.
Counting Document The document that is used as the source of the Function Point Count. This can be one of the following:
Crashing Crashing is the process of refining a project schedule to complete it within either a cost or time constraint.
Critical Path A project's critical path is made up of those tasks that will cause the project end date to be changed if any one of those tasks is changed.
Critical Path Method (CPM) A project management technique of calculating total project duration based on individual task durations and task-to-task dependencies. A path becomes "critical" because it includes those tasks with the longest duration and can not afford any delays without affecting the project end date.
Cycle Time The elapsed time it takes to complete one cycle of a Process.
Data Fundamental (ie, non-aggregated) facts, numbers, letters and symbols stored in the computer which has been created and/or used by an application system.

See "Information".
Data Flow Diagram A logical diagram showing how Functions operate upon data.
Data Model See "Logical Data Model".
Defect Any reproducible deviation of software from its specification.
Deliverable Work products produced by the project. These can either be designed to survive the project (eg, a User's Guide) or just be applicable during the project lifecycle. A deliverable need not be a Configuration Item.
Dependency The timing relationship between two tasks.
Derived Attribute (or entity) Non-fundamental data calculated by applying some formula to fundamental data. May also apply to replicated copies of fundamental data. May also apply to application system-generated data (eg, Date Of Transaction Entry).
Duration The length of elapsed time needed to complete a task or the whole project.
Duration-Driven A task is duration-driven when it will take the same amount of elapsed time to perform regardless of the number of resources assigned to perform it.
Effort-Driven A task is effort-driven when it will take less elapsed time to perform as more resources are assigned to perform it.
Enquiry
Entity A logical grouping of data about which the Enterprise is interested. During application system development, entities become computer-based files.

Examples include:

  • Client

  • Client Order

  • Project
Entity Relationship Diagram A diagram showing all of the data relationships between entities.
Estimate To Complete The amount of time or cost needed to finish a task or project.
Event Events are checkpoints which a project team needs to meet in order to produce the deliverable for the project phase in a fixed timeframe. Events are not necessarily milestones.
File
Float See "Slack".
Foreign Key The attribute(s) by which occurrences of one entity are logically linked to occurrences in some other entity. A foreign key in one entity must be a primary key in some other entity.

This implies that any value entered into a foreign key attribute will be validated against the entity where it occurs as a primary key to ensure that it does already exist in that "home" entity. It also implies some form of enquiry capability to view what occurrences exist in the entity where it is a primary key (sometimes known as a "Foreign Key Enquiry" or "pop-up").
Function See "Business Event".
Function Decomposition A function decomposition is a hierarchy of things which occur, get done or are performed within or by the Enterprise. The hierarchy shows Business Events, Functions and tasks. There are rarely more than six levels in the hierarchy.

Example:

0. Enterprise

X.1 Business Area

X.1.1 Application System

X.1.1.1 Subsystem/Module

X.1.1.1.1 Function

X.1.1.1.1.1 Subordinate Function

X.1.1.1.1.1.1 Sub-Subordinate Function

X.1.1.1.1.1.1.1 Validation and Derivation Task
Function Point Count The process of counting function points.
Function Point Estimate Worksheet The Microsoft Excel spreadsheet used to record the results of the function point count.
Fundamental Entity
Gantt Chart A time-phased view of a project Work Plan (schedule) showing tasks and their durations. Tasks are listed down the page and their durations are shown as horizontal bars whose width denotes their duration and whose position under the timeline denotes when they will start and end.
Hard Wall Date A Milestone date that must be met.
Implementation Included in Rollout phase.
Identifier Attribute
Information Data presented in a meaningful way by an application system. This may simply be the listing of fundamental data or the more complex manipulation of data by applying some formula to it.

See "Data".
Information Engineering The general name given to the application system development Methodology encompassing the techniques of Data Modelling and Function Analysis.
Initial Count The function point count performed by the first Function Point Counter in conjunction with a Business Staff representative and an IT Department representative from the Client.
Input
Installation
Interface
Intersecting Entity
Key One or more attributes within an entity used to identify an occurrence of an entity, to control its use and/or to define the sequence in which it is recorded within the entity.

See "Primary Key", "Foreign Key" and "Secondary Key".
Lag Time The time delay between the end of one task and the start of its successor task(s).
Lead Time The time overlap between the end of one task and the start of a successor task.
Logical Data Model A logical diagram showing all of the entities and attributes as well as all of their relationships to be stored by an application system.
Logical User View
Method/Operation Methods are behaviours of Classes. Methods are executed when a message is sent to an object. Methods are similar to functions or subroutines in traditional programming environments.
Methodology An integrated framework of project lifecycle processes, techniques, concepts and themes, tools, templates, check lists and project management approach.
Milestone A task with a duration of zero that indicates the beginning or completion of a significant project event.
Normalisation A formal method used to organise data into logical groupings (ie, entities) to avoid duplication and redundancy as well as to provide flexibility in programming and retrieval of data.
Organisation Breakdown Structure The Business Area responsible for completing a task.
Organisation Unit See "Business Area".
Output
Parent Task See "Summary Task".
PERT Chart A view of a project schedule showing all task-to-task dependencies.
Phase
Predecessor Task A task that must be completed before another task can begin.
Primary Key The attribute(s) which uniquely identifies an occurrence of an entity. The primary key also defines:
  • Which attribute(s) must be entered by the Data Entry Operator to retrieve occurrences of the entity

  • The primary sequence of occurrences of the entity.

Example:

  • For a Vessel/Ship entity, the primary key may be the "Lloyd's Registration ID" attribute.
Process
Process Diagram
Product Breakdown Structure (PBS) A hierarchical list of all project work products (ie, things that are produced by the project).
Project The overall process of specifying an Enterprise's requirements for one or more application systems and then either procuring an off-the-shelf software package solution or building one. Also includes the installation, training and implementation associated with making the application system work. A project has a finite life and differs from an "application system" which is on-going.
Project Participant Includes the project team as well as Project Support Group.
Profit Centre See "Business Area".
Programme Evaluation and Review Technique (PERT) The combination of task-to-task dependencies (successor and predecessor relationships) among a project's tasks forms a network. This network can be analysed to determine the critical path and other project schedule implications.

PERT is a technique for determining how much time a project needs to complete. Each task is assigned a best, worst and most probable duration. These estimates are used to determine the average duration for each task. The average task duration is then used to determine the project's critical path as well as the standard deviation of the whole project's duration.
Project Portfolio See "Works Programme".
Project Team The core group of people working on the project.
Project Team Member A person who is a member of the project team.
Proposed Solution Encompasses system software, application software, hardware, telecommunications and associated services.
Purge The deleting of ALL trace of an occurrence of an entity. No backup copies are taken. All occurrences of an entity which are to be purged are listed on a report so that this hardcopy may be archived.

See "Archive".
Reconciliation Count The reconciliation function point count performed by both the first and second Function Point Counters.
Relationship The association between two things (eg, people, Business Areas, entities). Relationships can show:
  • Hierarchy (eg, Department A is subordinate to Branch 3)

  • Aliases (eg, Item X is known as a "Desk" by Branch 1 but is known as a "Table" by Branch 3)

  • Sequence (eg, Perform Job 37 before Job 29)

  • Bill Of Materials (eg, Item A is made from Items X, Y and Z)
Repeating Attribute An attribute which occurs more than once within the one entity.
Resource The personnel, equipment, facilities, infrastructure, funding and materials required to complete a task or project.
Resource Levelling Delaying tasks to resolve resource usage conflicts (ie, over allocations). When a resource's capacity is exceeded, you can use resource levelling to resolve the conflict.
Rollout
Scheduling The process of determining when project tasks will be performed. It is performed within duration, task-to-task dependency and resource availability constraints.
Scope As well as the functionality to be delivered, Scope also includes all other work that needs to be performed by the project (eg, project management).
Secondary Key The attribute(s) which specify a secondary (or alternate) way of uniquely identifying an occurrence of an entity. For an Employee entity, examples could include:
  • The primary key may be the "Employee ID" attribute

  • A secondary key may be the "Name Of Employee" attribute
Security The protection of occurrences of an entity from unauthorised access or modification (ie, add, change, delete, enquire, print, replicate or filter). The following types of security exist:
  • Menu Level - Unless the program which accesses the entity appears on a person's menu, they will not be able to access or modify any occurrences of the entity.

  • Business Area Level - Data Entry Operators authorised to access the entity by way of Menu Level security may only access or modify those occurrences which apply to their Business Area. Head Office Data Entry Operators may enquire on all Business Area's data but may not modify it.

  • Add/Change/Delete/Enquire/Print/Replicate/Filter Level - Data Entry Operators authorised to access the entity by way of Menu Level security are further controlled as to the actions which they may perform on occurrences of the entity (ie, some Data Entry Operators may add, change and/or delete while other Data Entry Operators may be restricted to enquire and print only).
Service Centre See "Business Area".
Slack (Free) The amount of time a task can be delayed past its end date without delaying another task.
Slack (Total) The amount of time a task can be delayed without delaying the project end date.
Slippage The amount of time that a task's end date has been delayed. If the task is on the critical path and/or the delay uses up all of a task's Float, then the project's end date will also slip.
Stakeholder Includes all project participants as well as all Interested Parties, fringe dwellers and hangers on. It includes all people who have an interest in seeing the project completed or will be impacted by the project's outcomes.

This term also relates to all those identities (people or Enterprises) which have an interest in the successful operation of the Enterprise. This includes all shareholders, owners, employees, Customers, Clients, consumers, debtors, subcontractors, vendors, suppliers, creditors, etc.
Standard Operating Environment See "Technical Architecture" below.
Subcontractor An Enterprise that is delivering a major component of the overall project but has a contract to do so with the Prime Contractor and not to the Client directly (eg, the software development Enterprise).
Subordinate Entity
Successor Task See "Predecessor".
Summary Task A summary task is one which has been decomposed into smaller child tasks. Its duration will be derived from that of the child tasks.
Supplier An Enterprise that supplies products and/or services that are required for the project but are either tangential or not mainstream to the project (eg, the supply of 1 Personal Computer for the project to use to demonstrate its deliverables).
System Software Includes:
  • Operating System

  • Data Base Management System
Task Planned work which must be performed during the project. Tasks have a duration and require resources to perform them.

Tasks should always have a verb as their first word (so as to make them an imperative statement to assist in galvanising people into action) except for Milestones which should have a noun first and past tense verb last.

Tasks are also the lowest level of the function hierarchy. There are only two types:

  • Derivation (ie, calculating something), and

  • Validation (ie, verifying entered data is logically, semantically and syntactically correct).

Tasks define the Business Rules which will be embedded in source program code. Examples include:

  • Validate Date Applicable To Attribute

    This Attribute must not be less than the Date Applicable From Attribute.

  • Derive Quantity Onhand Attribute

    This Attribute is derived using the following formula:

    Quantity Onhand - Quantity Of Issue.
Technical Architecture The Enterprise's standard for hardware, system software, development software, application software and telecommunications platforms (eg, what mainframe, mid-range, desktop hardware, system software and application software can be used in the Enterprise). Sometimes known as the "Standard Operating Environment (SOE)".
Timebox
Vendor An Enterprise that is delivering a major component of the overall project but has a contract to do so with the Client directly and not to the Prime Contractor (eg, the mainframe hardware vendor Enterprise).
Work Breakdown Structure (WBS) A Work Breakdown Structure is a hierarchical organisation of tasks. Sometimes known as an "outline". The WBS facilitates assignment of work packages, determination of tasks within the WBS as well as project performance reporting.
Works Programme A collection of projects.

Glossary of Abbreviations and Acronyms

The following abbreviations and acronyms have been used in PMMentor (PMM). Also see the "Glossary Of Project Management Formulae" (below) for additional abbreviations and acronyms.

Abbreviation Meaning
4GL Fourth Generation Language
ABC Activity-Based Costing
ACM Association of Computing Machinery
ACRONYMS A Convenient Reduction Of Nomenclature Yielding Mnemonic Syllables
ACS Australian Computer Society
ACWP Actual Cost of Work Performed (the actual cost of completing the actual work in any given time period)
AIM Australian Institute of Management
AKA Also Known As
ALAP As Late As Possible
AMA American Management Association
ANSI American National Standards Institute
API Application Program Interface
APM Association of Project Managers
ASAP As Soon As Possible
ASMA Australian Software Metrics Association
BAC Budgeted At Completion (Baseline Cost)
BAFO Best And Final Offer
BCWP Budgeted Cost of Work Performed (Achieved Cost, Earned Value)
BCWS Budgeted Cost of Work Scheduled (Baseline Elapsed Cost)
BPR Business Process Re-Engineering
BL Business Leader
BRP Business Recovery Planning
BS British Standard
CASE Computer Assisted Software Engineering
CBA Cost/Benefit Analysis
CBT Computer-Based Training
CCB Configuration Control Board
CCPM Critical Chain Project Management
CDRL Contract Deliverables Requirements List
CD-ROM Compact Disk - Read-Only Memory
CFPS Certified Function Point Specialist
CI Configuration Item
CI Contract Item
CM Configuration Management
CFPS Certified Function Point Specialist
CM Configuration Management
CMM Capability Maturity Model
CPI Cost Performance Index
CPI Consumer Price Index
CPM Critical Path Method
CPU Central Processing Unit
CRC Classes, Responsibilities, Collaboration
CRM Client Relationship Manager
C/SCS Cost/Schedule Control System (eg, PMComplete™)
C/SCSC Cost/Schedule Control System Criteria (eg, PMComplete™)
CSF Critical Success Factor
CSI Customer Satisfaction Index
C/SSR Cost/Schedule Status Report
CTI Computer-Telephony Integration
CV Cost Variance (Earned Value)
DAT Direct Access Tape
DBA Data Base Administrator
DBMS Data Base Management System
DCF Discounted Cash Flow (DCF)
DFD Data Flow Diagrams
DOA Dead On Arrival
DoD Department of Defence
DRP Disaster Recovery Planning
DSS Decision Support System
EAC Estimate At Completion
EBIT Earnings Before Interest and Tax
ECP Engineering Change Proposal
EDI Electronic Data Interchange
EIA Environmental Impact Assessment/Analysis
EIS Executive Information System
ERA Extended Relational Analysis
ERD Entity Relationship Diagramming
ERP Enterprise Resource Planning
ETC Estimate to Complete
EV Earned Value
EVA Earned Value Analysis
EVA Economic Value Added
EVM Earned Value Management
FAC Forecast At Completion
FAQ Frequently Asked Questions
FAT Function Analysis Technique
FBT Fringe Benefits Tax
FM Facilities Management
FTE Full Time Equivalent
FUD Fear, Uncertainty and Doubt
FX Foreign Exchange
GUI Graphical User Interface
HCI Human-Computer Interaction
HIPO Hierarchy plus Input-Process-Output
IC Infrastructure Co-ordinator
ICWG Interface Control Working Group
IEEE Institute of Electrical and Electronic Engineers
IFPUG International Function Point User's Group
ILS Integrated Logistics Support
ILT Instructor-Led Training
IR Industrial Relations
IRR Internal Rate of Return (IRR)
ISBSG International Software Benchmark Standards Group
ISL Initial Spares List
ISO International Standards Organisation
IT Information Technology
JAD Joint Application Design

JAD® is a registered trademark of IBM Corporation.
JAD Joint Application Development
JCL Job Control Language
JIT Just In Time
KLOC Thousands of Lines of Code
KSLOC Thousands of Source Lines of Code
KPI Key Performance Indicator
LAN Local Area Network
LCOF Lifecycle Objective Functions
LCPM Lifecycle Project Management
LDM Logical Data Model
M&A Mergers and Acquisitions
MB Megabyte
MBO Management By Objectives
MBWA Management By Walking Around
MIL-STD Military Standard
MIPS Millions of Instructions Per Second
MIS Management Information System
MOTA Moment of Truth Activities
MRP Material Requirements Planning
MTBF Mean Time Between Failures
MTTF Mean Time To Failure
MTTR Mean Time To Repair
MTTR Mean Time To Respond
NDA Non-Disclosure Agreement (see "Deed of Confidentiality")
NPV Net Present Value (NPV)
OBS Organisation Breakdown Structure
ODBC Open Data Base Connection
OLE Object Linking and Embedding
OMP Original Manufacture Price
OO Object-Oriented
OOA Object-Oriented Analysis (OOA)
OOD Object-Oriented Design (OOD)
OOP Object-Oriented Programming (OOP)
P&L Profit and Loss
PABX Private Automatic Branch Exchange
PBIT Profit Before Interest and Tax
PBS Product Breakdown Structure
PC Personal Computer
PCR Project Control Review (PCR)
PERT Programme Evaluation and Review Technique
PIR Post-Implementation Review (PIR) Workshop
PIT Process Improvement Team (PIT)
PMBOK Project Management Body of Knowledge
PMCoE Project Management Centre of Excellence
PMI Project Management Institute
PMP Project Management Professional
PNA Performance Needs Analysis
POC Proof of Concept
PPR Post-Project Review
PRB Project Review Board (PRB)
QA Quality Assurance
QC Quality Control
QFD Quality Function Deployment
QMS Quality Management System
R&D Research and Development
R&D Receiving and Dispatch
RAD Rapid Application Development
RAM Random Access Memory
RAM Responsibility Assignment Matrix
RBT Reference-Based Training
RBT Role-Based Training
RDBMS Relational Data Base Management System
RDO Rostered Day Off
RFI Request For Information
RFP Request For Proposal
ROI Return on Investment (ROI)
ROM Read-Only Memory
RONA Return On Net Assets
RTVM Requirements Traceability Verification Matrix
SA Subcontractor Administrator
SCM Software Configuration Management
SDLC Systems Development Lifecycle
SEI Software Engineering Institute
SI Systems Integration
SIG Special Interest Group
SLOC Source Lines of Code
SOD Signposts of Danger (SOD)
SOE Standard Operating Environment
SOP Standard Operating Procedure. See "Procedure" for use within PMMentor (PMM).
SOW Statement of Work (SOW)
SPI Schedule Performance Index
SPM Subcontractor Project Manager
SPQR Software Productivity, Quality and Risk
SPR Software Problem Report
SQL Structured Query Language
SV Schedule Variance Earned Value)
T&C Terms and Conditions
TA Transactional Analysis
TCO Total Cost of Ownership
TLA Three Letter Acronym
TNA Training Needs Analysis
TNF Third Normal Form
TOC Theory of Constraints
TPM Technical Performance Measurement
TPM Transactions Per Minute
TQM Total Quality Management (TQM)
TTFN Ta Ta For Now
UI User Interface
VAC Variance At Completion
WACC Weighted Average Cost of Capital
WAN Wide Area Network
WBS Work Breakdown Structure
WDV Written Down Value
WIP Work In Process

Glossary Of Project Management Formulae

The following formulae have been used in PMMentor (PMM):

In the following formulae,

  1. "+" means add the two variables together,

  2. "-" means subtract one variable from the other,

  3. "*" means multiply the two variables together, and

  4. "/" means divide the second variable into the first.
Characteristic Formula
Achieved Cost Percent Complete * Baseline Cost
Baseline Cost BAC
BCWP Percent Complete * Baseline Cost (the budget value of the work which has been physically completed in any given time period)
BCWS Baseline Cost * (As-Of Date - Baseline Start) / Baseline Duration (the sum of the budget for work scheduled to be completed in any given time period)
Baseline Elapsed Cost Baseline Cost * (As-Of Date - Baseline Start) / Baseline Duration
Cost Performance Index BCWP / ACWP
Cost Performance Ratio Achieved Cost / Spent Cost
Cost Variance Achieved Cost - Spent Cost
Cost Variance Percent (Achieved Cost - Spent Cost) / Spent Cost
Cumulative CPI Sum of All BCWP / Sum of All ACWP
CV BCWP - ACWP
Duration Variance (Baseline Duration - Duration) * Percent Complete
Earned Value Percent Complete * Baseline Cost
Effort Variance (Baseline Effort - Spent Effort) * Percent Complete
Elapsed Time Percent (Start Date - As-Of Date) / Duration
End Variance Baseline End - End
Mathematical EAC Cost Spent Cost + (Baseline Cost - Achieved Cost)
Predicted Cost (Elapsed Time Percent / Percent Complete) * Total Cost
Projected Duration (Elapsed Time Percent / Percent Complete) * Duration
Projected Effort (Elapsed Time Percent / Percent Complete) * Effort
Projected End Start Date + Projected Duration
Remaining Cost Total Cost - Spent Cost
Remaining Duration Duration - Spent Duration
Remaining Effort Effort - Spent Effort
Schedule Performance Index BCWP / BCWS
Schedule Performance Ratio Achieved Cost / Baseline Elapsed Cost
Schedule Variance Achieved Cost - Baseline Elapsed Cost
SV BCWP - BCWS
Schedule Variance Percent (Achieved Cost - Baseline Elapsed Cost) / Achieved Cost
Slack Percent Slack (Free or Total) / Duration
Spending Ratio Baseline Elapsed Cost / Spent Cost
Spent Cost
Spent Cost Variance Ratio Spent Cost / Baseline Cost
Spent Duration Start Date - As-Of Date
Spent Duration Variance Ratio Spent Duration / Baseline Duration
Spent Effort Percent Complete * Effort
Start Variance Baseline Start - Start
Total Cost Variance Baseline Cost - Total Cost
Total Cost Variance Percent (Baseline Cost - Total Cost) / Baseline Cost
Total Cost Variance Ratio Total Cost / Baseline Cost
VAC BAC - EAC

Also See

Documentation Style Standards
 About Us | Contact Us | Other Sites | Site Map | Technologies | What's New | Partners | Careers