Practicing the principles

The seven principles are the foundation of every PRINCE2 project, and they appear in both exams. Foundation tests whether you can name them, state what each requires and recognize which principle an activity supports. Practitioner tests whether you can use them to judge actions in a scenario: an option that breaks a principle is almost never the most appropriate answer, and an option that applies a principle sensibly to the scenario often is. This lesson revises each principle briefly with the points exams most often test, then works through original practice questions at both levels with full analysis. Treat the questions as a workout: attempt each one before reading the reasoning.

The seven principles at a glance

Two cross-cutting points appear in many questions. First, a project is only a PRINCE2 project if all seven principles are applied; using the products and roles without the principles is not PRINCE2. Second, principles are never tailored away. Tailoring changes how a principle is applied, never whether it applies. A small project may review its business justification in a short conversation at a stage boundary rather than a formal document review, but it still reviews it.

Foundation-style practice

These questions test recall and understanding. Use the reading routine from lesson 2: read the stem twice, predict, read every option, eliminate, then choose.

Practitioner-style practice on the treatment plant

The following scenario extract is drawn from Ridgeline Water's treatment plant upgrade, which PRIN-150 used for large-project tailoring. Read it once, then attempt the questions.

Scenario extract. The treatment plant upgrade has an approved business case for a 38 million upgrade over four years, justified by meeting a new regulatory turbidity limit at the lowest whole-life cost. Stage 3 is the main civil works stage. A month into stage 3, the regulator announces that it will accept a different treatment process that would cost 6 million less over the plant's life but would require redesigning the filter building. The project manager, Ana, believes the current design is too advanced to change and plans to mention the news at the next stage boundary in five months. The board's project assurance lead for the business has asked for a lessons log entry about the late regulatory change.

Look at the pattern in these answers. Each one rejects an option that would leave a board decision with the project manager, or delay information the board needs. Principles questions in Practitioner very often turn on who decides and when, which is why the principles of business justification, management by exception and roles appear together so frequently.

Questions about tensions between principles

Some of the hardest Practitioner questions involve two principles pulling in different directions. Tailoring may suggest a lighter process, while management by stages requires a board decision at a boundary. Focus on products may suggest defining every product in detail, while tailoring suggests proportion. The resolution is always the same: apply every principle, choosing the lightest form that still achieves its purpose. A boundary decision can be made in a short meeting; a product description can be a one-paragraph checklist; but the decision and the definition still happen.

Scoring your practice

Dev and Ana both keep scores by principle so that they can see where to revise. The program below summarizes a week of their practice answers and flags any principle where accuracy is below 70 %, which is a useful threshold for targeted revision.

results = {   # principle: (correct, attempted), invented practice data
    "business justification": (11, 14),
    "learn from experience": (9, 10),
    "roles and responsibilities": (10, 15),
    "manage by exception": (12, 15),
    "manage by stages": (8, 9),
    "focus on products": (6, 10),
    "tailor to suit": (9, 12),
}
total_c = sum(c for c, a in results.values()); total_a = sum(a for c, a in results.values())
print(f"overall: {total_c}/{total_a} = {total_c / total_a:.0%}")
for name, (c, a) in sorted(results.items(), key=lambda kv: kv[1][0] / kv[1][1]):
    flag = "  <- revise" if c / a < 0.70 else ""
    print(f"  {name:<27} {c:>2}/{a:<2} {c / a:4.0%}{flag}")

overall: 65/85 = 76%
  focus on products            6/10  60%  <- revise
  roles and responsibilities  10/15  67%  <- revise
  tailor to suit               9/12  75%
  business justification      11/14  79%
  manage by exception         12/15  80%
  manage by stages             8/9   89%
  learn from experience        9/10  90%

Overall accuracy is 76 %, comfortably above the pass mark, but two principles fall below the revision threshold: roles and responsibilities, and focus on products. Revising those two areas for an hour each will usually do more for the final score than another full mock paper.

Ridgeline's city council receives quarterly capital project reports, and the treatment plant's business case review at each stage boundary feeds that report. In exam terms, the council and the utility's executive leadership are part of the business layer, which sets the project's tolerances and receives exception reports when project tolerances are threatened.

Recognizing principle language in options

Options that apply a principle well often contain its language in a natural way: 'review the business case', 'agree tolerances', 'decide at the stage boundary', 'agree the product description first', 'record the lesson', 'tailor the report but keep its purpose'. Options that break a principle often contain the opposite: 'skip', 'without the board', 'until closure', 'start work and define the product later', 'because the plan is approved'. Language alone never decides a question, but it is a useful early signal of which options to test first.