Agile Dictionary of Terms for Prince2
A - Z Dictionary of terms for Prince2 Agile edition. This is the official Dictionary of terms for the Agile prince 2 method. PRINCE2® is a registered trade mark of AXELOS Limited. See glossaries for Managing Successful Programmes (MSP), Project Office Dictionary (P30), PRINCE2, ITIL and Risk Management. See also the Project Management Dictionary
- acceptance critera to Agilometer
- backlog to business case
- change authority to customer subject matter expert
- definition of 'done' to Dynamic Systems Development Method
- early adopter to experiment
| F - G
- feature to Glad! Sad! Mad!
| H - I
- higlight report to issue
- Kaizen to Kano
- lead time to Little's Law
- manage by exception to MoSCoW
- Plan-Do-Check-Act to push system
- quality assurance to quality tolerance
- RACI to risk register
- SAFe to supplier subject matter expert
- team dynamics to transparency
| U - V
- user story to visioning
- Waterfall method to workshop
P - Plan-Do-Check-Act to push system
A four-stage cycle for process management, attributed to W. Edwards Deming. Plan-Do-Check-Act is also called the Deming Cycle. Plan – design or revise processes that support the IT service
s; Do – implement the plan and manage the processes; Check – measure the processes and IT service
s, compare with objectives and produce reports; Act – plan and implement changes to improve the processes
The period of time for which it is possible to plan accurately
A description of a product's purpose, composition, derivation and quality criteria. It is produced at planning time, as soon as possible after the need for the product is identified."
The role assigned to managing the product backlog in order to get the most value from it by ordering and prioritizing it.
A diagram or document that shows the intended development path for a product. This would typically be a long-range plan that may cover several months if not years. It exists outside a project context but could be used to trigger project work.
leading to a comprehensive plan based on the creation and delivery of required outputs. The technique
considers prerequisite products, quality requirements
and the dependencies between products.
A number of activities or projects that are planned and managed together.
A temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case
Read more on the characteristices of a Project - what is a project?
The project board's
responsibilities to assure itself that the project is being conducted correctly. The project board
members each have a specific area of focus for project assurance, namely business assurance for the executive, user
assurance for the senior user(s), and supplier
assurance for the senior supplier(s)
project initiation documentation (PID)
Usually, a single event where visioning activities may take place and the team comes together for the first time. The event can be run as workshops and require preparation to ensure that time is used as effectively as possible. (See also visioning
The planning, delegating, monitoring and control of all aspects of the project, and the motivation of those involved, to achieve the project objectives within the expected performance targets for time, cost, quality, scope
The person with authority and responsibility to manage a project on a day-to-day basis to deliver the required products within the constraints agreed by the project board
A high-level plan showing the major products of the project, when they will be delivered and at what cost. An initial project plan is presented as part of the project initiation documentation
. This is revised as information on actual progress appears. It is a major control document for the project board
to measure actual progress against expectations.
project product description
An administrative role in the project management team. Project support can be in the form of advice and help with project management tools, guidance, administrative services such as filing, and the collection of actual data.
Something created to help prove or disprove an idea, or to help to improve the general understanding of a situation (e.g. the customer's needs). It could be something that evolves into a real product or is thrown away.
A way of working in which work is started or 'pulled' from upstream, but only as capacity becomes available.
Kanban systems are pull systems. The availability of capacity and the ability to pull work are indicated by the gap between current work in progress and the corresponding limit. See also push system
The act of placing work into a system or activity
without due regard to its available capacity. See also pull system
Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS