PRINCE2F People: organizations, teams, and leadership Practice Question
When should the Project Board meet?
⚠ Common exam trap
A common misconception is that the Project Board meets regularly (e.g., weekly or daily) like a Scrum daily stand-up, but PRINCE2 specifically limits board meetings to stage boundaries and exception events to preserve management by exception.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
At stage boundaries and when an exception occurs
The Project Board is responsible for key decision points in the PRINCE2 methodology. It meets at stage boundaries to review progress, approve the next stage plan, and ensure continued business justification. It also meets when an exception occurs (i.e., when a stage plan deviates beyond tolerance) to decide on corrective action, such as approving an exception plan or prematurely closing the project.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
At stage boundaries and when an exception occurs
Why this is correct
PRINCE2 mandates Project Board meetings at each stage boundary to authorise the next stage, and whenever an exception is raised, so the Board can decide how to recover. This satisfies the stem's governance requirement for decision points rather than continuous attendance.
- ✗
Only at the end of the project
Why it's wrong here
Meeting only at project closure removes the board's decision points at each stage boundary, so continued business justification and stage authorisation go unchecked. It is tempting as minimal overhead, but end-stage assessments exist precisely to review and authorise the next stage, which a single closing meeting cannot provide.
- ✗
Daily
Why it's wrong here
Daily meetings exceed PRINCE2's tolerance-based governance; the Project Board convenes at end-stage assessments and exception situations, not continuously. It is tempting because frequent checkpoints suit agile delivery, yet daily cadence belongs to the delivery team's stand-ups, not board-level direction.
- ✗
Weekly
Why it's wrong here
A fixed weekly cadence ignores PRINCE2's event-driven governance; the board meets at end-stage assessments, exception reports and ad-hoc when tolerance is forecast to be exceeded. It is tempting because regular intervals feel controlled, yet weekly meetings would not align with stage boundaries or exception triggers.
Go deeper
Related to this question
About these practice questions
This PRINCE2F question is part of Courseiva's 1,189-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PRINCE2F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PRINCE2F exam.