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.A - acceptance critera to Agilometer | B - backlog to business case | C - change authority to customer subject matter expert | D - definition of 'done' to Dynamic Systems Development Method | E - early adopter to experiment | F - G - feature to Glad! Sad! Mad! | H - I - higlight report to issue | K - Kaizen to Kano | L - lead time to Little's Law | M - manage by exception to MoSCoW | P - Plan-Do-Check-Act to push system | Q - quality assurance to quality tolerance | R - RACI to risk register | S - SAFe to supplier subject matter expert | T - team dynamics to transparency | U - V - user story to visioning | W - Waterfall method to workshop
R - RACI to risk register
RACI
A model used to help define roles and responsibilities. RACI stands for responsible, accountable, consulted and informed.
release
The set of products in a handover. The contents of a release are managed, tested and deployed as a single entity.
In PRINCE2 Agile, a release is typically a container for more than one low-level timebox (e.g. a sprint)). However, this is not necessarily the case as the act of releasing features into operational use may happen more regularly (e.g. after each sprint or several times during a sprint).
In PRINCE2 Agile, a release is typically a container for more than one low-level timebox (e.g. a sprint)). However, this is not necessarily the case as the act of releasing features into operational use may happen more regularly (e.g. after each sprint or several times during a sprint).
requirement
A term to describe what a product does and/or how it will do it. A requirement can be written in the form of a user story if desired and will exist with other requirements in the form of a list.
Download a Requirements Management Plan
Download a Requirements Traceability Matrix
retrospective
A regular event that looks at how the process of doing work can be improved. In keeping with the agile concept of 'inspect and adapt', these events help teams to continually improve their working practices, little by little, over time.
risk
An uncertain event or set of events that, should it occur, will have an effect on the achievement of objectives.
A risk is measured by a combination of the probability of a perceived threat or opportunity occurring, and the magnitude of its impact on objectives.
risk management strategy
Describes the goals of applying risk management to the activity, the process that will be adopted, the roles and responsibilities, risk thresholds, the timing of risk management interventions, the deliverables, the tools and techniques that will be used, and the reporting requirements. It may also describe how the process will be coordinated with other management activities.
risk register
A record of all identified risks relating to an initiative, including their status and history. Also called a risk log.
Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS.
Support stakeholdermap.com
If you liked this page, feel free to recommend us!
If you liked this page, feel free to recommend us!