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

S - SAFe to supplier subject matter expert

SAFe (Scaled Agile Framework)

Large-scale application of agile across an organization.


A safe-to-fail experiment is one that is designed to have only limited impact on the system or the plan in the event of failure.


An iterative timeboxed approach to product delivery that is described as 'a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value'

Scrum master

This is a Scrum role that is responsible for ensuring Scrum is understood and enacted and that the Scrum Team adheres to Scrum theory, practices, and rules.


The application of Kanban or the Kanban method in the context of an existing implementation of Scrum.

senior user

The project board role accountable for ensuring that user needs are specified correctly and that the solution meets those needs.

sensitivity analysis

A technique for testing the robustness of a calculation or model by assessing the impact of varying the input, to reflect the risk that the calculation or model might not be accurate.

spike or spiking

A temporary piece of work used to understand more about a given situation. It may take the form of a prototype or some research and is often used to reduce uncertainty from a technical or customer viewpoint. Experiments are similar.


A fixed timeframe (typically of 2–4 weeks) for creating selected features from the backlog.

sprint zero

A specific sprint at the beginning of a piece of work in order to address many upfront activities (e.g. forming a team, visioning, defining the architecture). Also referred to as iteration zero or (the) discovery (phase).

stage (management stage)

A PRINCE2 term that describes a section of the project that a project manager is managing at any one point in time. It is in effect a high-level timebox and will usually contain one or more lower-level timeboxes such as releases or sprints. The concept of a PRINCE2 stage does not have an exact equivalent commonly used in agile.

stage plan

A detailed plan used as the basis for project management control throughout a stage.

stand- up meeting

A short meeting to assess progress. Typically lasting 15 minutes or less, they involve describing work that has been done, will be done and any problems being encountered.

SWOT analysis

Acronym for 'strengths, weaknesses, opportunities and threats'. A technique to determine favourable and unfavourable factors in relation to business change or current state.

supplier subject matter expert (SSME)

A supplier subject matter expert (SSME) is assigned to the delivery team and provides the appropriate technical skills to build and initially quality check the project's products.

Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS.