Prince2:2009 - Glossary of Terms
More..
Term
|
Definition
|
accept (risk
response)
|
A risk response to
a threat where a conscious and deliberate
|
|
decision is taken
to retain the threat, having discerned that it is
|
|
more economical to do so than to
attempt a risk response action.
|
|
The threat should continue to be
monitored to ensure that it
|
|
remains tolerable.
|
|
|
acceptance
|
The formal act of
acknowledging that the project has met agreed
|
|
acceptance criteria and thereby met
the requirements of its
|
|
stakeholders.
|
|
|
acceptance criteria
|
A prioritized list
of criteria that the project product must meet before
|
|
the customer will accept it, i.e.
measurable definitions of the
|
|
attributes required for the set of
products to be acceptable to key
|
|
stakeholders.
|
|
|
activity
|
A process, function
or task that occurs over time, has recognizable
|
|
results and is managed. It is
usually defined as part of a process or
|
|
plan.
|
|
|
agile methods
|
Principally,
software development methods that apply the project
|
|
approach of using
short time-boxed iterations where products are
|
|
incrementally developed. PRINCE2 is
compatible with agile
|
|
principles.
|
|
|
approval
|
The formal confirmation
that a product is complete and meets its
|
|
requirements (less
any concessions) as defined by its Product
|
|
Description.
|
|
|
approver
|
The person or group
(e.g. a Project Board) who is identified as
|
|
qualified and authorized to approve
a (management or specialist)
|
|
product as being complete and fit
for purpose.
|
|
|
assumption
|
A statement that is
taken as being true for the purposes of
|
|
planning, but which could change
later. An assumption is made
|
|
where some facts are not yet known
or decided, and is usually
|
|
reserved for
matters of such significance that, if they change or turn
|
|
out not to be true, there will need
to be considerable replanning.
|
|
|
assurance
|
All the systematic
actions necessary to provide confidence that the
|
|
target (system,
process, organization, programme, project,
|
|
outcome, benefit, capability,
product output, deliverable) is
|
|
appropriate. Appropriateness might
be defined subjectively or
|
|
objectively in
different circumstances. The implication is that
|
|
assurance will have a level of
independence from that which is
|
|
being assured. See also ‘Project
Assurance’ and ‘quality
|
|
assurance’.
|
|
|