Home
Contact
Products
About us
Useful Links
PRINCE2 Exam Guide
Introduction & Getting Ready
Practitioner Exam Structure
Question Difficulty
Question Structure
Useful References
PRINCE2 Master Class
Tailoring PRINCE2


Part-questions will vary in their level of difficulty depending on the learning objective of the test. The difficulty levels are: 

1. Knowledge

2. Comprehension

3. Application

4. Analysis

5. Synthesis

6. Evaluation

The focus of the exam is on application, analysis and evaluation learning objectives.

A summary description of each difficulty level and example syllabus topics it tests is detailed below:

1. Knowledge

This learning level is NOT used in the PRINCE2 Practitioner exam.

2. Comprehension

This is the demonstration of understanding of PRINCE2 concepts. Typically this tests the grasping of meaning and the interpretation of wording that is different from the standard paragraphs in the PRINCE2 manual.

This competency maps to syllabus statements ‘must understand’.

Examples of topics tested include:

•  assessing whether statements are a benefit of a product/ technique/component;

•  identifying which products are updated in a project process or used as input to

   creating/updating a product;

•  matching generic descriptions of PRINCE2 activities to roles;

•  identifying correct descriptions of a product’s content/process activities.

3. Application

Application refers to the ability to apply PRINCE2’s components, techniques and products to a given project situation. This competency maps to the syllabus statements ‘apply a component or technique’, ‘produce’ or ‘demonstrate the application of’.

In the objective test format candidates cannot actually produce products, but this competency can still be tested, for example by using ‘matching questions’ which require the candidate to match statements to the correct product composition heading.

Other possibilities include testing Product Breakdown Structure (PBS)/Product Flow Diagram (PFD) creation by using partially blank diagrams for which candidates have to identify correct products from a list to match the blank product.

Examples of test topics include: 

•  identifying how a product is impacted/updated in a given project situation;

•  matching scenario candidates to organisation roles;

•  identifying suitable customer’s quality expectations/acceptance criteria for a given

   scenario;

•  matching risk responses to risk action types for a given project;

•  identifying the impact on a product of a given scenario situation.

4. Analysis

This is the competency to analyse the use of the method. This is NOT the ability to use analysis techniques such as risk analysis and product based planning – these are tested as an application competency.

Typically this would test the ability to identify errors in the application of PRINCE2 or to identify the aspects of a PRINCE2 component or technique that could be of benefit in a given project situation. 

To answer these kind of questions candidates must have breadth of understanding of the topic, understand how that component/process/technique interacts with other
components/processes/techniques and the implications of this for a given project scenario.

Examples of test topics include: 

•  identifying specific control problems on a project and the changes in control products   that  will address the problems;

•  assessment of errors in a PRINCE2 management product e.g. Quality Plan,  Business Case, End Stage Report, Highlight Report;

•  identifying the errors in a PBS/PFD diagram;

•  identifying specific configuration management problems in a project scenario  situation. 

5. Synthesis

This learning level is NOT used in the PRINCE2 Practitioner exam. 

6. Evaluation 

This is the ability to evaluate or justify the use of the method in a given project situation. It is closely linked to the analysis competency but builds on this by requiring the candidate to explain or justify the recommendations they have made and maps to the syllabus statements ‘understand how to integrate’ and ‘modify or discuss’. 

Examples of test topics include: 

•  identifying reasons for unsatisfactory aspects in project controls;

•  identifying reasons for inadequacies in a PRINCE2 product e.g. Quality Log, PQP;

•  matching explanations to proposals for project controls/staging;

•  identifying reasons for a proposed project organisation or changes to it.

 

 
Top