Project Management Professional / PRINCE2 The Seven Principles Syllabus

What is the minimum number of management stages in a PRINCE2 project, and what are they?

A minimum of two management stages: the initiation stage (where the project is initiated/planned) and at least one further management stage (where the specialist work is delivered).

What is the difference between a management stage and a technical/delivery stage in PRINCE2?

Management stages are partitions of the project for senior-management control purposes, separated by decision points and aligned to commitment of resources. Technical (delivery) stages relate to the techniques/specialist skills used and may overlap; PRINCE2 plans, monitors and controls by management stages, not technical stages.

At the end of each management stage, what does the Project Board do under 'Manage by stages'?

It reviews the End Stage Report and the plan/Business Case for the next stage, then decides whether to authorise the next management stage, continue, or stop the project — exercising go/no-go control.

Which two factors influence how a project is divided into management stages?

How far ahead it is sensible to plan, and where the key decision points need to be on the project — these (along with risk and the planning horizon) determine the number and length of management stages.

What does the 'Manage by exception' principle establish?

A PRINCE2 project has defined tolerances for each project objective, establishing limits of delegated authority. Each management level manages within its tolerances and only escalates to the level above when those tolerances are forecast to be exceeded (an exception).

List the six (or seven) tolerance areas used in 'Manage by exception'.

Time, Cost, Quality, Scope, Risk (risk tolerance/appetite), and Benefit. (Sustainability is added in PRINCE2 7th edition.) These are the aspects of performance for which tolerances can be set.

In 'Manage by exception', what happens when a tolerance is forecast to be exceeded?

The situation is escalated to the next management level up via an exception. For example, a stage forecast to breach tolerance triggers an Exception Report to the Project Board, which may request an Exception Plan.

What efficiency benefit does 'Manage by exception' give senior management?

It avoids the need for senior managers to be constantly involved or attend regular progress meetings; they delegate day-to-day control within tolerances and are only consulted when something significant (an exception) occurs — efficient yet effective use of their time.

Which management products are central to 'Manage by exception' when tolerances are threatened?

The Exception Report (alerts the higher level that tolerance is forecast to be exceeded and recommends a response) and, if requested, the Exception Plan (replaces the plan for the remainder of the stage or project).

What does the 'Focus on products' principle require?

A PRINCE2 project focuses on the definition and delivery of products, in particular their quality requirements. Products are agreed and defined before work to create them is undertaken.

Why does PRINCE2 emphasise defining products before doing the work?

Because a clear, agreed product description (with quality criteria) sets shared expectations, reduces dispute over what is acceptable, supports accurate planning and resourcing, and ensures the project delivers fit-for-purpose outputs rather than just activity.

Which management product captures the agreed definition and quality criteria of a product in PRINCE2?

The Product Description, which defines a product's purpose, composition, derivation, format, quality criteria, quality method and quality responsibilities. The overall product breakdown is captured in the Product Breakdown Structure and Project Product Description.

Distinguish 'output', 'outcome' and 'benefit' in PRINCE2 product terms.

Output — a specialist product delivered to a user. Outcome — the result of the change derived from using the project's outputs. Benefit — the measurable improvement resulting from an outcome, perceived as an advantage by stakeholders.

What does a product-based (rather than activity-based) planning approach allow PRINCE2 to do?

By first identifying the products required and their quality, the project derives the activities, dependencies and resources from the products. This gives clearer scope, better quality control, and acceptance criteria the customer agrees to upfront.

What does the 'Tailor to suit the project' principle state?

PRINCE2 is tailored to suit the project's environment, size, complexity, importance, capability and risk. Tailoring ensures the method relates to the project's context and that controls are based on the project's scale, complexity and risk.

What is the purpose of tailoring PRINCE2?

To ensure the project management method (its processes, themes, roles, management products and terminology) is appropriate to the project context — neither over-engineered (too bureaucratic) nor under-managed (lacking control).

What can be tailored in PRINCE2, and what must NOT be removed?

Processes, themes, roles, management products and language/terminology can all be adapted. However, the seven principles must never be tailored away — they must always be applied, or the project is not PRINCE2.

Where is the approach to tailoring PRINCE2 documented for a project?

In the Project Initiation Documentation (PID), typically supported by/derived from organisational standards; the tailoring decisions and how PRINCE2 will be applied are recorded so they are agreed and visible.

What is the relationship between the seven principles and 'PRINCE2 compliance'?

A project is only PRINCE2 compliant if it applies all seven principles. The principles are the framework that defines what makes a project genuinely PRINCE2 — themes and processes may be tailored, but the principles are mandatory and non-negotiable.

Can a project that uses all PRINCE2 themes and processes but ignores one principle be called a PRINCE2 project? Why?

No. Applying themes and processes is not sufficient. If even one of the seven principles is not applied, the project is not a genuine PRINCE2 project — the principles, applied together, are what define compliance.

Which of the following is mandatory for PRINCE2 compliance: all processes, all themes, or all principles?

All principles. The seven principles are mandatory for compliance, whereas processes and themes can be tailored to suit the project.

From where are the seven PRINCE2 principles derived?

They are derived from lessons learned from both successful and failed projects (good and bad project experiences). This is what makes them self-validating and proven in practice.

Why are the PRINCE2 principles described as 'universal'?

Because they apply to every project regardless of its type, size, organisation, geography or culture — they are not dependent on any particular industry or context.

Why are the PRINCE2 principles described as 'empowering'?

Because they give practitioners added confidence and the ability to influence and shape how the project is managed, supporting professional judgement rather than blind rule-following.

Match the principle to its core question: 'Do we still have a good reason to continue?'

Continued business justification — it ensures there is always a valid, documented reason to keep investing in the project.

Match the principle to its core idea: 'Set tolerances and only escalate when they will be breached.'

Manage by exception — defined tolerances establish limits of delegated authority, and only forecast breaches are escalated upward.

Match the principle to its core idea: 'Break the project into reviewable chunks with go/no-go decisions.'

Manage by stages — the project is planned, monitored and controlled stage by stage with decision points between stages.

Match the principle to its core idea: 'Engage business, user and supplier interests with clear accountability.'

Defined roles and responsibilities — an agreed organisation structure represents the three stakeholder interests and assigns clear responsibilities.

Match the principle to its core idea: 'Define what must be delivered and to what quality before doing the work.'

Focus on products — products and their quality requirements are defined and agreed before the work to create them begins.

Compare 'Manage by stages' and 'Manage by exception': what control aspect does each provide?

Manage by stages provides periodic control — review and decision points at stage boundaries (when to look). Manage by exception provides control within a stage — tolerances that define when to escalate during the stage (how much freedom). Together they give the Project Board efficient control without daily involvement.