Project Management Glossary

for 200CT, 221CR, 215IS & H85CS

A package of work (same as task) (cf. event). From Field and Keller, Project Management

Some behaviour that may persist for the duration of a state (ie something is happening but the 'state' isn't changing. From Bennet et al

Aim

What you intend to do. (Same as one definition of 'goal'.) From Field and Keller, Project Management

CPA

A diagrammatic technique for analysing the dependencies between project tasks and determining those that must be completed on time if the project itself is to be completed on time. Also called PERT or Network Analysis. From Bennet et al

Critical Path

A path of sequential activities such that an increase in the duration of any one of them wll increase the time required to complete the project. From Field and Keller, Project Management

Deliverable

A product to be delivered at a specified time during a project, maybe at its end. Includes intangibles, such as test results. Based on Field and Keller, Project Management

Design Specification

Can be taken to mean the same as a Requirments Specification. Sommerville considers this to be a detailed abstract description which is the basis for the system design. Based on Sommerville, Software Engineering

Event

A point in time when all the activities have been completed which lead into the node under consideration (cf. activity and task ). From Field and Keller, Project Management

Float

The time available for an activity or path in addition to its duration. From Field and Keller, Project Management

Functional Specification

see Requirements Specification

Gantt chart

A chart with a timescale in which a bar represents the period over which each activity is scheduled to be performed. From Field and Keller, Project Management

Goal

The desired outcome. A final point marking the desired end or the object desired. (Same as 'aim'.) From Field and Keller, Project Management

A general characteristic which the system should exhibit eg 'user-friendly'. (cf Requirement which is testable) From Sommerville, Software Engineering

Milestone

An event selected for its importance in the project. From Field and Keller, Project Management

Objective

A means towards obtaining an aim or goal. The things the organisation wants to achieve. Examples:

to increase profit
to improve my family's standard of living
to reduce society's dependance on motor cars

These imply that actions are needed to achieve broader goals, such as 'a happy family life'.

A football team probably has aims: to win matches and trophies; to bring paying spectators so the club is profitable. The team's possible objectives are: to score goals; to prevent the opposition from scoring goals; to play exciting football; to win the league, cup or promotion.

Based on Field and Keller, Project Management

Try to ensure all objectives are ‘smart’:

S – Specific – precisely described

Similar to a 'requirement' but generally considered to be larger. An objective may breakdown into several requirements.

Project

A temporary endeavour undertaken to create a unique product or service

temporary – definite beginning and definite end – not continuous
unique – different in some distinguishing way from similar products or services (time, space, resources etc).

Based on PMI (Project Management Institute), Body of Knowledge, www.pmi.org

Requirement

A statement of what is expected of a product or project, what role it is expected to fill or what it is expected to do. From Field and Keller, Project Management

A feature which the system should have, which must be testable (ie checkable). (cf Goal which is not testable) From Sommerville, Software Engineering

Similar to, but sometimes considered to be 'smaller' than, an objective

Requirements definition

Many different interpretations exist. A description of the services the system is to provide and its constraints. Does not include design characteristics. Includes both functional and non-functional requirements. Based on Sommerville, Software Engineering

A statement of what is expected, not how it might be done. Must be appropriate and well-defined. Based on Field and Keller, Project Management

Requirements Specification

Many different interpretations exist. Can mean anything from a broad outline statement to a mathematically-presented formal specification. A structured document which sets out the user services the system is expected to provide. Sometimes called a functional specification. Should be precise and detailed since it acts as a contract between the client and developer. Often created at the same time as a high-level design. Based on Sommerville, Software Engineering

A statement of the characteristics of a project or product. Must be able to prove the requirements have been met so need to be well-defined. Based on Field and Keller, Project Management

Covers the processing required, inputs, outputs and data to be stored. Also includes non-functional issues such as perfprmance criteria, data volumes and security issues. From Bennet et al

Risk

The probability of an undesired outcome - something 'going wrong'. Based on Field and Keller, Project Management

Risk Assessment

An assessment of what can go wrong with a project; aims to identify risks, quantify their likelihood pf occurribg and assess their likely impact on the project. It is intended to allow Risk Management to take place. Based on Field and Keller, Project Management

Risk Management

Strategies for dealing with risks, including avoidance, acceptance and reduction. Preceeded by Risk Assessment to take place. Based on Field and Keller, Project Management

Task

A specific activity or step in a project (same as activity) (cf. event ). From Bennet et al