Project Management Dictionary of Terms

This glossary covers all common project management terminology.
A - Acceptance Criteria to Authority | B - Backward Pass to Business Process Manager (BPM) | C - Change to Customer | D - Decision Tree Analysis to Duration | E - Early Finish Date to Event | F - Failure Mode and Effect Analysis to Functional Organisation | G - Gantt Chart to guidelines | H - Hammock task to Hyperlink | I - i-j notation to ITIL | J - Job Description to Just-In-Time | K - Kaizen to Knowledge | L - Labor, Equipment, Material to Logical Relationship | M - Manage Project Team to Monte Carlo Analysis | N - Near-Critical Activity to Node | O - Operations to Output | P - Parametic to Projectized Organization | Q - Qualitative Risk Analysis to Quantitative Risk Analysis | R - Records Management to Root Cause Analysis | S - Saved Search to System | T - Target Completion Date to Triple Constraint | U - Uncontrollable Risks to User Group | V - Validation to Voice of the Customer | W to Z - War Room to Zero Float

A - Acceptance Criteria to Authority

Activity-On-Node (AON)

Actual Cost (AC)

Total costs actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component. Actual cost can sometimes be direct labor hours alone, direct costs alone, or all costs, including indirect costs. Also referred to as the actual cost of work performed (ACWP). See also earned value.

Actual Cost of Work Performed (ACWP)

Total cost actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component.

Actual Finish Date (AF)

The point in time that work actually ended on a schedule activity. (Note: In some application areas, the activity is considered "finished" when work is "substantially complete.")

Actual Start Date (AS)

The point in time that work actually started on a schedule activity.

Agile

Agile refers to a group of project management approaches often used in software development, but increasingly widely used across multiple industries and project types. The project is delivered in small increments or sprints. Plans, requirements and outcomes are assessed regularly and flexibility is built in to allow evolution (changes) in requirements. Emphasis is placed on self-organising, co-located and cross-functional teams.

The Manifesto for Agile Software Development sets out four values for Agile Software Development:
  • Individuals and interactions over processes and tools
  • Working Software over comprehensive documentation
  • Customer Collaboration over contract negotiation
  • Responding to Change over following a plan

Agreement

A legal document that binds two or more parties to specific and implied obligations (e.g., a contract).

Align

Building a common understanding of the project and developing a common view of what the solution will and will not address.

Approved Change Request

A change request that has been processed through the integrated change control process and approved. Contrast with requested change.

Download a Change Request Template.

As-Late-As-Possible ("ALAP")

An activity for which the application sets the early dates as late as possible without delaying the early dates of any successor.

As-Soon-As-Possible ("ASAP")

An activity for which the application sets the early dates as soon as possible. This is the default activity type in most project management systems.

Authority

The right to apply project resources, expend funds, make decisions, or give approvals.

Avoid (risk response)

A risk is avoided by changing the project in some way. For example, by changing the project approach, technology, machinery, resources etc.
 

Methodology specific dictionaries / glossaries