PRINCE2 7 Foundation study guide

Most exams in this catalogue reward judgement: several options are defensible and you choose the best. PRINCE2 Foundation does not work that way. The method defines its own terms, and the exam checks whether you know them. A question will ask which principle applies, which process produces a particular product, or which role holds a specific responsibility. There is one right answer and it is written down in the manual.

That makes this exam learnable in a way that judgement exams are not. The work is precision, not experience. The trap is the opposite of the PMP trap: instead of overthinking, candidates skim, assume two similar terms mean the same thing, and lose marks on distinctions that are entirely mechanical once learned.

The official weightings are unusually lopsided, and it changes how you should revise. The practices are 60% of the paper, roughly 36 of the 60 questions. Everything else combined is the other 40%. Key concepts is 3%, which is about two questions on the whole paper.

So: if your revision time is limited, spend it on the seven practices. Learning the key concepts section perfectly earns you two marks. Learning the practices section perfectly earns you thirty-six.

PRINCE2 7 was released in September 2023 and is what you will sit. It is not a light refresh, and material written for the 6th edition will actively mislead you:

Read that bar again. Practices alone are more than half the exam. Practices and processes together are 75%. If you learn nothing else properly, learn the seven practices: what each one is for, what it produces, and which role is accountable.

A project is a temporary organisation created for the purpose of delivering one or more business products according to an agreed business case. Note "temporary organisation", not "temporary endeavour". PRINCE2 treats a project as a structure of people with defined roles, which is why organising is one of the seven practices.

Projects are distinguished from business as usual by five characteristics: change, temporary, cross-functional, unique, and uncertainty.

PRINCE2 7 is built from five elements that work together. Learn these five words in order; questions frequently ask which element something belongs to.

A favourite exam distinction, and worth getting exactly right because the three are easy to blur.

The chain runs output leads to outcome leads to benefit. Projects deliver outputs. Benefits are usually realised after the project closes, which is why benefits management continues beyond it.

Manage by exception is the one candidates most often misread. It does not mean escalating problems. It means not escalating anything that stays within agreed tolerance, so management time is spent only where a decision is genuinely needed. Tolerances are set against all seven performance aspects, at project, stage and team level.

Continued business justification is the one that produces the "what should happen next" questions. If the business case is no longer valid, the correct PRINCE2 answer is almost always that the project should be closed, even mid-delivery. Sunk cost is not a justification.

PRINCE2 distinguishes the two deliberately. Leading is about direction, influence and motivation: setting a vision people will follow. Managing is about organising and controlling work so it gets done. A project manager needs both, and the balance shifts with the situation.

The method notes that leadership is not tied to authority. Influence, credibility and the ability to build trust matter more than position, which is why a project manager with no line authority can still lead effectively.

A crucial distinction, and one the exam tests: change management here means helping people adopt a change, not the change control procedure that handles issues and requests for change. Those are different things with confusingly similar names.

Projects produce outputs, but benefits only arrive when people actually work differently. If nobody adopts the new system, the outcome never happens and the benefit is never realised. That is why change management sits alongside delivery rather than after it.

PRINCE2 7 expects awareness of how project teams form and develop, how capability is built, and how motivation is sustained across a temporary organisation where people are often borrowed from elsewhere. The practical point the exam draws on: because a project team is temporary and cross-functional, the effort of forming it, agreeing how it will work, and disbanding it deliberately at closure is part of the work, not an overhead.

Establishes and maintains the justification. Owned by the executive, who is accountable for it throughout. Developed in outline during starting up a project, detailed during initiating a project, and reviewed at every stage boundary, because justification must remain valid, not merely have existed once.

The benefits management approach defines how and when benefits will be measured, and it survives the project: benefits are usually realised after closure, so someone must own their measurement afterwards.

Defines the temporary organisation. The structure has four levels, and the exam tests them constantly.

The project board holds three roles representing the three stakeholder interests: the executive (business interest, ultimately accountable, and the only role that cannot be shared), the senior user (specifies needs and is accountable for realising benefits), and the senior supplier (provides resources and technical expertise). Project assurance is the board's independent check and cannot be delegated to the project manager. Project support is administrative help and may be shared or delegated.

PRINCE2 plans are product-based. You define the products first, then the activities needed to create them, then the effort. The four plan types: project plan (the whole, owned by the board), stage plan (one management stage, the project manager's working document), team plan (optional, for a work package), and exception plan (replaces a plan that is forecast to breach tolerance, and is approved at the level that set the tolerance).

Product-based planning has four steps: write the project product description, create the product breakdown structure, write product descriptions, then create the product flow diagram showing the sequence and dependencies.

Two ideas the exam loves to separate. Quality planning defines what "fit for purpose" means: quality criteria go into product descriptions, and acceptance criteria into the project product description. Quality control checks that products meet them, and records results in the quality register.

Also distinguish quality assurance (an organisational function, independent of the project, checking the project is being run properly) from project assurance (the project board's own independent check). They are different, and questions exploit the similarity.

A risk is an uncertain event that, should it occur, will affect the achievement of objectives. Risks are threats (negative) or opportunities (positive). The recommended procedure has five steps: identify, assess, plan, implement, with communicate running throughout rather than as a final step.

Risk owner manages and monitors a risk; risk actionee carries out the response action. They may be the same person but are defined separately, and the exam asks.

An issue is anything happening now that needs addressing, as opposed to a risk, which might happen. Three types: a request for change, an off-specification (a product that does not or will not meet its specification), and a problem or concern (anything else).

Handled either formally in the issue register, or informally in the daily log if minor. Change authority is the role that decides on requests for change, and a change budget may be set aside to fund approved ones.

Answers whether the project is on track and should continue. It rests on tolerances (permitted deviation before escalation, set against all seven performance aspects at project, stage and team level) and on regular reporting.

Every PRINCE2 project has at least two management stages: the initiation stage and at least one delivery stage. That follows directly from the manage by stages principle, and it is a frequent exam check.

The board's decision points sit at stage boundaries, which is what makes stages the control mechanism rather than an administrative convenience.