PRINCE2 Agile Practitioner key terms

A tailored version of the PRINCE2 method that keeps its principles, themes and process structure while integrating agile behaviours and techniques, so projects can combine governance with iterative, incremental delivery of products.

An approach to work that favours short cycles of delivery, frequent feedback, empowered teams and the ability to change direction quickly, rather than doing extensive up-front planning before any value is produced.

A way of working in which decisions are based on what is actually observed and measured as work progresses, rather than on predictions made in advance, allowing plans to be adjusted as real evidence accumulates.

A fixed, short period of work during which a team builds and reviews a portion of the product, ending with something that can be inspected and used to inform what happens next.

The usable, finished portion of the product produced at the end of a cycle of work, which adds to what has already been completed and can be demonstrated, tested or released.

A fixed period of time that cannot be extended; work is scoped to fit the available time rather than allowing time to stretch to fit the work, which keeps delivery rhythm predictable.

A style of leading in which the manager's main job is to remove obstacles, protect the team from distraction and create conditions for others to succeed, rather than issuing detailed instructions and controlling activity.

A group that decides for itself how to carry out its work and who does what, within agreed boundaries and objectives set by the wider organisation, rather than waiting for a manager to allocate tasks.

Giving people the authority and confidence to make decisions about their own work without seeking approval at every step, balanced by clear accountability for the outcomes they deliver.

The observable ways of working expected in agile delivery, such as transparency, collaboration, honesty about progress, willingness to adapt and respect for people, which support the method's principles in daily practice.

Making work, progress, problems and decisions visible to everyone who needs to see them, so that trust can be built and informed choices can be made based on real information.

Working jointly across roles and disciplines, including business and delivery people, so that decisions are made with shared understanding rather than handed across organisational boundaries in a series of documents.

A PRINCE2 Agile diagnostic tool that assesses a project against eight focus areas, showing where agile practices are strong or weak so that tailoring decisions can be targeted at the areas needing most attention.

The eight aspects of agile delivery assessed by AgileSHAPE: agility, transparency, flexibility, resilience, lean startup thinking, collaboration, stakeholder engagement, and self-organising teams.

A structured review of how well agile practices are working on a project, used to identify strengths and weaknesses and to agree improvements, often carried out using the AgileSHAPE focus areas.

The capability to respond quickly and effectively to change by adjusting plans, priorities and ways of working, while still maintaining sufficient control and direction over the work.

The deliberate design of plans, roles and products so that they can be changed without disproportionate disruption, for example by prioritising what is delivered and when.

The ability of a team and project to absorb setbacks, recover from problems and keep delivering, supported by realistic planning, cross-skilled people and a culture that treats failure as learning.

An approach that favours small, cheap experiments and early feedback over large up-front investment, so that ideas can be tested and either developed further or dropped before significant cost is incurred.

Actively identifying the people affected by or interested in the project and working with them continuously so their needs inform decisions and their support is maintained throughout delivery.

Adapting the method's principles, themes, processes and management products to suit the size, risk and context of a particular project, while keeping the principles intact and documenting what was changed and why.

The justification for the project, setting out expected benefits, costs, risks and timescales; in agile delivery it is reviewed frequently so that continued investment is confirmed as understanding improves.

The measurable improvements or value the organisation expects to gain from the project's outputs, which should be defined clearly enough to be assessed and, where possible, realised incrementally.

The agreed amount of deviation from plan that a role may allow before the situation must be escalated, for example permitted variation in time, cost, scope, quality, risk or benefits.

A control approach in which decision-making is delegated within agreed tolerances, and higher authority is involved only when a forecast breach of those tolerances is predicted.

The group accountable for the project's direction and success, typically representing business, user and supplier interests; it makes key decisions, approves plans and manages escalation from the project manager.

A statement of a product's purpose, composition, quality criteria and quality method, used to agree what will be produced and how it will be judged as acceptable.

A short, plain-language statement of a need written from the perspective of the person who wants it, describing who wants what and why, so that it can be discussed and refined by the team.

Deciding the order in which requirements will be worked on, usually driven by value, risk and dependency, so that the most important things are delivered earliest and least valuable work can be dropped.

The smallest version of a product that delivers enough value to be released and tested with real users, allowing learning to begin early before further investment is committed.

An agreed checklist describing what must be true for a piece of work to be considered complete, ensuring everyone shares the same quality expectations and preventing unfinished work being counted as delivered.

The degree to which a product meets agreed requirements and is fit for its intended use; in agile delivery it is built in through shared criteria and frequent checking rather than inspected only at the end.

A regular team meeting after a period of work in which members review how they worked together, identify improvements and agree actions to try in the next cycle.

A highly visible display of key project information, such as progress, impediments or plans, placed where the team and stakeholders can see it easily so that status is transparent without lengthy reporting.

A technique for visualising the flow of work across stages, limiting how much work is in progress at once and exposing bottlenecks so that throughput and predictability improve.

An agile framework built around fixed-length iterations, a prioritised backlog, defined team roles and regular review and reflection events, often used within a PRINCE2 project to organise delivery work.

The worth of what is delivered, judged by the benefits it brings to the organisation and users relative to its cost; agile delivery aims to release value early and continuously rather than only at the end.