Practitioner scenario analysis

The Practitioner exam is different from the Foundation exam in one important way. Foundation asks whether you know what PRINCE2 says. Practitioner asks whether you can apply it: given a scenario, which action, role, product or tailoring choice is appropriate, and why. That calls for a method of reading scenarios and questions, not just knowledge of the manual. This lesson builds that method; lessons 9 to 11 apply it to the principles, practices and processes, and PRIN-160 covers full mock exams and timing in depth.

The exam in brief

Study guides describe the PRINCE2 7 Practitioner exam as an open-book exam of 150 minutes with 70 marks and a pass mark of 60 %, or 42 marks. The only permitted reference is the official PRINCE2 7 manual, in print or in the approved digital form. Questions are based on a scenario booklet that describes a project, with additional information for some sections. Question styles include one-mark multiple-choice questions and matching questions, often worth several marks, where items from one list are matched with another. Some questions ask whether a proposed action is appropriate and require you to identify the correct reason. Details of the format can change between versions, so candidates should always check the current guidance from the examination institute before sitting the exam.

At roughly two minutes per mark, the exam is not rushed, but it does not leave time to read the manual cover to cover during the exam either. The open book is for checking, not for learning.

A five-step method for scenario questions

Almost every Practitioner question can be tackled with the same five steps. They take a few seconds each once practised, and they prevent the most common errors.

Step 1, locate, means identifying where the project is: which stage, which process is running, who is speaking or acting, and what has just happened. Many wrong answers are good actions at the wrong time, such as producing a lessons report in the middle of a stage or authorizing a work package before the stage is authorized.

Step 2, classify, means deciding what the question is really testing. A question about whether the project manager should accept a change might look like an issues question but actually turn on the project manager's change authority, which is part of organizing and the PID's controls. Classifying tells you where to look in the manual.

Step 3, recall the rule, is where knowledge matters. If you are unsure, the manual is open. The best candidates use it to confirm a specific detail, such as who is responsible for an activity or what a product contains, rather than to search for the topic from scratch.

Step 4, apply to the scenario, is where the scenario's tailoring comes in. If the scenario says the project uses agile delivery with highlight reports every sprint, an option that criticizes the project manager for not producing monthly highlight reports is wrong for this project, even though monthly reports might be normal elsewhere. Roles, authority limits and tolerances in the scenario override general expectations.

Step 5, eliminate and choose, removes options that break a principle, give a decision to the wrong role or level, or use the wrong product. Read the stem again before choosing: questions may ask for the most appropriate action, the least appropriate one, or which statements are true, and misreading the direction of the question is an expensive mistake.

Reading the scenario booklet

The scenario booklet describes the organization, the project's objectives, the people involved and often extracts from management products: part of a business case, a project product description, a risk register or a highlight report. Read it once quickly for the big picture, then return to the relevant section for each question. Useful things to mark on a first read are the delivery approach, any stated tailoring, the board members and their roles, tolerances and authority limits, and anything unusual, such as a regulator, a supplier with its own project manager or a programme above the project.

A worked scenario: the digital card at stage 2

Here is a short scenario in the style of the exam, based on the digital card project from lesson 7. It is followed by three questions and an analysis using the five steps.

Scenario. Harbour City Libraries' digital card project is in stage 2, which builds the account sign-up and wallet pass in four two-week sprints. The PID states that highlight reports are produced at the end of each sprint as a dashboard, that the product owner (the head of collections and digital services, acting for the senior user) can reprioritize backlog items within the stage's scope tolerance, and that the project manager's change authority is 3 thousand per change. Stage 2 has a cost tolerance of 6 thousand. In sprint 3, the vendor reports that the wallet pass needs an extra security certificate costing 4.5 thousand a year. Separately, branch staff ask for a printable temporary card for patrons whose phones are not compatible.

marks = [1] * 40 + [3] * 10              # an illustrative mix: 40 one-mark, 10 three-mark items
total_marks, minutes = sum(marks), 150
read_time, review_buffer = 10, 15
work_time = minutes - read_time - review_buffer
per_mark = work_time / total_marks
print(f"total marks: {total_marks}; working minutes: {work_time}")
print(f"budget: {per_mark:.2f} min per mark -> one-mark item {per_mark:.1f} min, three-mark item {3 * per_mark:.1f} min")
check = [10, 30, 60, 90, 120]
for c in check:
    print(f"  by minute {c + read_time:>3}: about {c / per_mark:.0f} marks attempted")

total marks: 70; working minutes: 125
budget: 1.79 min per mark -> one-mark item 1.8 min, three-mark item 5.4 min
  by minute  20: about 6 marks attempted
  by minute  40: about 17 marks attempted
  by minute  70: about 34 marks attempted
  by minute 100: about 50 marks attempted
  by minute 130: about 67 marks attempted

The budget allows about 1.8 minutes per mark after ten minutes of reading and fifteen of review. A useful habit is to check progress at a few fixed times. If at minute 70 you have attempted fewer than about 33 marks, you are falling behind and should stop searching the manual for marginal details.

Using the manual well

Open-book exams reward preparation of the book, not just the candidate. Candidates commonly tab the sections on principles, the people element, each practice and each process, plus the appendix of management products and the glossary. Some write short page references on the tabs for the most-checked tables, such as the responsibilities for each process activity or the composition of each management product. Rules about what may be written in or attached to the manual are set by the examination institute and should be checked in advance. Whatever the rules, the manual is fastest when you already know roughly what you are looking for.

Candidates in Canada can sit the exam online with remote proctoring or through accredited training organizations, and should check the time zone shown in their booking. Employers that fund certification sometimes expect a record of study time for professional development plans.

Building speed before the exam

Speed in the exam comes from practice with scenarios, not from rereading the manual. A useful routine is to take one scenario from this course each day, write five questions about it in the exam's styles, and answer them a day later without notes, then check the answers against the manual. Writing questions forces you to think like the examiner: what would a plausible but wrong option look like for this situation? Most good distractors are actions that are sensible in general but belong to a different process, a different role or an untailored version of the method. Candidates who can generate such distractors themselves rarely fall for them. Keep a short error log of every question you get wrong, noting which step of the five-step method failed, so that you can see whether your weakness is locating, classifying, recalling or applying.