logo
Home | The ProjectOutcomes: Workshop program | Licensed Delivery Partners | Resources | Glossary | Contact Us
 
 
Glossary
A B C D E F G H I J L M O P Q R S T U V W Z
Term Definition Discussion Examples & Illustrations
Champion See Promoter.

Closure A process of judging the project across a number of selected performance areas—with a view to improving the organisation’s performance on future initiatives. Closure is distinct from evaluation (which is concerned with gauging the project’s worth.

Closure is not to be confused with post-implementation review which is a formal technique to determine if an IS/IT output is fit-for- purpose.

Constraint An established boundary on a parameter of a project. Constraints are set as hard or soft:
  • A hard constraint is one that must not be violated under any conditions.
  • A soft constraint is one that, if violated, incurs some sort of penalty for a stakeholder.
Constraints are usually set for:
In addition, from the perspective of the project funder and owner, fulfilment of project scope is a constraint on achievement of the project’s target outcomes.
Cost (s) The value of resources demanded by the project’s WBS. Costs are of two kinds:
  • Outlays of cash—to acquire products/services from outside the sponsoring entity.
  • The opportunity cost of labour allocated to the project from within the funding entity.

Cost infeasible (project) A project for which an optimal resource plan indicates a demand for more resources than those approved in the budget.

The difference between the budget and the costs of the resource plan is a gauge of the level of (cost) infeasibility.
Cost infeasibility must be resolved before a project can be approved.

Refer also infeasible project.
If Henry Crun has indicated a budget of $50M for the exercise—but Minnie Bannister’s initial estimate is $60M—then the project is infeasible and must not be approved until the infeasibility is resolved.
Customer See Project customer.

Customer map A tool used to analyse the appropriateness of a project’s scoping statement. The customer map takes the form of a table in which:
  • The rows are associated with outputs.
  • The Columns are associated with target outcomes.
  • Cell entries indicate the project’s customers who utilise the linked outputs to generate the linked outcomes.