PRINCE2 Foundation Practice Test

PRINCE2 Project Management Foundation (Version 7)

PRINCE2 Foundation overview

  • 200 practice questions
  • 32 flashcards
  • 4 study guide topics
  • 40 key terms

What you'll study

  • Principles25%
  • People25%
  • Practices25%
  • Processes25%

PRINCE2 Project Management Foundation (Version 7) is an entry-level certification in the PRINCE2 project management method, administered by PeopleCert. PeopleCert describes it as a way to "Learn the principles of a best-practice method, trusted by over 2M professionals worldwide, and build a strong foundation for a career in project management." It suits aspiring and practising project managers, project team members, PMO and assurance staff, and anyone who needs a shared vocabulary for managing projects in a controlled, stage-by-stage way. The syllabus is organised into four broad areas: the principles that make a project a PRINCE2 project, the people aspects of leading and working with teams, the practices that supply the method's techniques and management products, and the processes that describe the flow of a project from start to closure. Preparation can be self-study or through an Accredited Training Organisation, and PeopleCert lists self-study, e-learning, virtual and in-person class options, with or without official mock exams. Because the exam tests breadth of understanding across the whole method rather than depth in one area, candidates typically work through the official manual systematically, then use mock papers to find gaps. This page and the questions that follow are independent study material and are not affiliated with, endorsed by, or produced by PeopleCert.

Common mistakes

Selecting answers that say a principle can be adapted, scaled, or dropped for small projects - for example, agreeing that 'continued business justification' can be relaxed on a short project, or that only 'some' of the seven principles need to apply.

The whole point of tailoring is made in the Practices/Processes material, so candidates carry the idea 'PRINCE2 is scalable' across to the Principles and assume the seven principles are equally adjustable.

What to do instead

Learn the seven principles word-for-word with their one-line definitions, and memorise the rule 'principles are mandatory and never tailored; only the practices, roles and processes are tailored'. Whenever an option offers an exception to a principle, eliminate it.

In scenario questions asking 'which principle is being demonstrated', choosing the practice, role, or product that appears in the scenario (e.g. picking 'business case' or 'manage by exception' when the correct answer is 'continued business justification').

The scenario dialogue and the option list use the same vocabulary as the practices, and 'manage by exception' in particular sounds like a description of an exception report rather than a behavioural principle.

What to do instead

Rehearse a behaviour-test for each principle ('is the answer a way of thinking/behaving, or a thing someone produces?'). If the option names a document, a role, a tolerance or a process activity, it is not the principle. Practise 20 short scenarios and label the principle before looking at the options.

Assigning accountability to the wrong role - for example, saying the Project Manager is accountable for realisation of benefits, that the Executive can delegate overall accountability for the project, or that the Senior Supplier signs off the achievement of benefits.

In day-to-day project life the Project Manager does most of the visible work, so candidates transfer real-world habit onto the exam instead of using the PRINCE2 accountability split.

What to do instead

Build a one-page role chart: Executive = accountable for the project and the Business Case; Senior User(s) = accountable for user needs and benefits realisation; Senior Supplier = accountable for supplier resources and quality of supplier products; Project Manager = responsible for day-to-day management within tolerances. Test every People/Organisation question against this chart.

Treating 'People' questions as general leadership or HR trivia and picking the option that sounds most collaborative (e.g. 'involve the whole Project Board in every issue', 'hold a team-building day to resolve a performance problem') rather than the PRINCE2-consistent behaviour.

People-domain stems read like soft-skills scenarios, and candidates switch off their PRINCE2 filter because the question does not mention a process or a product.

What to do instead

Filter every People option through two tests: (1) does it fit manage by exception - escalate only when a tolerance is forecast to be exceeded; (2) does it match the role's defined accountability? Discard options that require the Board to make operational decisions or that rely on generic morale-building with no defined-role or communication-management hook.

Confusing which management product is created or updated in which process - e.g. placing the Project Brief in Initiating a Project, the PID in Starting up a Project, or mixing the Lessons Log with the Lessons Report and the Checkpoint Report with the Highlight Report.

The products appear across several processes and the question stems often ask 'which process is this activity part of?' while the options list products, so candidates match on keyword familiarity rather than on sequence.

What to do instead

Make a timeline table of products against processes: Starting up a Project produces the Project Brief, outline Business Case and Daily Log; Initiating a Project produces the PID, benefits management approach and communication management approach; Lessons Log is created in Starting up and maintained throughout, while Lessons Reports are produced at stage end and project end. Learn who receives each report (Checkpoint = Project Manager from Team Manager; Highlight = Project Board from Project Manager).

Getting the tolerance hierarchy wrong - for example, saying the Project Manager sets stage tolerances, that the Project Board sets project tolerances from scratch, or that a forecast breach of a stage tolerance is escalated straight to corporate/programme management.

All six tolerance types and three organisational levels are taught together, and candidates learn 'tolerances exist' without learning the direction in which they are delegated and escalated.

What to do instead

Memorise the delegation chain and the escalation chain: corporate/programme sets project tolerances (the Board may refine them) → Board sets stage tolerances for the Project Manager → Project Manager sets team/work-package tolerances for the Team Manager. Escalation mirrors it: stage tolerance forecast breach goes to the Project Board as an exception; project tolerance forecast breach is escalated by the Board to corporate/programme.

Mixing up quality planning, quality assurance and quality control, or misassigning quality review responsibilities - e.g. saying the Project Manager performs quality assurance, that product descriptions are produced during quality control, or that quality assurance is part of the Project Manager's team.

The words 'quality' and 'assurance' appear in several places (project assurance roles, the Quality practice, quality review technique), and candidates blur the terms because they never separated planning/assurance/control into three distinct purposes.

What to do instead

Learn the three-part split: quality planning defines what quality means and how it will be achieved (quality management approach, product descriptions, quality register); quality assurance is an independent check that the quality approach is being followed (not done by the Project Manager); quality control is the execution of the quality methods on products (quality review, testing) and updates the quality register. For every quality question, first ask 'plan, check the method, or check the product?'.

Attributing Project Board decision activities to the wrong process - for example placing 'authorise the project', 'authorise a stage or exception plan' or 'authorise project closure' inside Initiating a Project or Controlling a Stage, or expecting the Project Manager to authorise a stage.

The processes run in parallel and the Board's activities are short, so candidates absorb them into the phase where they notice them rather than into Directing a Project, which is the Board's own process.

What to do instead

Learn Directing a Project as 'the Board's process with the authorise verbs': authorise initiation, authorise the project, authorise a stage or exception plan, give ad hoc direction, authorise project closure. If an option has the Project Manager authorising a stage, an exception plan or closure, eliminate it automatically.

Confusing Managing a Stage Boundary with Controlling a Stage - placing 'authorise a work package', 'review work package status' or 'take corrective action' in Managing a Stage Boundary, or believing an exception plan is prepared inside Controlling a Stage.

Both processes involve the Project Manager reacting to work-package information, and Managing a Stage Boundary only happens at stage end (or when an exception plan is needed), so candidates merge the two.

What to do instead

Anchor each process to its trigger: Controlling a Stage is continuous, work-package-driven, and the Project Manager's day-to-day process; Managing a Stage Boundary is triggered only by the end of a stage or a request to prepare an exception plan, and its output is the End Stage Report, the next Stage Plan, and an updated PID and Business Case for Board approval. Classify any option by asking 'is this routine delivery control or stage-end preparation?'.

Getting Starting up a Project and Initiating a Project out of order - e.g. saying the full Business Case, the PID or the benefits management approach is produced in Starting up a Project, or that the Project Brief is created in Initiating a Project.

Both processes happen before delivery starts and share products (Business Case, project approach, team roles), so candidates memorise 'the front end' as a single block instead of two distinct decision points.

What to do instead

Learn the two questions: Starting up a Project answers 'is this project worth initiating at all?' and outputs the Project Brief, outline Business Case, project approach and initiation stage plan; Initiating a Project answers 'how will we actually do it?' and outputs the PID, benefits management approach, communication management approach and the first Stage Plan. If an option puts a detailed planning artefact in Starting up a Project, it is wrong.

Exam requirements can change. Confirm current details with the exam provider.

PRINCE2 Foundation practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Principles

    How many principles does PRINCE2 define?

    1. Four
    2. Nine
    3. Six
    4. Seven Correct answer.

    Explanation

    PRINCE2 rests on seven principles: continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to suit the project environment. These principles are the foundation that the themes, processes and products are built on.

  2. Question 2Principles

    Which principle requires that a project has a justifiable reason for starting and that this reason remains valid throughout its life?

    1. Focus on products
    2. Manage by stages
    3. Continued business justification Correct answer.
    4. Manage by exception

    Explanation

    Continued business justification requires a justifiable reason for the project that is documented in the business case and re-assessed as the project progresses. If the justification lapses, the project should be stopped or re-scoped.

  3. Question 3Principles

    Which principle requires the project team to seek, record and act on knowledge gained from earlier work?

    1. Manage by exception
    2. Learn from experience Correct answer.
    3. Focus on products
    4. Defined roles and responsibilities

    Explanation

    Learn from experience requires that lessons are sought from previous and similar projects, recorded as they arise, and then acted upon during the project and passed on afterwards. It applies to everyone involved, not just the project manager.

  4. Question 4Principles

    Which principle ensures that accountability for the project is allocated to named people within an agreed structure?

    1. Focus on products
    2. Defined roles and responsibilities Correct answer.
    3. Manage by stages
    4. Continued business justification

    Explanation

    Defined roles and responsibilities requires an explicit organisation structure with agreed roles that engage the business, user and supplier interests. It ensures that accountability for decisions and deliverables sits with identifiable people.

  5. Question 5Principles

    Which principle requires that the project is planned, monitored and controlled on a stage-by-stage basis?

    1. Learn from experience
    2. Manage by stages Correct answer.
    3. Manage by exception
    4. Tailor to suit the project environment

    Explanation

    Manage by stages means the project is broken into management stages, each with its own plan and decision point. This gives the project board control points at which progress is reviewed and continuation is approved.

  6. Question 6Principles

    The focus on products principle directs the project to concentrate on which of the following?

    1. The lessons recorded by previous similar projects
    2. The sequence of activities set out in the stage plan
    3. The products required with agreed quality criteria Correct answer.
    4. The tolerances delegated by the project board

    Explanation

    Focus on products means the project is driven by the definition and delivery of products, particularly their quality requirements. Activities and plans are derived from what must be delivered, not the other way round.

  7. Question 7Principles

    What does the principle 'tailor to suit the project environment' require?

    1. PRINCE2 is adapted to the project's size, complexity, risk and environment Correct answer.
    2. Every project must use the same set of PRINCE2 documents without change
    3. The seven principles may be replaced by locally agreed organisational standards
    4. Stages that are considered unnecessary may be dropped from the project

    Explanation

    Tailoring means adapting the processes, themes, roles and documentation so that they are proportionate to the project's scale, complexity, importance and risk. The principles themselves are never tailored away; only the way they are applied is adapted.

  8. Question 8Principles

    Which principle allows a project board to delegate authority within agreed limits, so that only deviations beyond those limits are escalated?

    1. Manage by exception Correct answer.
    2. Defined roles and responsibilities
    3. Manage by stages
    4. Focus on products

    Explanation

    Manage by exception sets tolerances for each project objective, creating the limits of delegated authority at each management level. Work proceeds within those limits and only forecast breaches are escalated as exceptions.

  9. Question 9Principles

    A project uses PRINCE2 processes, themes and products but leaves out one of the seven principles. What does this mean for the project?

    1. The omission is acceptable if the project board formally approves it
    2. It is not applying PRINCE2, because all seven principles must be applied Correct answer.
    3. The omitted principle may be replaced by a locally written equivalent
    4. It can still be described as PRINCE2 because the documentation is the same

    Explanation

    The seven principles are mandatory and must all be evident in a PRINCE2 project; using the processes and documents alone is not sufficient. If a principle is not applied, the project cannot claim to be following PRINCE2.

  10. Question 10Principles

    Under the continued business justification principle, when should the business case be reviewed and, if necessary, updated?

    1. Only at the end of the project, as part of the final lessons report
    2. Only at the start of the project, when the business case is first written
    3. At each stage boundary, and whenever a change or exception may affect it Correct answer.
    4. Only when the project board explicitly asks for a review of it

    Explanation

    The business justification must remain valid, so the business case is reviewed and updated at every stage boundary and whenever a change or exception could affect the costs, risks or benefits. This allows the board to decide whether continuation is still justified.

  11. Question 11Principles

    A stage's forecast cost is about to exceed its cost tolerance. What does the manage by exception principle require the project manager to do?

    1. Escalate to the project board by raising an exception Correct answer.
    2. Wait until the end of stage assessment to report it
    3. Reduce quality criteria to bring costs back within tolerance
    4. Absorb the overspend from another stage's budget

    Explanation

    Under manage by exception, a forecast breach of an agreed tolerance is escalated to the level that set that tolerance, in this case the project board, by raising an exception. The project manager must not take decisions reserved for the board, such as changing scope or quality.

  12. Question 12Principles

    Which approach is most consistent with the focus on products principle?

    1. Describe the products only when they are handed over to the customer
    2. Plan the activities first and then identify what each activity will produce
    3. Define each product and its quality criteria before planning the activities to deliver it Correct answer.
    4. Focus on the deliverables listed in the supplier contract and nothing else

    Explanation

    Focus on products means products are identified, described and given quality criteria before the work needed to create them is planned. Plans and activities are then derived from the product descriptions.

  13. Question 13Principles

    When should lessons be sought in a project that applies the learn from experience principle?

    1. Only during the initiation stage, when the lessons log is first created
    2. Whenever the project board asks to see the lessons log during a stage
    3. Only at the end of the project, when the final report is prepared
    4. At the start, throughout the project, and when passing lessons on Correct answer.

    Explanation

    Lessons should be sought from previous projects before work begins, captured as they arise during the project, and passed on to the organisation at the end. The principle is continuous rather than a single event.

  14. Question 14Principles

    Under the defined roles and responsibilities principle, which three stakeholder interests must be represented on the project board?

    1. Customer, supplier and regulator
    2. Business, user and supplier Correct answer.
    3. Business, project manager and supplier
    4. Sponsor, user and team manager

    Explanation

    The project board must represent the business, user and supplier interests so that decisions reflect viability, fitness for purpose and the feasibility of delivery. These interests are represented by the Executive, Senior User(s) and Senior Supplier(s).

  15. Question 15Principles

    Why does PRINCE2 divide a project into management stages?

    1. To provide decision points at which the board can review progress and approve continuation Correct answer.
    2. To make sure that the number of stages matches the number of delivery teams
    3. To reduce the amount of documentation required on smaller projects
    4. To avoid the need to maintain a business case after the initiation stage

    Explanation

    Management stages create control points at which the board can review the end stage information, reassess the business case and authorise the next stage. This keeps investment under review as uncertainty reduces.

  16. Question 16Principles

    Which statement best describes tailoring under PRINCE2?

    1. Removing stages and documents that the project board considers to be low value
    2. Adapting the method to the project's scale and risk while applying all the principles Correct answer.
    3. Creating organisation-specific principles to replace the PRINCE2 ones
    4. Selecting, from the seven principles, those that this particular project will apply

    Explanation

    Tailoring adapts the processes, themes, roles and documentation to the project's size, complexity, risk and environment. Crucially, all seven principles still apply; tailoring changes how they are applied, not whether they are applied.

  17. Question 17Principles

    Which statement best reflects the defined roles and responsibilities principle?

    1. The project board must include the project manager so that decisions can be made quickly
    2. Those who direct, manage and deliver are identified with accountabilities agreed and separated Correct answer.
    3. Every project must have a full-time project manager and a full-time support office
    4. Roles are defined at the start of the project and cannot change during it

    Explanation

    The principle requires an explicit structure in which the directing, managing and delivering roles are identified with agreed responsibilities. Separating these roles preserves accountability and ensures the board can hold the project manager to account.

  18. Question 18Principles

    Which role is accountable for the business case, and therefore for the continued business justification principle?

    1. Project Assurance
    2. The Senior User
    3. The Project Manager
    4. The Executive Correct answer.

    Explanation

    The Executive is accountable for the business case and owns the justification for the project. The project manager prepares and maintains the business case, and other roles contribute, but accountability rests with the Executive.

  19. Question 19Principles

    What is the purpose of the lessons log?

    1. To record the issues that the project board has escalated
    2. To record lessons that may be useful to the project and to future projects Correct answer.
    3. To record the changes made to the business case
    4. To record the quality checks that are carried out during each stage

    Explanation

    The lessons log captures lessons identified as the project progresses, together with any lessons brought in from earlier work, so they can be acted upon now and passed on later. It supports the learn from experience principle.

  20. Question 20Principles

    In PRINCE2, what is an exception?

    1. Any problem that a team member reports to the project manager during a stage
    2. A deviation that is discovered only after the tolerance has already been breached
    3. Any change that a stakeholder requests after the project has been baselined
    4. A forecast situation where a tolerance will be exceeded without corrective action Correct answer.

    Explanation

    An exception is a situation where it can be forecast that a tolerance will be exceeded, which triggers escalation to the management level that set the tolerance. Acting on forecasts gives the board time to decide on corrective action.

  21. Question 21Principles

    A small, low-risk project's board decides to remove all stage boundaries so the project runs as one stage with a single report at the end. Which principle is being compromised, and why?

    1. Manage by exception, because tolerances can only be agreed at stage boundaries
    2. Tailor to suit the project environment, because small projects should have fewer controls
    3. Manage by stages, because a PRINCE2 project must have at least two management stages Correct answer.
    4. Continued business justification, because the business case cannot be reviewed without stages

    Explanation

    Tailoring can reduce the number of stages and lighten control, but a PRINCE2 project still needs at least an initiation stage and one further management stage. Without stage boundaries the board loses the decision points at which progress and justification are reviewed.

  22. Question 22Principles

    An organisation adopting PRINCE2 wants to drop manage by exception and instead escalate every issue to the board. What is the correct PRINCE2 position?

    1. Acceptable, because principles may be tailored to fit local governance arrangements
    2. Acceptable, provided the change is approved by corporate or programme management
    3. Acceptable, provided the change is recorded in the lessons log and approved by the board
    4. Not acceptable, because all seven principles must be applied; only their application is tailored Correct answer.

    Explanation

    The principles are mandatory and cannot be removed or replaced, whatever governance arrangements an organisation uses. Tailoring may change how tolerances are set and reported, but delegated authority within tolerances must still operate.

  23. Question 23Principles

    A team plans its work as a list of activities and writes acceptance criteria only after each deliverable has been produced. Which principle is most clearly breached?

    1. Learn from experience, because acceptance criteria should be taken from lessons
    2. Manage by stages, because acceptance criteria are agreed at stage boundaries
    3. Defined roles and responsibilities, because only the board may define acceptance criteria
    4. Focus on products, because quality criteria must be defined before the work is planned Correct answer.

    Explanation

    Focus on products requires products to be identified and described, with their quality criteria, before the activities needed to create them are planned. Writing criteria after delivery removes the basis for quality control and acceptance.

  24. Question 24Principles

    A project's business case shows that costs now outweigh the expected benefits, but the board continues because the project is politically sensitive. Which principle is breached, and what should happen?

    1. Continued business justification; the project should be stopped or re-scoped so that it is justifiable Correct answer.
    2. Tailor to suit the project environment; the business case should be tailored to the political context
    3. Manage by exception; the board should escalate the decision to corporate management
    4. Learn from experience; the decision should be recorded in the lessons log

    Explanation

    Continued business justification requires that the justification remains valid, and a business case that no longer shows benefits outweighing costs removes that justification. If the justification cannot be restored through change, the project should be stopped.

  25. Question 25Principles

    Which statement correctly describes how tolerances are set under manage by exception?

    1. The board sets stage tolerances for the project manager, who sets team tolerances Correct answer.
    2. Team managers agree their tolerances directly with corporate or programme management
    3. Tolerances are set once at project level and then applied uniformly to every stage
    4. The project manager sets stage tolerances for the board, which sets team tolerances

    Explanation

    Tolerances are agreed at every level of the management structure: the board agrees project and stage tolerances with the project manager, who agrees team-level tolerances with team managers. Each level then works within its own tolerances and escalates only forecast breaches upward.

  26. Question 26Principles

    Which of the following is one of the seven PRINCE2 principles?

    1. Manage by exception Correct answer.
    2. Manage by stakeholders
    3. Manage by deliverables
    4. Manage by objectives

    Explanation

    The seven principles are continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to suit the project environment. Manage by exception is the only option taken from that list.

  27. Question 27Principles

    How are the PRINCE2 principles best described?

    1. Documents produced during project initiation
    2. Mandatory obligations that guide project management Correct answer.
    3. Optional guidelines that may be adopted when convenient
    4. Techniques used only when planning a stage

    Explanation

    The principles are mandatory; a project only uses PRINCE2 if all seven are applied. They guide how the project is managed rather than being optional techniques or documents.

  28. Question 28Principles

    Which management product provides the justification for a project and is central to the continued business justification principle?

    1. The lessons log
    2. The project plan
    3. The business case Correct answer.
    4. The project's risk register

    Explanation

    The business case records the reasons for the project, expected benefits, costs, risks, and timescale. It is reviewed throughout so the project continues only while it remains justified.

  29. Question 29Principles

    At the start of a project, which action best applies the learn from experience principle?

    1. Asking the project board to approve the lessons log
    2. Waiting until project closure to record lessons
    3. Recording only lessons that affect cost
    4. Reviewing lessons from similar past projects Correct answer.

    Explanation

    The principle requires lessons to be sought and applied from the beginning, not just at the end. Reviewing relevant past projects helps avoid repeating problems and improves planning.

  30. Question 30Principles

    Which project board role represents the business interest in a PRINCE2 project?

    1. Senior supplier
    2. Project assurance
    3. Executive Correct answer.
    4. Senior user

    Explanation

    The executive is accountable for the project and represents the business interest, ensuring it delivers value for money. The senior user represents users and the senior supplier represents suppliers.

  31. Question 31Principles

    What is the minimum number of management stages in a PRINCE2 project?

    1. One
    2. Four
    3. Two Correct answer.
    4. Three

    Explanation

    A PRINCE2 project must have at least two management stages: an initiation stage and at least one further stage for delivery work. This gives the board at least one stage boundary at which to review and decide whether to continue.

  32. Question 32Principles

    Which of the following is one of the six aspects for which tolerances are set under the manage by exception principle?

    1. Morale
    2. Technology
    3. Risk Correct answer.
    4. Culture

    Explanation

    Tolerances are set for time, cost, scope, quality, risk, and benefits. Risk is the only option in that list, and it allows the board to specify how much uncertainty can be accepted before escalation.

  33. Question 33Principles

    What is the main purpose of a product description in PRINCE2?

    1. To define a product's purpose, composition, and quality criteria Correct answer.
    2. To replace the business case for small projects
    3. To list the project's stakeholders
    4. To record the project's tolerances

    Explanation

    A product description defines what a product is, what it is made of, and the quality criteria it must meet. This supports the focus on products principle by making the deliverable and its quality requirements explicit.

  34. Question 34Principles

    Where is a project's tailoring approach normally recorded?

    1. In the quality register for the current stage
    2. In the daily log
    3. In the project initiation documentation Correct answer.
    4. In the risk register

    Explanation

    The project initiation documentation records how PRINCE2 has been tailored for the project, including changes to processes, themes, roles, or management products. This makes the tailoring visible and auditable.

  35. Question 35Principles

    At a stage boundary, the project board reviews the business case before deciding whether to continue. Which principle is being applied most directly?

    1. Learn from experience
    2. Focus on products
    3. Continued business justification Correct answer.
    4. Defined roles and responsibilities

    Explanation

    Reviewing the business case at each stage boundary checks that the project is still justified. If the justification has weakened, the board may change or stop the project.

  36. Question 36Principles

    A project produces a lessons report at closure. What should happen to this report?

    1. It should be added to the corporate lessons repository for future projects Correct answer.
    2. It should be filed with the project's daily log and archived with the project files
    3. It should be sent only to the project manager for personal reference
    4. It should be deleted once the project board has approved closure

    Explanation

    The learn from experience principle requires lessons to be shared beyond the project. A lessons report should be added to the organization's lessons repository so future projects can benefit.

  37. Question 37Principles

    Why does a PRINCE2 project board include a senior user role?

    1. To manage the project team on a day-to-day basis
    2. To provide independent assurance to the executive
    3. To approve the project's budget on behalf of the finance department
    4. To represent users' interests and confirm their needs are met Correct answer.

    Explanation

    The senior user represents the users' interests and is responsible for specifying their needs and confirming that products meet them. This reflects the business, user, and supplier interests required by defined roles and responsibilities.

  38. Question 38Principles

    Who appoints the project manager in a PRINCE2 project?

    1. The project board as a whole
    2. The executive Correct answer.
    3. The senior user
    4. Project assurance

    Explanation

    The executive is appointed first and then appoints the other project board members and the project manager. This is part of the defined roles and responsibilities principle.

  39. Question 39Principles

    What is decided at an end stage assessment?

    1. Whether the project manager should be replaced
    2. Whether to continue and approve the next stage plan Correct answer.
    3. Whether the quality register should be closed
    4. Whether the business case should be written for the first time

    Explanation

    At an end stage assessment the board reviews progress and the updated business case, then decides whether to continue and approves the next stage plan. This is how manage by stages gives the board control points.

  40. Question 40Principles

    What is the purpose of agreeing work package tolerances with a team manager?

    1. To transfer accountability for the business case to the team manager
    2. To set the project board's overall stage tolerances
    3. To remove the need for the project manager to monitor progress
    4. To allow the team manager to manage work within agreed limits Correct answer.

    Explanation

    Work package tolerances delegate limited authority to the team manager. The team manager manages within those limits and escalates only if a forecast exceeds them, applying manage by exception at the lowest appropriate level.

  41. Question 41Principles

    How does the focus on products principle help to manage quality?

    1. It guarantees that every product will be completed within cost tolerance
    2. It removes the need for a quality register
    3. It allows quality checks to be performed only at project closure
    4. It defines quality criteria for each product before work begins Correct answer.

    Explanation

    Focus on products requires each product and its quality criteria to be defined before work starts. This allows the team to plan the required quality activities and to judge acceptance objectively.

  42. Question 42Principles

    On what should the tailoring of PRINCE2 be based?

    1. The amount of budget remaining at the start of every stage
    2. The number of stakeholders who regularly attend board meetings
    3. The project's size, complexity, importance, capability, and risk Correct answer.
    4. The personal preferences of the project manager alone

    Explanation

    Tailoring should reflect the project's context, including its size, complexity, importance, capability, and risk. This ensures the method is proportionate without removing the principles.

  43. Question 43Principles

    What does the senior supplier role represent on a PRINCE2 project board?

    1. The interests of the end users and their acceptance criteria
    2. The interests of the project manager and the team
    3. The interests of the finance department and the project's funding
    4. The interests of those designing and producing the products Correct answer.

    Explanation

    The senior supplier represents the supplier interest and is accountable for supplier resources and the feasibility of the products. This ensures the board has the supplier perspective when making decisions.

  44. Question 44Principles

    Which PRINCE2 principle is most directly supported by creating a product breakdown structure?

    1. Focus on products Correct answer.
    2. Continued business justification
    3. Learn from experience
    4. Manage by exception

    Explanation

    A product breakdown structure identifies the products to be delivered and how they relate to one another. This is a direct application of the focus on products principle, which starts planning from the required outputs.

  45. Question 45Principles

    What distinguishes a management stage from a technical stage in PRINCE2?

    1. A management stage is used only for IT projects; a technical stage is used for all projects
    2. A management stage is owned by the team manager; a technical stage is owned by the project board
    3. A management stage is a control period; a technical stage is a work phase Correct answer.
    4. A management stage is optional; a technical stage is mandatory

    Explanation

    Management stages are the project board's control points and end at stage boundaries. Technical stages are specialist phases of work, such as design or build, and may span management stages or sit within them.

  46. Question 46Principles

    An executive wants to start a project because a competitor has launched a similar product, but no cost or benefit analysis has been prepared. What does the continued business justification principle require?

    1. The project may start immediately because the competitive threat is sufficient justification
    2. The senior user should decide whether a business case is needed
    3. An outline business case should be prepared before initiation Correct answer.
    4. The project should start and the business case should be written only at closure

    Explanation

    Continued business justification requires a justifiable reason for starting the project before significant work begins. The outline business case is developed during starting up a project and refined during initiation, so competitive pressure alone is not enough.

  47. Question 47Principles

    A project team records lessons only in the final lessons report at closure. Which principle is most poorly applied, and why?

    1. Learn from experience, because lessons should be applied throughout Correct answer.
    2. Tailor to suit the project environment, because the lessons report has been tailored
    3. Focus on products, because lessons are not products
    4. Manage by exception, because lessons are outside tolerances

    Explanation

    Learn from experience requires lessons to be identified, recorded, and acted on continuously, not just at the end. Waiting until closure means the project cannot benefit from those lessons while work is still in progress.

  48. Question 48Principles

    A project board has an executive and a senior user but no senior supplier. What is the main consequence for the defined roles and responsibilities principle?

    1. The supplier interest is unrepresented on the board Correct answer.
    2. The senior user automatically becomes accountable for supplier performance
    3. The business case can no longer be reviewed at stage boundaries
    4. The project manager must take on the executive role

    Explanation

    Defined roles and responsibilities requires the business, user, and supplier interests to be represented on the board. Without a senior supplier, the supplier perspective and authority to commit supplier resources are missing.

  49. Question 49Principles

    A project manager allows delivery work to continue past a stage boundary without project board approval because progress is good. Which principle is being breached?

    1. Learn from experience
    2. Manage by stages Correct answer.
    3. Focus on products
    4. Continued business justification

    Explanation

    Manage by stages gives the board control at stage boundaries, where it decides whether work should continue. Proceeding without that decision removes the board's control point and breaches the principle.

  50. Question 50Principles

    The project board sets stage tolerances and the project manager sets work package tolerances for team managers. Why is this hierarchy consistent with manage by exception?

    1. It removes the need for tolerances at stage level
    2. It ensures every decision is escalated to the project board for approval
    3. It allows team managers to change the project's business justification
    4. It delegates authority and escalates only forecast exceptions Correct answer.

    Explanation

    Manage by exception works through tolerances set at each management level. The board delegates within stage tolerances, and the project manager delegates within work package tolerances, so only exceptions are escalated.

  51. Question 51People

    What is the purpose of the People theme in PRINCE2?

    1. To build and maintain productive working relationships among project participants Correct answer.
    2. To establish the project's approach to quality control and assurance
    3. To set out the project's approach to identifying and managing risk
    4. To define the project's organization structure, roles, and reporting lines

    Explanation

    The People theme addresses the human side of the project and aims to create and sustain productive working relationships. It is one of the seven PRINCE2 themes and applies throughout the project. Roles and structure belong to the Organization theme, while quality and risk are covered by their own themes.

  52. Question 52People

    Which of the following is one of the people aspects addressed by the People theme?

    1. Developing great teams Correct answer.
    2. Controlling the project's stage boundaries
    3. Preparing the business case
    4. Managing the risk register

    Explanation

    The People theme covers leading successful change, defining roles and responsibilities, developing great teams, communicating effectively, and engaging stakeholders. The other options relate to processes or to other themes.

  53. Question 53People

    In what order do the stages of Tuckman's team development model occur?

    1. Storming, forming, performing, norming
    2. Norming, forming, storming, performing
    3. Forming, norming, storming, performing
    4. Forming, storming, norming, performing Correct answer.

    Explanation

    Tuckman's model describes a team progressing from forming through storming and norming to performing. Storming follows forming as members test boundaries and clarify expectations. A team that has established norms can then perform effectively.

  54. Question 54People

    Which stage of Tuckman's model is characterized by conflict and competition as team members test boundaries?

    1. Norming
    2. Storming Correct answer.
    3. Forming
    4. Performing

    Explanation

    Storming is the stage in which disagreements, power struggles, and challenges to authority often emerge. It is a normal part of team development and can be managed by clarifying roles and expectations. Once resolved, the team can move toward norming.

  55. Question 55People

    Which statement best describes Belbin's team roles?

    1. A team role is the same as a person's job title
    2. People adopt particular team roles, and a balanced team benefits from a mix Correct answer.
    3. The project manager should personally perform every team role
    4. Every effective team must contain exactly nine members and each member must hold one role

    Explanation

    Belbin identified a set of behavioral team roles, and a team tends to work best when it has a balance of these roles. Team roles describe how people contribute, not their job titles. A team does not need a fixed number of members to be effective.

  56. Question 56People

    According to Kotter's model for leading change, what is the first step?

    1. Forming a powerful coalition
    2. Communicating the vision
    3. Anchoring the changes in the culture
    4. Creating a sense of urgency Correct answer.

    Explanation

    Kotter's eight-step model begins with creating a sense of urgency so that people are motivated to act. Forming a coalition and communicating a vision come after the need for change has been established. Anchoring the changes in the culture is the final step.

  57. Question 57People

    What does the change curve illustrate?

    1. The typical emotional stages people experience when faced with change Correct answer.
    2. The project's planned timeline for implementing changes across each stage
    3. The total cost of change over the entire project life cycle
    4. The hierarchy of roles needed to approve and reject changes

    Explanation

    The change curve shows that people commonly pass through predictable emotional stages when confronting change. Understanding it helps the project manager support people through transition. It is not a schedule, cost model, or approval hierarchy.

  58. Question 58People

    Which statement best distinguishes leadership from management in a project?

    1. Management is only performed by the project board, while leadership is only performed by the project manager
    2. Leadership focuses on planning and controlling resources, while management focuses on vision and motivation
    3. Leadership focuses on direction and motivating people, while management focuses on planning and controlling resources Correct answer.
    4. Leadership and management are identical and interchangeable

    Explanation

    Leadership is about setting direction, aligning people, and motivating them, whereas management is about planning, organizing, and controlling resources. Both are needed in a project. The distinction is about emphasis, not about who is allowed to perform which role.

  59. Question 59People

    What is the main purpose of stakeholder analysis?

    1. To decide which products will be produced in each stage
    2. To determine the project's overall budget and identify its funding sources
    3. To identify stakeholders and understand their interests and influence Correct answer.
    4. To assess whether the business case remains viable

    Explanation

    Stakeholder analysis identifies who has an interest in the project and assesses their influence and needs. This informs how the project engages them and shapes the communication management approach. Budgeting, product planning, and business case review are separate activities.

  60. Question 60People

    Which PRINCE2 product describes how the project will communicate with its stakeholders?

    1. Quality management approach
    2. Risk management approach
    3. Benefits management approach
    4. Communication management approach Correct answer.

    Explanation

    The communication management approach defines the methods, frequency, and responsibilities for communicating with stakeholders. It supports stakeholder engagement throughout the project. The other products cover benefits, quality, and risk respectively.

  61. Question 61People

    Why is communication described as a two-way process?

    1. Because the project manager must approve every message
    2. Because communication must be documented in writing
    3. Because feedback confirms that the message has been understood Correct answer.
    4. Because the sender must always communicate with more than one person at a time

    Explanation

    Effective communication requires the receiver to understand the message, so feedback is essential. Simply transmitting information does not confirm that it has been received or understood. Two-way communication therefore includes listening and checking understanding.

  62. Question 62People

    What is the main purpose of a role description in PRINCE2?

    1. To set out the project's communication plan
    2. To record the project's quality criteria and acceptance methods for each product
    3. To define a role's responsibilities, competences, and relationships Correct answer.
    4. To list every task the role holder must perform daily

    Explanation

    Role descriptions clarify what a role is accountable for, the competences it requires, and how it relates to other roles. They support clear roles and responsibilities, which is a People theme concern. They are not daily task lists or product quality records.

  63. Question 63People

    Which statement about authority and accountability is correct?

    1. Accountability can be shared equally among all team members
    2. A person can delegate authority but remains accountable Correct answer.
    3. A person can delegate accountability along with authority
    4. Authority is only granted to the project board

    Explanation

    Accountability is the obligation to answer for an outcome and cannot be delegated away. Authority to act can be delegated so that people can make decisions within agreed limits. This principle underpins defined roles and responsibilities.

  64. Question 64People

    Why might a project manager choose to co-locate team members?

    1. To avoid documenting decisions
    2. To reduce the need for any communication
    3. To ensure the project board attends daily meetings
    4. To improve communication and team building Correct answer.

    Explanation

    Co-location makes informal communication easier and helps build team cohesion. It supports team development but does not replace formal communication or documentation. It also does not require the project board to attend daily meetings.

  65. Question 65People

    Which action by a project manager best supports team motivation?

    1. Assigning all interesting work to the project manager
    2. Avoiding any discussion of team performance
    3. Recognizing and celebrating team achievements Correct answer.
    4. Withholding feedback until the project closes

    Explanation

    Motivation is supported by recognition, feedback, and a sense of achievement. Celebrating achievements reinforces progress and helps the team feel valued. Withholding feedback or concentrating interesting work undermines motivation.

  66. Question 66People

    In the People theme, what is the project manager's role in leading successful change?

    1. To prevent stakeholders from discussing the change
    2. To delegate all communication about change to the project board
    3. To help people understand and commit to the change Correct answer.
    4. To approve every change request personally

    Explanation

    Leading successful change involves communicating the vision, addressing concerns, and supporting people through transition. The project manager helps people understand why the change is needed and how it affects them. Formal change control is a separate process.

  67. Question 67People

    What does 'engaging stakeholders' mean in PRINCE2?

    1. Building relationships so stakeholders' needs are understood and considered Correct answer.
    2. Including only senior managers in project meetings
    3. Persuading stakeholders to accept every project decision
    4. Sending stakeholders regular reports without expecting or reviewing any response

    Explanation

    Engagement is a two-way relationship that helps the project understand and respond to stakeholder interests. It involves listening as well as informing. It is not one-way reporting, exclusion, or simply persuading people to agree.

  68. Question 68People

    Which of the following is an example of a barrier to effective communication?

    1. Choosing a channel appropriate to the message
    2. Providing feedback to confirm understanding
    3. Using jargon the audience does not understand Correct answer.
    4. Checking that the message has been received

    Explanation

    Jargon, noise, and unclear language can prevent the receiver from understanding the message. Feedback and appropriate channels help overcome such barriers. Barriers reduce the effectiveness of communication.

  69. Question 69People

    In Tuckman's model, what characterizes the performing stage?

    1. Team members are polite but uncertain about their roles and responsibilities
    2. Team members experience conflict over roles and authority
    3. The team works effectively together towards shared objectives Correct answer.
    4. The team is disbanding after completing the work

    Explanation

    At the performing stage, the team has established norms and works productively toward its goals. Forming, storming, and norming precede this stage. The team is not yet disbanding, which would be a later adjourning stage.

  70. Question 70People

    When should the People theme be applied in a project?

    1. Only during the initiation stage
    2. Throughout the project Correct answer.
    3. Only during the final stage of the project
    4. Only when a change request is raised

    Explanation

    People aspects affect the project at every stage, so the People theme is applied continuously. It is not limited to initiation, change control, or closure. All roles have a part to play in maintaining productive working relationships.

  71. Question 71People

    How does the People theme differ from the Organization theme?

    1. Organization defines roles and responsibilities; People focuses on how people work together Correct answer.
    2. Organization applies only to the project board, while People applies only to the team
    3. People defines roles and responsibilities, while Organization focuses on behaviors and working relationships
    4. People is optional, while Organization is mandatory

    Explanation

    The Organization theme sets the project's structure, roles, and responsibilities. The People theme addresses the behaviors, relationships, and engagement needed to make those roles work effectively. Both themes are mandatory and apply across the project.

  72. Question 72People

    In stakeholder analysis, what does the power/interest grid help the project manager decide?

    1. Which stakeholders will approve the business case
    2. How closely to engage each stakeholder Correct answer.
    3. Which stakeholders should be excluded from the project
    4. How much each stakeholder should be paid

    Explanation

    The power/interest grid helps prioritize engagement by showing which stakeholders have high influence and high interest. Stakeholders with high power and high interest usually need closer engagement. It does not determine exclusion, payment, or approval rights.

  73. Question 73People

    What is an appropriate way for a project manager to handle conflict within the team?

    1. Ignore the conflict and hope it resolves itself
    2. Remove all team members involved in the conflict
    3. Escalate every disagreement to the project board
    4. Address it openly and facilitate a resolution Correct answer.

    Explanation

    Constructive conflict management means surfacing issues and helping the team resolve them. Addressing conflict openly supports team development and prevents escalation. Avoidance, immediate escalation, or removing people rarely builds a healthy team.

  74. Question 74People

    In the change curve, what does the 'denial' stage look like?

    1. People actively champion the change
    2. People ignore or deny that change is happening Correct answer.
    3. People negotiate for exceptions to the change
    4. People have fully integrated the change into their work

    Explanation

    Denial is an early reaction in which people resist the reality of change and may ignore it. It is followed by other stages such as frustration and eventual acceptance. Champions and full integration come much later.

  75. Question 75People

    Why should a project manager consider cultural differences within a team?

    1. Because cultural awareness removes the need for any communication planning
    2. Because only one culture can be represented on a project
    3. Because cultural differences always cause project failure
    4. Because cultural norms affect communication and teamwork Correct answer.

    Explanation

    Cultural norms influence communication styles, expectations, and ways of working, so awareness helps the project manager adapt. It supports effective teamwork and engagement. It does not guarantee failure or remove the need for planning.

  76. Question 76People

    What is the main purpose of the People theme in PRINCE2?

    1. To record stakeholder interests in the communication plan
    2. To select team members with technical skills
    3. To define reporting lines and delegated authority
    4. To build a productive working environment Correct answer.

    Explanation

    The People theme focuses on creating and maintaining a productive working environment in which people are willing and able to work together effectively. It addresses leadership, change, stakeholders, roles, team development, and communication rather than structural reporting lines alone.

  77. Question 77People

    Which of the following is one of the five elements of the People theme?

    1. Preparing the business case
    2. Engaging stakeholders Correct answer.
    3. Applying quality control
    4. Managing stage boundaries

    Explanation

    The five elements of the People theme are leading successful change, engaging stakeholders, roles and responsibilities, team development, and communication. Engaging stakeholders is therefore one of its elements.

  78. Question 78People

    What does team development mainly aim to improve?

    1. Replacing underperforming staff quickly
    2. Assigning work packages to team members
    3. Skills and working relationships Correct answer.
    4. Documenting the team's reporting structure

    Explanation

    Team development is about improving the capabilities, confidence, and working relationships of the people in the project team. It helps the team become more effective together, not just more technically skilled.

  79. Question 79People

    In the change curve, which stage often involves resistance, frustration, and blame?

    1. Shock
    2. Frustration Correct answer.
    3. Denial
    4. Acceptance

    Explanation

    After initial shock or denial, people often move into a stage of frustration or resistance where they may question the change and blame others. Recognizing this as a normal reaction helps the project manager respond with support and clear communication.

  80. Question 80People

    According to Kotter's model, which step typically follows creating a sense of urgency?

    1. Declaring victory early
    2. Building a guiding coalition Correct answer.
    3. Anchoring changes in culture
    4. Removing obstacles

    Explanation

    Kotter's sequence begins with creating urgency, then forming a powerful guiding coalition to lead the change. Removing obstacles and anchoring changes come later in the model.

  81. Question 81People

    Which Tuckman stage is characterized by conflict about roles and ways of working?

    1. Forming
    2. Adjourning
    3. Norming
    4. Storming Correct answer.

    Explanation

    In the storming stage, team members may challenge each other and disagree about roles, goals, or working methods. The project manager can help by clarifying expectations and facilitating resolution.

  82. Question 82People

    Which is an example of an intrinsic motivator?

    1. A financial bonus for meeting a deadline
    2. Pride in doing a task well Correct answer.
    3. A promotion to a more senior role
    4. A public award for project success

    Explanation

    Intrinsic motivation comes from internal satisfaction, such as pride, interest, or a sense of achievement. Rewards such as bonuses, promotions, and public awards are external incentives.

  83. Question 83People

    Which communication method is most suitable for giving the same information to a large, dispersed audience at the same time?

    1. A broadcast email newsletter Correct answer.
    2. One-to-one meetings
    3. Informal corridor conversations
    4. Interactive workshops

    Explanation

    A broadcast email newsletter is a push method that can reach many people consistently at once. It suits one-way dissemination of information, though it should be combined with other methods when feedback is needed.

  84. Question 84People

    A stakeholder needs to be consulted on key decisions but does not need to be involved in every working session. Which engagement approach is most appropriate?

    1. Informing them only at project closure
    2. Consulting them on key decisions Correct answer.
    3. Giving them full control of the team
    4. Excluding them from project communications

    Explanation

    Consulting means seeking stakeholder input on decisions or outputs while retaining appropriate control within the project. It fits stakeholders whose views are important but who do not need day-to-day involvement.

  85. Question 85People

    Why should a project manager confirm that each team member understands their role?

    1. To avoid defining any reporting lines
    2. To reduce the need for project documentation
    3. To align expectations and avoid duplication Correct answer.
    4. To transfer accountability to the team member

    Explanation

    Clear role understanding helps people know what is expected of them and how their work fits with others. This reduces gaps, duplicated effort, and avoidable conflict.

  86. Question 86People

    Which action best supports team development in a newly formed project team?

    1. Agreeing working practices and building trust Correct answer.
    2. Waiting for the team to resolve all issues alone
    3. Avoiding feedback until the project ends
    4. Assigning all tasks to the most experienced member

    Explanation

    Team development is supported by agreeing how the team will work together and creating early opportunities to build trust. This helps the team move through forming and storming more effectively.

  87. Question 87People

    Two team members are making personal remarks about each other during a disagreement. What should the project manager do first?

    1. Reassign one team member to another project
    2. Facilitate a discussion to understand both viewpoints Correct answer.
    3. Escalate the disagreement immediately to the project board
    4. Ignore the disagreement because it may resolve itself

    Explanation

    The project manager should first address the behavior and help the parties discuss the issue constructively. Early facilitated discussion can resolve the conflict before it escalates and disrupts the team.

  88. Question 88People

    Which behavior best demonstrates situational leadership?

    1. Adapting direction and support to the team's needs Correct answer.
    2. Focusing only on task completion and not on people
    3. Using the same leadership style with every team member at all times
    4. Making all decisions without consulting the team

    Explanation

    Situational leadership means adjusting the level of direction and support according to the team's competence and commitment. A flexible approach is more effective than applying one style rigidly.

  89. Question 89People

    A project manager wants to reduce misunderstandings in a complex technical discussion. Which approach is most appropriate?

    1. Avoiding discussion until the design is finalized
    2. Using a real-time discussion with visual aids Correct answer.
    3. Relying on the project intranet for all details
    4. Sending a brief text message summary

    Explanation

    Complex technical topics benefit from richer communication channels that allow questions, clarification, and visual explanation. A real-time discussion with visual aids supports shared understanding.

  90. Question 90People

    A stakeholder is supportive but has low influence over the project. How should the project manager engage them?

    1. Ignore them because they cannot affect outcomes
    2. Spend most engagement effort on this stakeholder
    3. Escalate every decision to them for approval
    4. Keep them informed and use their support Correct answer.

    Explanation

    Stakeholders with low influence but positive interest still need appropriate information and can be useful advocates. Engagement effort should be proportionate, with more attention given to high-power and high-interest stakeholders.

  91. Question 91People

    Which factor is most likely to undermine a team's willingness to collaborate?

    1. Visible project board support
    2. Clear roles and responsibilities
    3. A blame culture when problems arise Correct answer.
    4. Regular constructive feedback

    Explanation

    A blame culture makes people defensive and less willing to share problems or ideas. Collaboration depends on psychological safety and trust that issues can be raised without unfair reprisal.

  92. Question 92People

    What is the main benefit of effective delegation by a project manager?

    1. It removes the manager's accountability for the work
    2. It ensures all decisions are made by one person
    3. It means the manager no longer needs to monitor progress
    4. It develops people and frees manager capacity Correct answer.

    Explanation

    Good delegation gives team members responsibility and opportunity to develop while allowing the manager to focus on other work. The manager must still monitor progress and remains accountable for the delegated work.

  93. Question 93People

    What makes feedback most useful to a team member?

    1. Waiting until a mistake is repeated several times
    2. Focusing on the person's character rather than actions
    3. Giving it only during the annual appraisal
    4. Making it specific, timely, and focused on behavior Correct answer.

    Explanation

    Useful feedback is specific, given close to the event, and focused on observable behavior rather than personality. This makes it easier for the recipient to understand and act on.

  94. Question 94People

    Which practice best supports a team working across different locations?

    1. Holding all meetings without an agenda to save time
    2. Assuming everyone prefers the same communication style
    3. Agreeing communication norms and using shared tools Correct answer.
    4. Reducing the frequency of progress updates

    Explanation

    Virtual teams need explicit communication norms and reliable shared tools to compensate for the lack of informal contact. Agreeing these early helps maintain clarity, inclusion, and trust.

  95. Question 95People

    Why can diversity within a project team improve decision-making?

    1. It guarantees that all conflicts will be avoided
    2. It brings different viewpoints Correct answer.
    3. It removes the need for a project manager
    4. It ensures everyone has the same perspective

    Explanation

    Diverse teams can draw on different experiences, knowledge, and perspectives, which can improve problem-solving and challenge groupthink. The project manager must still facilitate inclusively so those views are heard.

  96. Question 96People

    A project will introduce a new system that changes long-established working practices. Which action best addresses likely resistance?

    1. Treating resistance as a disciplinary matter
    2. Involving affected staff early and explaining benefits Correct answer.
    3. Reducing communication to avoid raising concerns
    4. Announcing the change only when it is fully implemented

    Explanation

    Resistance is reduced when people understand the reasons for change and have a chance to contribute to how it is implemented. Early involvement and clear explanation build ownership and trust.

  97. Question 97People

    A stakeholder has high power and high interest in the project. What is the most appropriate engagement approach?

    1. Ignore their concerns to avoid scope changes
    2. Keep them informed only through a newsletter
    3. Monitor them with minimal effort
    4. Manage them closely and involve them Correct answer.

    Explanation

    High-power, high-interest stakeholders can significantly affect the project and care about its outcomes, so they need close engagement and involvement in key decisions. This helps maintain support and manage expectations.

  98. Question 98People

    Which is the best example of emotional intelligence in a project manager?

    1. Recognizing stress and responding supportively Correct answer.
    2. Hiding all emotions from the team at all times
    3. Making decisions without considering their impact on people
    4. Avoiding difficult conversations to keep everyone happy

    Explanation

    Emotional intelligence includes recognizing one's own and others' emotions and responding appropriately. Noticing stress and offering support shows empathy and awareness of the human impact of project work.

  99. Question 99People

    A project manager wants to build trust with a new team. Which action is most likely to achieve this?

    1. Changing decisions frequently without explanation
    2. Taking credit for the team's successes
    3. Being consistent and transparent Correct answer.
    4. Keeping information about risks and issues secret

    Explanation

    Trust grows when a project manager is consistent, open, and reliable, and when promises are kept. Transparency about risks and issues helps the team feel respected and able to raise concerns.

  100. Question 100People

    Which action best demonstrates Kotter's principle of generating short-term wins?

    1. Waiting until the final stage to report progress
    2. Hiding early successes to avoid complacency
    3. Celebrating an early improvement Correct answer.
    4. Removing all recognition until closure

    Explanation

    Short-term wins are early, visible achievements that show the change is working and help maintain momentum. Celebrating them reinforces commitment and builds confidence for the remaining work.

  101. Question 101Practices

    What is the purpose of the business case practice?

    1. To document the reporting lines between the project board and corporate management.
    2. To establish whether the project is desirable, viable and achievable, and to support continued investment decisions. Correct answer.
    3. To define the quality criteria for each specialist product to be delivered.
    4. To record the day-to-day tasks assigned to each team member during a stage.

    Explanation

    The business case practice provides the mechanism for judging whether the project is desirable, viable and achievable, and for continuing, changing or stopping the project. It is reviewed at stage boundaries and at exception points. It does not record tasks, product quality criteria or reporting lines.

  102. Question 102Practices

    A project is expected to reduce processing time by 20%, but it will also require two staff to be redeployed away from customer service. How should the redeployment be treated in the business case?

    1. As a benefit, because it reduces processing time
    2. As a risk, because it may affect customer satisfaction
    3. As a dis-benefit, because it is negative for a stakeholder Correct answer.
    4. As an output, because it is produced by the project

    Explanation

    A dis-benefit is a negative consequence of the project that is perceived as negative by one or more stakeholders. The redeployment is a known consequence, not an uncertain event, so it belongs in the business case as a dis-benefit. It is not an output or a benefit.

  103. Question 103Practices

    Which statement correctly distinguishes an outcome from a benefit?

    1. An outcome is recorded in the risk register; a benefit is recorded in the quality register
    2. An outcome is a result of change; a benefit is a measurable improvement Correct answer.
    3. An outcome is a measurable improvement; a benefit is the change itself
    4. An outcome is a specialist product; a benefit is the activity that creates it

    Explanation

    An outcome is the result of change, such as staff being able to use a new system. A benefit is a measurable improvement that results from the outcome and is perceived as an advantage by a stakeholder. Outputs are the specialist products, and benefits are recorded in the business case.

  104. Question 104Practices

    Which three roles make up the project board in a PRINCE2 project?

    1. Project manager, team manager and project support
    2. Senior user, senior supplier and project assurance
    3. Executive, project manager and senior user
    4. Executive, senior user and senior supplier Correct answer.

    Explanation

    The project board consists of the executive, senior user and senior supplier. These roles represent the business, user and supplier interests respectively. The project manager, team manager, project support and assurance roles are not board members by definition.

  105. Question 105Practices

    Who is responsible for project assurance in a PRINCE2 project?

    1. The team manager, who reviews products before delivery
    2. The project board, which may delegate to appointed assurance roles Correct answer.
    3. The project support office, which audits all projects in the organization
    4. The project manager, who checks the work of the team managers

    Explanation

    Project assurance is a project board responsibility, covering business, user and supplier assurance. Board members may delegate their assurance responsibilities to appointed assurance roles. The project manager and team manager perform delivery management, not independent project assurance.

  106. Question 106Practices

    Which responsibility belongs to the team manager rather than the project manager?

    1. Accepting work packages and managing the team's work Correct answer.
    2. Approving the end stage report
    3. Preparing the project initiation documentation
    4. Setting project tolerances with corporate management

    Explanation

    The team manager accepts work packages from the project manager and manages the team that produces the products. Preparing the project initiation documentation is a project manager responsibility. End stage reports are approved by the project board, and project tolerances are set with corporate or programme management.

  107. Question 107Practices

    A project needs a central record of configuration items and administrative support for board meetings. Which role is most appropriate?

    1. Project support Correct answer.
    2. Team manager
    3. Senior supplier
    4. Project assurance

    Explanation

    Project support provides administrative services and often maintains registers, logs and configuration records. It can also support board meetings and document control. Assurance, supplier and team management roles have different responsibilities.

  108. Question 108Practices

    Which sequence follows the product-based planning technique correctly?

    1. Project product description, product breakdown structure, product descriptions, product flow diagram Correct answer.
    2. Product descriptions, product flow diagram, project product description, product breakdown structure
    3. Product flow diagram, product descriptions, product breakdown structure, project product description
    4. Product breakdown structure, project product description, product flow diagram, product descriptions

    Explanation

    Product-based planning starts with the project product description, then creates the product breakdown structure. Product descriptions are written for the products, and finally the product flow diagram shows dependencies and sequence.

  109. Question 109Practices

    What does a product breakdown structure show?

    1. The project's products and their hierarchical relationships Correct answer.
    2. The resources assigned to each work package
    3. The order in which activities must be carried out
    4. The costs and durations of each stage

    Explanation

    A product breakdown structure decomposes the project into its component products and shows their hierarchical relationships. It is not a schedule and does not show activities, resources, costs or durations. Those details appear in plans and the product flow diagram.

  110. Question 110Practices

    What is the key difference between a management stage and a delivery stage?

    1. A management stage is optional, while a delivery stage is mandatory in every project.
    2. A management stage is board-controlled at boundaries; a delivery stage groups work packages. Correct answer.
    3. A management stage contains only reporting, while a delivery stage contains specialist work.
    4. A management stage exists only for exceptions, while a delivery stage exists for initiation.

    Explanation

    A management stage is the section of the project that the project board controls, with decisions taken at stage boundaries. A delivery stage is a group of work packages managed by a team, often within a management stage. Management stages are not merely reporting or exception constructs.

  111. Question 111Practices

    Which plan is produced by a team manager to cover the work assigned in a work package?

    1. The team plan Correct answer.
    2. The stage plan
    3. The project plan
    4. The exception plan

    Explanation

    A team plan is produced by the team manager for the work in a work package and may cover a smaller timescale than a stage. The project plan and stage plan are project manager responsibilities. An exception plan is produced in response to an exception.

  112. Question 112Practices

    In product-based planning, what is the main purpose of the product flow diagram?

    1. To record the quality criteria that each product must meet
    2. To show the activities, durations and resources needed to create each product
    3. To show the sequence and dependencies in which products are produced Correct answer.
    4. To identify the risks associated with producing each product

    Explanation

    The product flow diagram shows the order in which products are produced and the dependencies between them. It helps derive activities for the plan. It does not itself record durations, resources, quality criteria or risks.

  113. Question 113Practices

    How do quality assurance and quality control differ?

    1. Quality assurance is performed by the team, while quality control is performed by the board.
    2. Quality assurance confirms the methods are appropriate; quality control checks products against criteria. Correct answer.
    3. Quality assurance checks products against quality criteria, while quality control sets the quality methods.
    4. Quality assurance applies only to projects, while quality control applies only to programmes.

    Explanation

    Quality assurance provides confidence that the project's quality methods are appropriate and effective. Quality control is the operational checking of products against their quality criteria. The two are complementary, not alternatives.

  114. Question 114Practices

    What is the purpose of the quality register?

    1. To list the risks that could affect product quality
    2. To document the roles and responsibilities of the project board
    3. To record changes requested to baselined products
    4. To record planned and performed quality activities, such as reviews Correct answer.

    Explanation

    The quality register records the quality management activities planned and performed, including quality reviews and their results. It provides a central quality record for the project. Risks, organization roles and change requests are recorded elsewhere.

  115. Question 115Practices

    Which statement best describes the relationship between acceptance criteria and quality criteria?

    1. Acceptance criteria apply only to the final product; quality criteria apply only to component products.
    2. Acceptance criteria are set by the senior supplier; quality criteria are set by the team manager.
    3. Acceptance criteria relate to how the team works; quality criteria relate to how the board reports.
    4. Acceptance criteria relate to the project product; quality criteria relate to each product's attributes. Correct answer.

    Explanation

    Acceptance criteria are the prioritized requirements for the project product, while quality criteria are the attributes that a product must have to meet those requirements. Quality criteria appear in product descriptions and are used for quality control.

  116. Question 116Practices

    In a quality review, who is responsible for presenting the product and explaining how it was produced?

    1. The presenter Correct answer.
    2. The administrator
    3. The chair
    4. The reviewer

    Explanation

    The presenter introduces the product, explains what it is intended to achieve and answers questions about how it was produced. The chair runs the review, reviewers examine the product, and the administrator records the results.

  117. Question 117Practices

    What is the difference between risk appetite and risk tolerance?

    1. Risk appetite applies only to threats recorded in the risk register; risk tolerance applies only to opportunities.
    2. Risk appetite is the risk an organization accepts; risk tolerance is the exposure threshold it allows. Correct answer.
    3. Risk appetite is set by the team manager; risk tolerance is set by the project support office.
    4. Risk appetite is the list of risks recorded in the risk register; risk tolerance is the budget for responding to them.

    Explanation

    Risk appetite describes the amount and type of risk an organization is willing to accept in pursuit of its objectives. Risk tolerance expresses the measurable threshold of exposure that will be allowed. These concepts guide how risks are assessed and responded to.

  118. Question 118Practices

    Which risk response is used to take advantage of an opportunity by ensuring it definitely happens?

    1. Avoid
    2. Transfer
    3. Accept
    4. Exploit Correct answer.

    Explanation

    Exploit is the response for an opportunity where the organization acts to ensure the opportunity is realized. Avoid is a threat response, transfer shifts risk to another party, and accept involves no proactive action.

  119. Question 119Practices

    Which information is typically recorded in the risk register?

    1. The quality criteria for each specialist product
    2. Cause, event, effect, probability, impact, response and owner Correct answer.
    3. The work packages assigned to each team
    4. The changes approved by the change authority

    Explanation

    The risk register records each risk's cause, event and effect, together with its probability, impact, proximity, response and owner. It is the central record for managing project risks. Quality criteria, work packages and approved changes are held in other records.

  120. Question 120Practices

    A request for change is classified as which type of item in the change practice?

    1. A risk response
    2. An issue Correct answer.
    3. A progress report
    4. A quality record

    Explanation

    The change practice handles issues, and a request for change is one type of issue. The other main issue types are off-specifications and problems or concerns. Issues are recorded and managed through the issue register and change control.

  121. Question 121Practices

    A project board wants to delegate authority to approve changes within agreed limits. Where should this be defined?

    1. In the change control approach, which defines the change authority and its limits Correct answer.
    2. In the daily log, which records day-to-day information
    3. In the quality register, which records quality management activities
    4. In the business case, which records the project's benefits and justification

    Explanation

    The change control approach defines how changes are controlled, including who has change authority and any limits on that authority. The board may delegate approval within those limits. The business case, quality register and daily log serve different purposes.

  122. Question 122Practices

    What is a baseline in the change practice?

    1. A configuration-controlled snapshot of products used as a change reference Correct answer.
    2. A plan for delivering a work package assigned to a team
    3. A list of risks that have been accepted by the project board
    4. A report that summarizes the stage's progress to the board

    Explanation

    A baseline is a configuration-controlled snapshot of products, used as a reference point against which changes and progress can be assessed. Once baselined, changes to products must go through change control. It is not a risk list, report or work package plan.

  123. Question 123Practices

    Which pair correctly describes checkpoint reports and highlight reports?

    1. Checkpoint reports go from the project board to the project manager; highlight reports go from the project manager to the team.
    2. Checkpoint reports are produced at stage boundaries; highlight reports are produced at project closure.
    3. Checkpoint reports are optional; highlight reports are mandatory in every work package.
    4. Checkpoint reports go from team manager to project manager; highlight reports go from project manager to board. Correct answer.

    Explanation

    Checkpoint reports are produced by the team manager for the project manager at agreed intervals. Highlight reports are produced by the project manager for the project board at agreed intervals. Their direction and audience distinguish them.

  124. Question 124Practices

    What is the likely consequence when a project manager forecasts that a stage tolerance will be exceeded?

    1. The project board automatically closes the stage without further review.
    2. The team manager revises the project plan and informs the senior user.
    3. An exception report is sent to the project board, which may request an exception plan. Correct answer.
    4. The project manager ignores the forecast until the stage boundary is reached.

    Explanation

    If a stage tolerance is forecast to be exceeded, the project manager escalates the situation to the project board through an exception report. The board may then direct an exception plan or take other action. The forecast should not be ignored until the boundary.

  125. Question 125Practices

    What is the difference between the lessons log and the lessons report?

    1. The lessons log captures lessons during the project; the lessons report passes them on at the end. Correct answer.
    2. The lessons log records risks, while the lessons report records quality reviews.
    3. The lessons log is produced at project closure, while the lessons report is updated daily.
    4. The lessons log is for the project board, while the lessons report is for the team manager only.

    Explanation

    The lessons log is used throughout the project to record lessons as they are identified. The lessons report is produced at the end of a stage or project to pass on relevant lessons to the wider organization. The two are sequential and complementary.

  126. Question 126Practices

    What is the main purpose of the business case practice?

    1. To allocate work packages to the team managers
    2. To record and control requests for change during the project
    3. To define the quality methods used to inspect deliverables
    4. To judge whether the project remains desirable and viable Correct answer.

    Explanation

    The business case practice provides a mechanism to judge whether the project is still desirable, viable and achievable, so investment can continue or be stopped. It is reviewed at stage boundaries and when significant issues arise.

  127. Question 127Practices

    Which three stakeholder interests must be represented on a PRINCE2 project board?

    1. Sponsor, customer and regulator
    2. Finance, audit and procurement
    3. Operations, risk and quality
    4. Business, user and supplier Correct answer.

    Explanation

    The project board represents the business, user and supplier interests so that key perspectives are considered in decisions. Each interest is covered by a board role such as executive, senior user or senior supplier.

  128. Question 128Practices

    Which plan provides the overall baseline for controlling the whole project?

    1. Exception plan
    2. Project plan Correct answer.
    3. Stage plan
    4. Team plan

    Explanation

    The project plan is the overall plan for the project and provides the baseline against which overall progress is measured. Stage and team plans sit below it and cover narrower levels of detail.

  129. Question 129Practices

    Within the risk practice, what is a risk owner?

    1. The person who first identifies the risk in a workshop
    2. The person accountable for managing a specific risk Correct answer.
    3. The person who records the risk in the risk register
    4. The person who funds the response from the change budget

    Explanation

    A risk owner is the person accountable for managing a specific risk and its selected response. This is distinct from the person who identifies or records the risk.

  130. Question 130Practices

    What does management by exception mean for a project board?

    1. It approves each checkpoint report before work continues
    2. It reviews every work package before work starts
    3. It removes all tolerances once the project has started
    4. It sets tolerances and delegates control within them Correct answer.

    Explanation

    Management by exception means the board agrees tolerances and delegates day-to-day management within those limits. It intervenes only when forecasts show that tolerances may be exceeded.

  131. Question 131Practices

    Which item is treated as an issue in PRINCE2?

    1. A problem that requires management action Correct answer.
    2. A benefit recorded in the business case
    3. A forecast that a stage will finish within tolerance
    4. A quality criterion agreed for a product

    Explanation

    An issue is a concern or problem that requires management action. It can include a request for change, an off-specification or a general problem.

  132. Question 132Practices

    What is the main purpose of the quality management approach?

    1. To record the results of quality inspections
    2. To list the products required in a work package
    3. To authorize changes to product baselines
    4. To define how quality will be controlled Correct answer.

    Explanation

    The quality management approach defines the quality standards, methods, responsibilities and controls to be used across the project. It provides the framework for quality planning and quality control.

  133. Question 133Practices

    What is project assurance responsible for?

    1. Producing highlight reports for the project board
    2. Approving the project plan on behalf of the supplier
    3. Delivering the specialist products assigned to a team
    4. Monitoring the project on behalf of the project board Correct answer.

    Explanation

    Project assurance monitors the project on behalf of the project board and provides confidence that the project is being managed appropriately. It is independent of the project manager.

  134. Question 134Practices

    What does the benefits management approach describe?

    1. How risks will be transferred to a third party
    2. How benefits will be measured and realized Correct answer.
    3. How changes will be approved within tolerances
    4. How the project will recruit specialist team members

    Explanation

    The benefits management approach defines how benefits will be measured, achieved and reviewed, including responsibilities and timing. It supports the business case after the project outputs are delivered.

  135. Question 135Practices

    What is rolling wave planning?

    1. Repeating the same plan for every management stage
    2. Replacing the project plan with a team plan each stage
    3. Detailing near work and outlining later work Correct answer.
    4. Planning only the final stage in detail before closure

    Explanation

    Rolling wave planning means planning near-term work in detail while later work is kept at a broader level. As more information becomes available, later parts of the plan are refined.

  136. Question 136Practices

    What is a quality tolerance?

    1. The acceptable range for quality criteria Correct answer.
    2. The maximum cost allowed for a quality inspection
    3. The time allowed for completing a quality review
    4. The number of reviewers required for a product

    Explanation

    A quality tolerance defines the acceptable range for a product's quality criteria. If the product is forecast to fall outside that range, the deviation should be managed.

  137. Question 137Practices

    A threat has low impact and the project cannot influence it. Which response is most appropriate?

    1. Transfer the threat to a supplier through insurance
    2. Accept the threat and monitor it Correct answer.
    3. Reduce the threat by adding a control activity
    4. Avoid the threat by changing the project scope

    Explanation

    When a threat has low impact and cannot be influenced, acceptance is usually appropriate, with monitoring in case the situation changes. Avoidance, transfer or reduction would add cost or effort out of proportion to the exposure.

  138. Question 138Practices

    What does the change control approach define?

    1. How benefits are measured after project closure
    2. How team managers recruit specialist staff
    3. How changes are identified, assessed and approved Correct answer.
    4. How the project board appoints project assurance

    Explanation

    The change control approach sets out how changes and other issues are identified, assessed, approved, implemented and reviewed. It also defines roles, responsibilities and authorities for change control.

  139. Question 139Practices

    What is the main content of an exception report?

    1. A list of quality criteria for each product
    2. The benefits forecast in the business case
    3. The deviation, impact and recovery options Correct answer.
    4. The daily tasks completed by each team member

    Explanation

    An exception report explains the actual or forecast deviation from tolerance, its impact and the options available to recover. It supports a project board decision on how to proceed.

  140. Question 140Practices

    How does project assurance differ from quality assurance?

    1. Project assurance inspects products; quality assurance sets standards
    2. Project assurance is optional; quality assurance is required by PRINCE2
    3. Project assurance is independent; quality assurance reports to the team manager
    4. Project assurance covers board interests; quality assurance checks systems Correct answer.

    Explanation

    Project assurance monitors the project on behalf of the project board across its interests. Quality assurance is an independent check that quality management arrangements and standards are appropriate and being followed.

  141. Question 141Practices

    When is an exception plan produced?

    1. When a stage may exceed its tolerances Correct answer.
    2. When a quality review finds a minor error
    3. When the project board approves the project brief
    4. When a team manager needs a new work package

    Explanation

    An exception plan is produced when a stage or project is forecast to exceed its tolerances and the existing plan is no longer viable. It shows how the forecast exception will be handled.

  142. Question 142Practices

    In a quality review, what is a reviewer expected to do?

    1. Present the product and explain how it was built
    2. Record the review in the risk register
    3. Approve changes to the product's baseline
    4. Check the product against its quality criteria Correct answer.

    Explanation

    Reviewers examine the product against its quality criteria and raise findings during the review. The presenter explains the product, but reviewers perform the checking role.

  143. Question 143Practices

    What is included in the risk management approach?

    1. The schedule of stages and their tolerances
    2. The list of all identified risks and their owners
    3. The quality criteria for each project product
    4. The roles and techniques used to manage risk Correct answer.

    Explanation

    The risk management approach defines how risk management will be performed, including procedures, roles, responsibilities, techniques and risk appetite. The risk register holds the individual risks.

  144. Question 144Practices

    What is the change budget used for?

    1. Covering the cost of project assurance
    2. Paying for team manager overtime
    3. Funding changes within agreed limits Correct answer.
    4. Funding quality inspections during a stage

    Explanation

    The change budget is an amount allocated to fund changes within agreed limits, allowing certain changes to be handled without escalating every one. It is defined as part of change control arrangements.

  145. Question 145Practices

    What does the end stage report provide to the project board?

    1. A summary of stage performance and lessons Correct answer.
    2. A list of all changes approved in the project
    3. A daily record of team progress
    4. A forecast of benefits after closure

    Explanation

    The end stage report summarizes stage performance against the stage plan and includes lessons and any relevant issues. It supports the board's decision to approve the next stage.

  146. Question 146Practices

    During a stage, a key benefit is no longer expected although cost and time remain within tolerance. What should happen next?

    1. Transfer the benefit to another project without approval
    2. Review the business case and consider stopping the project Correct answer.
    3. Record the change in the quality register and continue
    4. Continue unchanged because cost and time are within tolerance

    Explanation

    The business case must remain valid, not just the cost and time tolerances. If a key benefit is no longer expected, the business case should be reviewed and the project board should consider whether continued investment is justified.

  147. Question 147Practices

    A risk has high probability and high impact, but the cost of its response exceeds the potential impact. What is the most appropriate action?

    1. Ignore the risk because it is too expensive to manage
    2. Accept the risk and monitor it Correct answer.
    3. Transfer the risk to the project board
    4. Implement the response regardless of its cost

    Explanation

    Risk responses should be proportionate to the exposure. If the response costs more than the potential impact, acceptance with monitoring may be more appropriate than implementing an uneconomic response.

  148. Question 148Practices

    A team manager forecasts that a work package will exceed its tolerances. What should the team manager do first?

    1. Change the product's quality criteria to fit
    2. Approve additional change budget
    3. Update the business case
    4. Raise an exception to the project manager Correct answer.

    Explanation

    A team manager works within the tolerances agreed for the work package. If those tolerances are forecast to be exceeded, the team manager should escalate the exception to the project manager.

  149. Question 149Practices

    A change request would exceed stage tolerance but remain within project tolerance. Who should decide whether to approve it?

    1. The project manager, because project tolerance is not exceeded
    2. Project assurance, because it monitors board interests
    3. The team manager, because the work is in their work package
    4. The project board, because stage tolerance is exceeded Correct answer.

    Explanation

    The project manager can approve changes within delegated stage tolerances. Once a change is forecast to exceed stage tolerance, it must be escalated to the project board for a decision.

  150. Question 150Practices

    A product fails a quality review. What is the most appropriate PRINCE2 action?

    1. Close the stage because the review is complete
    2. Change the quality criteria to match the product
    3. Log the failure as an issue and correct it Correct answer.
    4. Accept the product and log the failure as a lesson

    Explanation

    A failed quality review means the product does not meet its quality criteria and requires corrective action. The failure should be managed, often as an issue, so that the product is corrected and re-checked.

  151. Question 151Processes

    Which of the following triggers the Starting up a Project process?

    1. An endorsed Project Brief
    2. An approved Project Initiation Documentation
    3. A project mandate Correct answer.
    4. A signed-off Stage Plan

    Explanation

    Starting up a Project is the pre-project process and is triggered by a project mandate, which is any information that prompts the project to be considered. The Project Brief and the initiation Stage Plan are outputs created by the process itself, while the Project Initiation Documentation belongs to a later process.

  152. Question 152Processes

    In which process does the activity 'Authorise the project' take place?

    1. Managing a Stage Boundary
    2. Starting up a Project
    3. Initiating a Project
    4. Directing a Project Correct answer.

    Explanation

    Authorising the project is a Project Board decision taken within Directing a Project once the Project Manager has delivered the Project Initiation Documentation. Initiating a Project carries out the preparation; the authority to commit to the project rests with the board's own process.

  153. Question 153Processes

    In which process does a Team Manager accept, execute and deliver a work package?

    1. Managing a Stage Boundary
    2. Directing a Project
    3. Managing Product Delivery Correct answer.
    4. Controlling a Stage

    Explanation

    Managing Product Delivery sits between the Project Manager and the team and contains exactly three activities: accepting, executing and delivering a work package. Controlling a Stage authorises the work package but does not manage its day-to-day delivery.

  154. Question 154Processes

    Which process contains the activity 'Recommend project closure'?

    1. Closing a Project Correct answer.
    2. Managing a Stage Boundary
    3. Directing a Project
    4. Controlling a Stage

    Explanation

    Closing a Project is where the Project Manager confirms product acceptance, evaluates the project, assesses follow-on actions and recommends closure to the Project Board. The board's matching decision, 'Authorise project closure', is the Directing a Project activity that follows.

  155. Question 155Processes

    Which process prepares the Stage Plan for the next management stage?

    1. Initiating a Project
    2. Closing a Project
    3. Controlling a Stage
    4. Managing a Stage Boundary Correct answer.

    Explanation

    Managing a Stage Boundary is used at the end of every management stage except the final one, and its first activity is to plan the next stage. Controlling a Stage delivers the current stage against the plan that already exists.

  156. Question 156Processes

    In which process is the Project Initiation Documentation assembled?

    1. Directing a Project
    2. Initiating a Project Correct answer.
    3. Starting up a Project
    4. Managing a Stage Boundary

    Explanation

    Initiating a Project takes the Project Brief and develops it into the full Project Initiation Documentation, which then forms the basis for the Project Board's decision to authorise the project. Starting up a Project produces only the Project Brief and the initiation Stage Plan.

  157. Question 157Processes

    Who authorises a work package for issue to a team?

    1. The Team Manager
    2. The Project Manager Correct answer.
    3. Project Assurance
    4. The Project Board

    Explanation

    The Project Manager prepares and authorises the work package, which is the agreement setting out the products to be delivered, the constraints and the reporting required. The Team Manager accepts and executes it under Managing Product Delivery.

  158. Question 158Processes

    Which process spans the period from the appointment of the Executive to the closure of the project?

    1. Directing a Project Correct answer.
    2. Managing a Stage Boundary
    3. Starting up a Project
    4. Controlling a Stage

    Explanation

    Directing a Project is the Project Board's process and runs from the first appointment of the Executive until the project is closed. Starting up a Project occurs before this point, when the mandate is being turned into a Project Brief.

  159. Question 159Processes

    During a stage, the Project Manager forecasts that the stage will exceed its agreed tolerances. What should the Project Manager do?

    1. Take corrective action within the stage and continue as planned
    2. Escalate the forecast to the Project Board using an Exception Report Correct answer.
    3. Ask the Team Manager to renegotiate the work package
    4. Issue an Exception Plan to the Project Board straight away

    Explanation

    Controlling a Stage allows the Project Manager to take corrective action while performance is inside the tolerances, but a forecast breach of stage tolerances must be escalated to the next management level with an Exception Report. An Exception Plan is only produced later, if the board decides to request one.

  160. Question 160Processes

    Which Directing a Project activity allows the Project Board to respond to a request for guidance between formal decision points?

    1. Give ad hoc direction Correct answer.
    2. Authorise project closure
    3. Authorise initiation
    4. Authorise a stage or exception plan

    Explanation

    Give ad hoc direction is the activity that lets the board respond to requests for advice, to Exception Reports and to other information at any time during a stage. The authorisation activities are tied to specific decision points at stage and project boundaries.

  161. Question 161Processes

    When is the 'Produce an exception plan' activity in Managing a Stage Boundary carried out?

    1. Whenever a Team Manager asks for a revised work package
    2. At the end of every management stage as a matter of routine
    3. When the project is being closed before its planned end
    4. When the Project Board has requested an Exception Plan after considering an exception report Correct answer.

    Explanation

    Producing an Exception Plan is part of Managing a Stage Boundary and is triggered when the Project Board, having considered an Exception Report, asks for a plan to replace the current Stage Plan or the project plan. If no exception exists, the only stage-end activity set used is the normal plan-and-report sequence.

  162. Question 162Processes

    The Project Board decides to stop a project before its planned end because the business need has disappeared. Which Closing a Project activity is used?

    1. Prepare planned closure
    2. Evaluate the project
    3. Hand over products
    4. Prepare premature closure Correct answer.

    Explanation

    Closing a Project has two alternative routes: prepare planned closure when the project has delivered as intended, and prepare premature closure when the board stops the project early. Premature closure addresses the extra work of disbanding the team and securing whatever has been produced.

  163. Question 163Processes

    Who approves the Project Initiation Documentation as the basis for authorising the project?

    1. The Team Manager
    2. The Project Board Correct answer.
    3. Project Assurance
    4. The Project Manager

    Explanation

    The Project Manager assembles the Project Initiation Documentation, but it is the Project Board that reviews and approves it as part of the 'Authorise the project' activity. Approval confirms the board's commitment to the project baseline.

  164. Question 164Processes

    Which report does a Team Manager produce to keep the Project Manager informed of progress within a work package?

    1. Highlight Report
    2. Exception Report
    3. End Stage Report
    4. Checkpoint Report Correct answer.

    Explanation

    Checkpoint Reports are produced by the Team Manager at a frequency agreed in the work package and give the Project Manager progress information during execution. Highlight Reports flow the other way, from the Project Manager to the Project Board.

  165. Question 165Processes

    Which document defines the frequency and format of the reports used on a project?

    1. The Business Case
    2. The Quality Management Approach
    3. The Project Plan
    4. The Communication Management Approach Correct answer.

    Explanation

    The Communication Management Approach, prepared in Initiating a Project, sets out the reporting arrangements, including which reports are produced, for whom and how often. The other documents deal with schedule, justification and quality respectively.

  166. Question 166Processes

    Which statement about the outline Business Case is correct?

    1. It is created afresh in Managing a Stage Boundary at the end of each stage
    2. It is produced during Initiating a Project and approved during Closing a Project
    3. It is developed in Starting up a Project and refined during Initiating a Project Correct answer.
    4. It is produced by the Project Board as part of Directing a Project

    Explanation

    An outline Business Case is part of the Project Brief produced in Starting up a Project, giving early justification for the work. It is then developed in detail during Initiating a Project and updated at each stage boundary thereafter.

  167. Question 167Processes

    Which report summarises stage performance and supports the Project Board's decision to authorise the next stage?

    1. End Project Report
    2. End Stage Report Correct answer.
    3. Exception Report
    4. Highlight Report

    Explanation

    The End Stage Report is produced by the Project Manager during Managing a Stage Boundary and is presented with the next Stage Plan so the board can decide whether to authorise the following stage. The End Project Report serves the equivalent purpose at the very end of the project.

  168. Question 168Processes

    Which of the following is an output of the Closing a Project process?

    1. A lessons report Correct answer.
    2. A Project Brief
    3. A Stage Plan
    4. An Exception Plan

    Explanation

    Closing a Project produces the End Project Report, a lessons report and follow-on action recommendations, which are archived for use by future projects. Lessons are also captured continuously in the lessons log, but the formal report is a closure output.

  169. Question 169Processes

    What does the 'Set up the project controls' activity in Initiating a Project define?

    1. The acceptance criteria for each of the project's products
    2. The tolerances, monitoring and reporting arrangements for the project Correct answer.
    3. The team structure and role descriptions for the project
    4. The lessons learned from previous, similar projects

    Explanation

    Setting up the project controls establishes how the project will be monitored and controlled, including the tolerances delegated to each level and the reporting arrangements, and these are recorded in the Project Initiation Documentation. Team structures, acceptance criteria and lessons are handled by other activities.

  170. Question 170Processes

    Why is Managing a Stage Boundary not used at the end of the final management stage?

    1. Because the Project Board has no authority at that point
    2. Because there is no following stage to plan, so Closing a Project is used instead Correct answer.
    3. Because the final Stage Plan is never reviewed
    4. Because the project plan replaces the need for a stage plan

    Explanation

    Managing a Stage Boundary exists to plan the next stage and update the project plan and Business Case before the board authorises continuation. When the final stage ends there is nothing left to plan, so the Project Manager moves into Closing a Project.

  171. Question 171Processes

    A Team Manager has finished the products in a work package and returns them to the Project Manager. Which Controlling a Stage activity covers this?

    1. Review the work package status
    2. Authorise the work package
    3. Take corrective action
    4. Receive completed work packages Correct answer.

    Explanation

    Receiving completed work packages is the point at which the Project Manager confirms that the products have been approved and updates the stage status accordingly. Authorising the work package happens at the start of the work, not at its completion.

  172. Question 172Processes

    Which statement correctly distinguishes Controlling a Stage from Managing Product Delivery?

    1. Managing Product Delivery agrees the work package, while Controlling a Stage ensures the products meet their quality criteria
    2. Controlling a Stage agrees the work package with the team, while Managing Product Delivery ensures the products meet their quality criteria Correct answer.
    3. Controlling a Stage delivers the products, while Managing Product Delivery authorises the work packages
    4. Both processes are performed by the Project Board at different levels of detail

    Explanation

    The Project Manager controls the stage, including agreeing and issuing work packages and monitoring progress, while the Team Manager manages product delivery, including the quality work needed to meet the product descriptions. The two processes meet at the work package boundary.

  173. Question 173Processes

    At what point does Starting up a Project end and the project formally move forward?

    1. When the project mandate is first received by the Executive
    2. When the Project Brief has been written and the Project Manager appointed
    3. When the Project Board authorises initiation in Directing a Project Correct answer.
    4. When the stage plan for the initiation stage has been produced

    Explanation

    The activities of Starting up a Project produce the Project Brief, the initiation Stage Plan and the request to initiate a project, but the process concludes only when the Project Board responds by authorising initiation through Directing a Project. Producing the documents alone does not end the pre-project stage.

  174. Question 174Processes

    Which Closing a Project activity confirms that the customer has accepted the project's products and that operational responsibilities are in place?

    1. Give ad hoc direction
    2. Authorise a stage or exception plan
    3. Hand over products Correct answer.
    4. Evaluate the project

    Explanation

    Handing over products confirms that the customer has taken delivery and acceptance, and that the arrangements for operating, maintaining and supporting the products are established. It complements the acceptance of products that occurred at the end of the final stage.

  175. Question 175Processes

    Which products does Managing a Stage Boundary update, in addition to preparing the next Stage Plan?

    1. The Communication Management Approach and the Quality Management Approach
    2. The Project Brief and the project mandate
    3. The lessons log and the daily log only
    4. The project plan and the Business Case Correct answer.

    Explanation

    At each stage boundary the Project Manager plans the next stage, updates the project plan to reflect actual progress and revised forecasts, and updates the Business Case to confirm the project remains viable. The approaches and the Project Brief are not the focus of this process.

  176. Question 176Processes

    Which input triggers the Starting up a Project process?

    1. Project Initiation Documentation
    2. Project Mandate Correct answer.
    3. Project Brief
    4. Stage Plan

    Explanation

    Starting up a Project is the pre-project process and is triggered by the Project Mandate, which comes from outside the project and describes the need for it. The Project Brief is created during the process itself, not before it.

  177. Question 177Processes

    Which PRINCE2 process is owned by the Project Board?

    1. Directing a Project Correct answer.
    2. Managing a Stage Boundary
    3. Initiating a Project
    4. Controlling a Stage

    Explanation

    Directing a Project is the only process whose activities are performed by the Project Board, covering key decision points from project initiation to closure. The other processes are performed by the Project Manager or Team Manager.

  178. Question 178Processes

    Which process covers the Project Manager's day-to-day management of work within a management stage?

    1. Managing Product Delivery
    2. Managing a Stage Boundary
    3. Directing a Project
    4. Controlling a Stage Correct answer.

    Explanation

    Controlling a Stage is the Project Manager's process for authorising work packages, monitoring progress, dealing with issues and risks, and taking corrective action during a stage. It does not include the decisions reserved for the Project Board.

  179. Question 179Processes

    Which process is used by the Team Manager to accept, execute and deliver a work package?

    1. Managing a Stage Boundary
    2. Directing a Project
    3. Managing Product Delivery Correct answer.
    4. Controlling a Stage

    Explanation

    Managing Product Delivery defines the interface between the Project Manager and the Team Manager, covering the acceptance, execution and delivery of work packages. Controlling a Stage is the Project Manager's counterpart process.

  180. Question 180Processes

    What is the first activity of the Starting up a Project process?

    1. Prepare the outline Business Case
    2. Plan the initiation stage
    3. Appoint the Executive and the Project Manager Correct answer.
    4. Design the project management team

    Explanation

    The process begins by appointing the Executive and the Project Manager, because the remaining activities require these roles to exist and to make decisions. Only then can the outline Business Case be prepared and the team designed.

  181. Question 181Processes

    Which Controlling a Stage activity produces the Highlight Report?

    1. Take corrective action
    2. Authorise a Work Package
    3. Review the stage status
    4. Report highlights Correct answer.

    Explanation

    The Report highlights activity gathers and formats the information the Project Board needs at its agreed reporting frequency, producing the Highlight Report. Reviewing stage status is a separate activity that supplies the data used.

  182. Question 182Processes

    Which process is used to bring a project to a controlled close once its final products have been delivered?

    1. Directing a Project
    2. Controlling a Stage
    3. Managing a Stage Boundary
    4. Closing a Project Correct answer.

    Explanation

    Closing a Project is entered at the end of the final management stage to confirm acceptance, hand over products, evaluate the project and recommend closure. Managing a Stage Boundary is not used at the end of the final stage for exactly this reason.

  183. Question 183Processes

    Which process establishes solid foundations for the project and produces the Project Initiation Documentation?

    1. Starting up a Project
    2. Directing a Project
    3. Initiating a Project Correct answer.
    4. Managing a Stage Boundary

    Explanation

    Initiating a Project is where the strategies, controls, Project Plan and Business Case are developed and assembled into the Project Initiation Documentation. Starting up a Project only produces the Project Brief.

  184. Question 184Processes

    Which Initiating a Project activity updates the project's justification with the detailed costs and timescales from the Project Plan?

    1. Assemble the Project Initiation Documentation
    2. Refine the Business Case Correct answer.
    3. Create the Project Plan
    4. Set up the project controls

    Explanation

    The outline Business Case from Starting up a Project is only indicative, so initiation refines it using the detailed cost and time information produced by the Project Plan. This gives the Project Board a reliable basis for authorising the project.

  185. Question 185Processes

    Which Controlling a Stage activity confirms that a work package is ready and issues it to the team?

    1. Authorise a Work Package Correct answer.
    2. Report highlights
    3. Receive completed work packages
    4. Review Work Package status

    Explanation

    Authorise a Work Package is where the Project Manager checks that the work package is properly defined, agreed and within tolerance before it is issued. Reviewing status only happens once the team is already working.

  186. Question 186Processes

    Which Controlling a Stage activity compares actual progress with the Stage Plan and assesses performance against tolerances?

    1. Capture and examine issues and risks
    2. Take corrective action
    3. Review the stage status Correct answer.
    4. Escalate issues and risks

    Explanation

    Review the stage status is the activity in which the Project Manager assesses progress, forecasts and tolerance position against the approved Stage Plan. It is the trigger for deciding whether corrective action or escalation is needed.

  187. Question 187Processes

    Which Managing Product Delivery activity confirms that a work package can be completed within its agreed tolerances before work starts?

    1. Deliver a Work Package
    2. Authorise a Work Package
    3. Execute a Work Package
    4. Accept a Work Package Correct answer.

    Explanation

    Accept a Work Package is where the Team Manager reviews the work package, agrees the plan and confirms it can be delivered within the stated constraints. Only after acceptance does execution begin.

  188. Question 188Processes

    In which process is the End Stage Report prepared?

    1. Managing a Stage Boundary Correct answer.
    2. Initiating a Project
    3. Controlling a Stage
    4. Closing a Project

    Explanation

    The End Stage Report is created in Managing a Stage Boundary so that the Project Board can compare actual stage performance with the Stage Plan and decide whether to authorise the next stage. Closing a Project uses an End Project Report instead.

  189. Question 189Processes

    Which Starting up a Project activity determines the roles and structure of the project management team?

    1. Prepare the outline Business Case
    2. Capture previous lessons
    3. Appoint the Executive and the Project Manager
    4. Design the project management team Correct answer.

    Explanation

    Design the project management team defines the composition of the team, including which roles are needed and how they relate to each other. Appointing the Executive and Project Manager is a separate, earlier activity that covers only those two roles.

  190. Question 190Processes

    Which Starting up a Project activity gathers experience from comparable projects to inform how this project should be run?

    1. Capture previous lessons Correct answer.
    2. Design the project management team
    3. Select the project approach and assemble the Project Brief
    4. Plan the initiation stage

    Explanation

    Capture previous lessons collects lessons from similar projects or from corporate records so that known problems and good practice can be reflected in the Project Brief and in the approach. It is a distinct activity from selecting the project approach.

  191. Question 191Processes

    In which process is the Project Plan created?

    1. Directing a Project
    2. Starting up a Project
    3. Initiating a Project Correct answer.
    4. Managing a Stage Boundary

    Explanation

    The Project Plan is created in Initiating a Project through the Create the Project Plan activity, giving the Project Board a whole-project baseline to authorise. Managing a Stage Boundary uses that baseline but only produces Stage Plans.

  192. Question 192Processes

    Which Directing a Project activity approves the next Stage Plan and authorises the Project Manager to proceed?

    1. Authorise project closure
    2. Authorise a stage or exception plan Correct answer.
    3. Authorise the project
    4. Give ad hoc direction

    Explanation

    Authorise a stage or exception plan is the decision point at a stage boundary where the Board reviews the End Stage Report and next Stage Plan before granting authority to continue. Authorise the project is a different, earlier decision taken after initiation.

  193. Question 193Processes

    Which Closing a Project activity compares the project's actual results with the baselines set at initiation?

    1. Prepare planned closure
    2. Evaluate the project Correct answer.
    3. Hand over products
    4. Recommend project closure

    Explanation

    Evaluate the project compares what was actually delivered, spent and achieved against the original baseline so that lessons and performance can be reported. It is distinct from the administrative steps of handing over products and recommending closure.

  194. Question 194Processes

    In which process does the Project Manager capture and examine issues and risks arising during a stage?

    1. Controlling a Stage Correct answer.
    2. Initiating a Project
    3. Managing Product Delivery
    4. Managing a Stage Boundary

    Explanation

    Controlling a Stage includes an activity for capturing and examining issues and risks, because they arise continuously while work is in progress and must be assessed as they occur. Some are resolved within the stage and others are escalated to the Project Board.

  195. Question 195Processes

    Which Starting up a Project activity assembles the Project Brief, including the chosen delivery method?

    1. Capture previous lessons
    2. Select the project approach and assemble the Project Brief Correct answer.
    3. Design the project management team
    4. Plan the initiation stage

    Explanation

    Select the project approach and assemble the Project Brief brings together the mandate, the outline Business Case, the team design and the chosen delivery approach into a single document. It is the activity that produces the Brief as a management product.

  196. Question 196Processes

    A stage is forecast to breach its agreed tolerances and the Project Manager has no authority to resolve the matter. Which Controlling a Stage activity addresses this?

    1. Authorise a Work Package
    2. Report highlights
    3. Escalate issues and risks Correct answer.
    4. Receive completed work packages

    Explanation

    Escalate issues and risks is used when the Project Manager cannot resolve a problem within the tolerances delegated to them, typically producing an Exception Report for the Project Board. It follows the review of stage status that identified the forecast breach.

  197. Question 197Processes

    Which Closing a Project activity is performed when the Project Board decides to stop the project before all products are delivered?

    1. Evaluate the project
    2. Prepare premature closure Correct answer.
    3. Recommend project closure
    4. Prepare planned closure

    Explanation

    Prepare premature closure is the activity used when the project ends early, confirming what has been delivered and what remains, so the closure is still controlled. Prepare planned closure applies only when the end is reached as planned.

  198. Question 198Processes

    Which Initiating a Project activity defines how product versions and changes to products will be identified and controlled?

    1. Create the Project Plan
    2. Refine the Business Case
    3. Prepare the Configuration Management Strategy Correct answer.
    4. Prepare the Communication Management Strategy

    Explanation

    The Configuration Management Strategy sets out how products will be identified, version-controlled, protected and tracked, including how changes are handled. It is prepared during initiation so that configuration control exists before product development starts.

  199. Question 199Processes

    Which Directing a Project activity confirms that the project may be brought to an end?

    1. Authorise project closure Correct answer.
    2. Give ad hoc direction
    3. Authorise a stage or exception plan
    4. Authorise the project

    Explanation

    Authorise project closure is the Board's final decision, taken after reviewing the End Project Report and confirming that there is nothing further to be gained. It follows the Project Manager's recommendation made in Closing a Project.

  200. Question 200Processes

    The Project Board has reviewed the assembled Project Initiation Documentation and commits the resources needed for the whole project. Which Directing a Project activity has just taken place?

    1. Authorise initiation
    2. Authorise a stage or exception plan
    3. Authorise project closure
    4. Authorise the project Correct answer.

    Explanation

    Authorise the project is the decision taken after initiation, when the Board is satisfied with the Project Initiation Documentation and commits the resources required for the whole project. Authorise initiation is the earlier decision that allows initiation to be carried out at all.

PRINCE2 Foundation flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Continued business justification
A PRINCE2 principle requiring a justifiable, documented and approved Business Case that is reviewed and updated throughout the project; without it the project should be stopped.
Learn from experience
A principle requiring lessons to be sought, recorded and acted on throughout the project; PRINCE2 uses a lessons log and lessons reports to transfer knowledge.
Defined roles and responsibilities
A principle requiring clear accountability and agreed roles across business, user and supplier interests, documented in the project organization and used to control decision-making.
Manage by stages
A principle requiring at least two management stages, initiation plus one or more delivery stages, so the project board can control progress at key decision points.
Manage by exception
A principle using agreed tolerances for time, cost, scope, quality, risk and benefits; work proceeds within tolerance and escalates only if tolerances are forecast to be exceeded.
Focus on products
A principle requiring the project to define its products and quality criteria before doing work; product descriptions drive planning, execution and acceptance.
Tailor to suit
A principle requiring PRINCE2 practices and processes to be adapted proportionately to project size, complexity, risk and environment; principles themselves are never omitted.
PRINCE2 principles characteristics
The seven principles are universal, self-validating, empowering and applicable to every project; applying all seven is what makes a project PRINCE2.
People management approach
A tailored description of how the project will address people aspects such as leadership, communication, motivation and stakeholder engagement; it may be part of project initiation documentation.
Stakeholder analysis
Identifying stakeholders, then assessing their interest, influence and attitude to plan appropriate engagement; results inform the communication management approach.
Communication management approach
A project document defining who needs what information, when, in what format and through which channel; it is based on stakeholder analysis and is kept current.
Leadership versus management
Leadership sets direction, aligns and motivates people; management plans, organizes and controls resources. PRINCE2 projects need both, adapted to the project situation.
Team development stages
Forming, storming, norming and performing describe how teams mature; a project manager should recognize the stage and adapt support and communication accordingly.
Emotional intelligence
The ability to recognize and manage one's own emotions and those of others; components include self-awareness, self-regulation, motivation, empathy and social skills.
Business case practice
Establishes mechanisms to judge whether the project is desirable, viable and achievable; outputs include the Business Case and benefits management approach, reviewed at stage boundaries.
Organization practice
Defines roles, responsibilities and accountability for business, user and supplier interests; it establishes the project board and project management team structure.
Quality practice
Defines and controls how products meet requirements; activities include quality planning, quality control, quality assurance, product descriptions and a quality register.
Plans practice
Defines how products will be delivered; PRINCE2 plan levels are project, stage, team and exception plans, and planning is product-based.
Risk practice
Identifies, assesses and controls uncertainty; outputs include risk management approach and risk register, with responses implemented and communicated through the project.
Change practice
Controls baselines and changes; it uses a change control approach, issue register and change authority to assess, approve or reject changes and record decisions.
Progress practice
Monitors and controls performance against plans; controls include checkpoints, highlight reports, end stage assessments and exception reports, using tolerances and dashboards.
Product description
A document defining a product's purpose, composition, quality criteria, quality method and acceptance responsibilities; it is used in plans and work packages.
Benefits management approach
Defines how benefits will be measured, reviewed and realized after the project; it is created during initiation and updated through the project.
Starting up a Project
The pre-project process that appoints the project manager and team, captures lessons, prepares the project brief, outline business case and initiation stage plan.
Directing a Project
The project board process that authorizes initiation, the project, stage or exception plans, gives ad hoc direction and authorizes project closure.
Initiating a Project
Establishes the project's controls and documents; it develops the project initiation documentation, business case, plans, and quality, risk and change approaches for board authorization.
Controlling a Stage
The project manager's process for authorizing, monitoring and reviewing work packages, reporting progress, handling issues and escalating exceptions to the project board.
Managing Product Delivery
The process where the team manager authorizes, accepts and executes work packages and confirms delivery and acceptance of products to the project manager.
Managing a Stage Boundary
Prepares the next stage plan, updates the project plan and business case, reports stage end performance and requests project board authorization to continue.
Closing a Project
Confirms product acceptance, prepares closure documentation, evaluates project performance, reviews benefits and captures lessons before the project board authorizes closure.
Project brief
A starting-up output defining the project's purpose, scope, objectives, constraints, risks and outline business case; it supports the project board's decision to initiate.
Work package
A set of product descriptions, activities and resources assigned to a team manager; it is authorized in Controlling a Stage and accepted in Managing Product Delivery.

PRINCE2 Foundation study guide

Principles: the non-negotiable foundations of PRINCE2

What you must know

PRINCE2 has seven principles: continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to the project environment. In the current edition they sit alongside the practices and the People element as one of the method's core elements.

Candidates are expected to explain why they are principles rather than optional techniques. They are universal (they apply to every project, whatever its size, sector or delivery approach), self-validating (they embody proven good practice), and empowering (they give the project board confidence that the project is being run properly). Crucially, they must be applied all together; a project that applies only a selection is not using PRINCE2.

Traps in questions

  • Tailoring is itself a principle, so principles are never 'tailored out'. What you tailor is the how of the practices and processes, not the principles themselves.
  • Each scenario description usually maps to one principle only. Manage by exception is about tolerances and only escalating when a tolerance is forecast to be breached. Manage by stages is about breaking the project into reviewable chunks with board decisions between them. Focus on products is about defining and agreeing products and their quality criteria before doing the work.
  • Learn from experience is not just 'keep a lessons log'; it means acting on lessons throughout, not only at closure.

Rule of thumb

If you could sensibly drop it on a small, low-risk project, it is a practice or a process activity, not a principle. Principles survive every tailoring decision.

People: leadership, roles and working together

What you must know

The People element recognises that projects are delivered by human beings, not by documents. It covers good practice in leading successful teams (the difference between management and leadership, motivating and developing the team, adapting your style to the situation and to the individuals), communication (planning who needs what information, when, and in what form), collaboration and self-management (empowering teams with clear objectives and the authority to act), and the influence of organisational culture on how a project runs.

People questions almost always hinge on the role model, so learn it precisely. There are three project interests (business, user, supplier) represented on the project board by the executive, senior user(s) and senior supplier(s). The executive is ultimately accountable for the project and owns the business case; senior users specify benefits and products; senior suppliers provide resources and expertise; the project manager runs the project day to day; the team manager (optional) manages product delivery; project assurance monitors the board's interests and project support administers the method's products.

Traps in questions

  • People is neither a principle nor a practice; don't confuse the elements.
  • Accountability cannot be delegated. The board may delegate activities (project assurance, change authority, project support) but it keeps its accountability.
  • The project board's accountability is collective, yet business-case ownership sits specifically with the executive.

Rule of thumb

When asked 'who is responsible?', separate accountable (executive or board) from responsible for doing (project manager, team manager, project support).

Practices: the seven management disciplines

What you must know

PRINCE2 has seven practices: business case, organizing, plans, quality, risk, issues and progress. Each is described by its purpose, its key concepts, the roles involved, the products it creates and how it can be tailored.

  • Business case: outputs, outcomes and benefits (plus dis-benefits); justification is reviewed at every stage boundary and whenever a change or exception arises.
  • Plans: three levels - project, stage and team - plus exception plans. Plans use product-based planning: product breakdown structure, product descriptions, then a product flow diagram.
  • Quality: quality planning (what is required) versus quality control (checking it has been achieved); techniques include quality review, and records include the quality register and acceptance records.
  • Risk: cause → event → effect; risk appetite versus risk tolerance; risk management approach and risk register.
  • Issues: types of issue, change control approach, issue register and change authority.
  • Progress: management stages, tolerances and reports - checkpoint, highlight, end stage and end project - plus lessons.

Traps in questions

  • Mixing up the registers (quality, risk, issue) and the logs (lessons). Registers track live items needing action; the lessons log is a continuing record of lessons, which feeds the lessons report at closure.
  • Confusing the quality register (planned and completed quality activities) with a product description (the product's quality criteria).
  • Forgetting that each practice's approach (risk, quality, change control) is baselined in the project initiation documentation.

Rule of thumb

Ask 'is this planning the requirement or controlling against it?' - planning sits in approaches and product descriptions, control sits in registers and reports.

Processes: the seven-step project lifecycle

What you must know

The seven processes, in lifecycle order, are: starting up a project (SU), directing a project (DP), initiating a project (IP), controlling a stage (CS), managing product delivery (MP), managing a stage boundary (SB) and closing a project (CP). Each has activities, and each activity has recommended actions and outputs - none of which are mandatory in detail once tailored.

Learn what each process produces. SU is pre-project and produces the project brief (and the outline business case) so the board can decide whether initiation is worth funding. DP runs for the whole project and is the board's process: its activities are authorising initiation, authorising the project, authorising a stage or exception plan, giving ad hoc direction, and authorising project closure. IP produces the project initiation documentation. CS is the project manager's day-to-day controlling of work packages, issues and risks, reviews and reports. MP is where the team manager accepts, executes and delivers a work package. SB plans the next stage (or an exception plan) and reports on the ending stage. CP confirms acceptance, evaluates the project and recommends closure.

Traps in questions

  • Authorising always belongs to DP, never to the project manager.
  • SB is used at the end of every stage except the final one, where CP follows instead.
  • A stage can contain several work packages; MP is not a stage.
  • SU is not part of the project itself - it happens before initiation is authorised.

Rule of thumb

At every boundary, the board decides; the project manager prepares and seeks approval. If a question says 'approve' or 'authorise', the answer is almost always a project board action in DP.

PRINCE2 Foundation cheat sheet

Quick reference

Principles

  • The seven PRINCE2 principles are: continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to suit the project environment.

  • PRINCE2 principles are universal, self-validating, empowering, and applicable to every project; applying all seven is what makes a project PRINCE2.

  • Continued business justification requires a justifiable, documented, and approved Business Case that is reviewed and updated throughout the project.

  • Manage by stages requires at least two management stages: an initiation stage and at least one further management stage.

  • Manage by exception uses tolerances for time, cost, scope, quality, risk, and benefits; escalation occurs only when a tolerance is forecast to be exceeded.

  • Focus on products means defining products and their quality criteria before work begins; product descriptions drive planning and acceptance.

  • Tailor to suit the project environment means adapting practices and processes proportionately to size, complexity, risk, and context, without omitting principles.

  • Learn from experience requires lessons to be sought, recorded, and acted on throughout the project, supported by a lessons log and lessons reports.

  • Defined roles and responsibilities require clear accountability across business, user, and supplier interests, documented in the project organization.

Quick reference

People

  • PRINCE2 addresses people aspects including leading successful change, communication, motivation, stakeholder engagement, and team management.

  • A people management approach defines how the project will handle people aspects; it is tailored to the project and may form part of the project initiation documentation.

  • Stakeholder analysis identifies stakeholders and assesses their interest, influence, and attitude so that engagement and communication can be planned.

  • The communication management approach defines who needs what information, when, in what format, and through which channel.

  • Leadership sets direction and motivates people, while management plans, organizes, and controls resources; projects typically require both.

  • Team development stages are forming, storming, norming, and performing; recognizing the stage helps a project manager adapt support and communication.

  • Emotional intelligence includes self-awareness, self-regulation, motivation, empathy, and social skills, and supports effective project leadership.

  • PRINCE2 does not prescribe a single leadership style or motivation theory; the approach is selected and tailored to the people and context.

Quick reference

Practices

  • The seven PRINCE2 practices are business case, organization, quality, plans, risk, change, and progress.

  • The business case practice establishes whether the project is desirable, viable, and achievable; outputs include the Business Case and benefits management approach.

  • The organization practice defines roles, responsibilities, and accountability across business, user, and supplier interests, including the project board.

  • The quality practice covers quality planning, quality control, and quality assurance, using product descriptions and a quality register.

  • The plans practice uses product-based planning and defines project, stage, team, and exception plans.

  • The risk practice uses a risk management approach and risk register; risks are identified, assessed, responded to, implemented, and communicated.

  • The change practice uses a change control approach, issue register, and change authority to assess, approve or reject changes and record decisions.

  • The progress practice uses checkpoints, highlight reports, end stage assessments, and exception reports to monitor performance against plans and tolerances.

  • Each PRINCE2 practice includes tailoring guidance so that its application is proportionate to the project's size, complexity, and risk.

Quick reference

Processes

  • The seven PRINCE2 processes are Starting up a Project, Directing a Project, Initiating a Project, Controlling a Stage, Managing Product Delivery, Managing a Stage Boundary, and Closing a Project.

  • Starting up a Project is a pre-project process that appoints the project manager and team, captures lessons, prepares the project brief and outline business case, and plans initiation.

  • Directing a Project is the project board process that authorizes initiation, the project, stage or exception plans, ad hoc direction, and project closure.

  • Initiating a Project establishes project controls and develops the project initiation documentation, business case, plans, and quality, risk, and change approaches.

  • Controlling a Stage covers authorizing work packages, monitoring and reviewing work, reporting progress, handling issues, and escalating exceptions.

  • Managing Product Delivery covers authorizing, accepting, and executing work packages, and confirming delivery and acceptance of products.

  • Managing a Stage Boundary prepares the next stage plan, updates the project plan and business case, reports stage end performance, and requests authorization to continue.

  • Closing a Project confirms product acceptance, prepares closure documentation, evaluates performance, reviews benefits, and captures lessons before closure authorization.

PRINCE2 Foundation key terms

Continued business justification

The principle that a project must have a valid reason to exist before it starts, and that this reason must be reviewed and remain sound throughout; if it fails, the project is changed or stopped.

Related: Business case, Manage by exception
Learn from experience

The principle that a project team should deliberately seek out lessons from previous work and from its own progress, then act on them instead of simply recording them.

Related: Lessons log, Lessons report
Defined roles and responsibilities

The principle that a project needs an explicit, agreed structure showing who does what, with clear accountability and authority understood by everyone involved.

Related: Project board, Project manager
Manage by stages

The principle of splitting the project into manageable chunks, each with its own plan and decision point, so that commitment grows only as detail and confidence grow.

Related: End stage report, Manage by exception
Manage by exception

The principle that a higher level sets boundaries for delegated work and intervenes only when those boundaries are forecast to be exceeded, freeing managers from constant reporting.

Related: Tolerance, Exception
Focus on products

The principle that a project should first agree what outputs it will create and the quality they must meet, and only then decide the activities needed to create them.

Related: Product description, Acceptance criteria
Tailor to suit the project environment

The principle that PRINCE2 must be adapted in depth, rigour and terminology to fit the project's size, complexity, risk, delivery approach and the organisation's existing ways of working.

Stakeholder

Any individual, group or organisation that can affect, be affected by, or reasonably perceive itself to be affected by the project, its outputs or its outcomes.

Related: Stakeholder engagement, Communication management approach
Stakeholder engagement

The continuing work of identifying the people with an interest in the project, judging their influence and interest, and deciding how to involve and communicate with them.

Related: Stakeholder, Communication management approach
Communication management approach

A document setting out how the project will keep people informed: which audiences need which information, in what format, how often and who is responsible for sending it.

Related: Stakeholder engagement
Business case

The documented justification for the project, covering the reasons for it, expected benefits, costs, timescales and key risks, and reviewed at each stage boundary to confirm it still holds.

Related: Benefit, Continued business justification
Benefit

A measurable improvement created by an outcome that one or more stakeholders judge to be an advantage; benefits are usually realised after the project has closed.

Related: Outcome, Business case
Outcome

The changed situation that results once the project's outputs are put to use by the organisation; the project influences it but does not fully control it.

Related: Benefit, Business case
Project board

The group accountable for the project, made up of an executive, senior users and senior suppliers, which directs the work and takes the key decisions within its authority.

Related: Executive, Senior user, Project manager
Executive

The single person ultimately accountable for the project, who owns the business case, chairs the project board on behalf of the business and judges whether the project remains worthwhile.

Related: Project board, Business case
Senior user

The project board role representing the people who will use or gain from the outputs; this person specifies user needs and later confirms that the expected benefits are achieved.

Related: Project board, Benefit
Project manager

The person who runs the project day to day within the limits set by the project board, delivering the agreed products at the required quality and escalating when limits are threatened.

Related: Project board, Tolerance
Tolerance

The amount of deviation allowed from a plan's target in time, cost, scope, quality, benefit or risk before the matter must be referred to the next level of management.

Related: Exception, Manage by exception
Exception

A forecast that an agreed tolerance will be exceeded, which must be reported upwards so that the level above can decide how the project should respond.

Related: Tolerance, Exception plan
Risk

An uncertain event that, if it happens, will affect the project's objectives; it is described through its cause, the event itself and the effect it would have.

Related: Risk register, Risk appetite
Risk appetite

The degree of uncertainty an organisation or individual is prepared to accept in pursuit of objectives, which guides how much risk is tolerated and how risks are handled.

Related: Risk, Risk register
Risk register

A working record of the project's risks, showing how each is assessed, who owns it and what response is planned, kept up to date as the project proceeds.

Related: Risk, Risk appetite
Issue

An event that has already happened, was not planned and needs management action; examples include a request for change, a problem, or a product forecast to fail its requirements.

Related: Off-specification, Project manager
Off-specification

A situation where a product is expected not to meet one or more of its agreed requirements, which must be raised as an issue and handled through change control.

Related: Issue, Product description
Product description

A statement of what a product must be like: its purpose, composition, quality criteria, the method used to check quality, and who produces and approves it.

Related: Acceptance criteria, Quality control
Acceptance criteria

The measurable conditions a product must satisfy before the customer will accept it; for the whole project these are set out in the project product description.

Related: Product description
Quality control

Checking that products actually meet their agreed quality criteria, for example through reviews, inspections or tests, and recording the outcome of each check.

Related: Acceptance criteria, Product description
Project mandate

The trigger that starts a project: a brief statement from the commissioning organisation giving enough information to justify doing initial start-up work.

Related: Project brief
Project brief

A document created while starting up the project that outlines purpose, scope, objectives and an initial business case, giving the basis for planning the initiation work.

Related: Project mandate, Project initiation documentation (PID)
Project initiation documentation (PID)

The collection of documents produced during initiation that sets out the project's rationale, governance, plans, controls and business case, and forms the basis for the board's authorisation.

Related: Business case, Project brief
Directing a project

The project board's process for making decisions at key points: authorising initiation, authorising the project, each stage or exception plan, giving ad hoc direction, and authorising closure.

Related: Project board, Tolerance
Managing product delivery

The process in which the team manager accepts a work package, carries out the work, keeps progress visible and returns the finished products for approval.

Related: Work package, Checkpoint report
Work package

The description of a piece of work given to a team, covering the products to be produced, time, cost, tolerances, constraints and the reporting expected while the work runs.

Related: Managing product delivery, Product description
Checkpoint report

A regular report from the team manager to the project manager giving progress, status of the assigned work and any issues arising during the reporting period.

Related: Work package, Highlight report
Highlight report

A progress report from the project manager to the project board at agreed intervals, summarising stage status and flagging any forecast deviation from agreed tolerances.

Related: Checkpoint report, Tolerance
End stage report

A report written at the close of a management stage that summarises performance so far and gives the project board what it needs to decide how to proceed.

Related: Manage by stages
End project report

A report produced when the project is closed, reviewing performance against the plan and the business case and confirming whether the project's objectives were met.

Related: Business case, Closing a project
Lessons log

A running record of lessons identified during the project, together with what should be done differently, used to improve the work as it continues.

Related: Learn from experience, Lessons report
Lessons report

A report produced at the end of a stage or of the project that summarises the lessons found and recommends improvements for future projects and the wider organisation.

Related: Lessons log, Learn from experience
Closing a project

The process of confirming that products are accepted, reviewing benefits and lessons, and handing over ongoing responsibilities so the project can be ended in a controlled way.

Related: End project report, Lessons report

PRINCE2 Foundation study plan

8 weeks · About 6 hours per week

Week 1

Processes

  • Map all seven PRINCE2 processes onto a single-page flow showing how each process triggers the next

  • Explain the purpose and key outputs of 'starting up a project', including the project brief and daily log

  • Describe how 'directing a project' decision points link to stage boundaries and to the project board's authority

  • Reproduce the activities of each process from memory, then check your version against the manual and correct gaps

Your checkpoint

A one-page hand-drawn process flow diagram plus a 10-question self-test on process purpose and sequencing, scored at 8/10 or better.

Week 2

Processes

  • Sequence the activities of 'initiating a project' and name the management products each activity creates

  • Distinguish 'controlling a stage' from 'managing product delivery' using work package, checkpoint report and quality register examples

  • Explain how 'managing stage boundaries' and 'closing a project' interact with project board decisions

  • Answer 40 practice questions on processes and log every wrong answer with the correct rationale in your own words

Your checkpoint

An error log of at least 15 reviewed questions with corrected explanations, and a score of 65% or better on a 40-question process-only quiz.

Week 3

Practices

  • Summarise the purpose, key roles and core management products of the business case, organising, plans and risk practices

  • Draft a one-page business case outline and a simple product-based plan for a small sample project

  • Build a risk register with six entries, each scored for probability and impact and assigned an owner

  • Compare the project manager's and project board's responsibilities across these four practices

Your checkpoint

Four one-page practice summary sheets (business case, organising, plans, risk) plus a completed six-entry sample risk register.

Week 4

Practices

  • Explain how the quality, issues and progress practices produce the quality register, issue register and progress reports

  • Describe the recommended issue and change control procedure step by step, and where a change authority fits

  • Apply tolerance and exception-reporting rules to three short scenarios and state the correct escalation path

  • Sit a 60-question timed mock covering Practices and Processes and analyse the result by sub-topic

Your checkpoint

A timed 60-question mock scored at 70% or better, accompanied by a written ranked list of your five weakest sub-topics in domains 3 and 4.

Week 5

Principles

  • State all seven principles from memory and explain in writing how each one would show up in a real project

  • Identify tailoring decisions in a short case study and justify each one against the principles

  • Write two exam-style application questions per principle and answer them without notes

  • Mark your own answers strictly and rewrite any principle you cannot apply confidently

Your checkpoint

Seven principle flashcards plus 14 self-written application questions answered in writing, self-marked at 80% or better.

Week 6

People

  • Describe the people elements of leading a successful team, collaboration and stakeholder communication in your own words

  • Build a role matrix mapping project board, project manager, team manager, project assurance, project support and change authority to their responsibilities

  • Explain how the approach to people and roles changes with project size, complexity and organisational context

  • Complete a 25-question quiz on People and Principles and review every incorrect answer

Your checkpoint

A complete role-and-responsibility matrix covering all PRINCE2 roles plus a 25-question People and Principles quiz scored at 75% or better.

Week 7

Principles & People & Practices & Processes

  • Sit two full-length timed mocks under exam conditions and mark them without giving yourself the benefit of the doubt

  • Re-study only the five weakest sub-topics revealed by the mock analysis

  • Convert your error log into one-page trigger sheets for the facts you keep missing

  • Practise question technique: eliminate options, spot distractor wording and manage time per question

Your checkpoint

Two completed full-length mocks with scores recorded and a prioritised list of remaining weak areas, each matched to a page of notes or a trigger sheet.

Week 8

Principles & People & Practices & Processes

  • Complete a final full-length mock within the time limit and score 80% or better

  • Perform a blank-page recall dump of the seven principles, seven practices, seven processes, roles and key management products

  • Review only the trigger sheets and error log, introducing no new material

  • Rehearse the exam-day routine: timing checkpoints, flag-and-return strategy and a final ten-minute review pass

Your checkpoint

A blank-page recall test scoring 100% on the framework skeleton, plus a final timed mock scored at 80% or better.

Milestones

Week 2: Score 65% or better on the 40-question process-only quiz and show an error log with at least 15 corrected entries.

Week 4: Score 70% or better on the 60-question Practices and Processes mock and produce a written ranked weak-area list.

Week 6: Score 75% or better on the 25-question People and Principles quiz and show a complete role-and-responsibility matrix.

Week 8: Score 80% or better on a final full-length timed mock and complete the blank-page framework recall without prompts.

PRINCE2 Foundation exam day

Your checklist

Government-issued photo ID

Bring the original ID in the name used on your booking. Which specific document types are accepted (passport, driving licence, national ID) is set by the exam provider, so confirm the accepted list with the provider before the exam.

Appointment confirmation / candidate reference

Have your booking confirmation, candidate number and the provider's contact details to hand in case of a technical or scheduling problem. Whether a printed copy is required depends on the venue - confirm with the provider.

Working webcam, microphone and stable internet (online-proctored sittings)

If you are sitting the exam remotely, test the equipment and run any required system/identity check in advance, and have a backup connection (e.g. mobile tethering) ready.

A quiet, well-lit room with a clear desk

For remote sittings, remove notes, books, phones, smart watches and any second screen from the desk and the room. The proctor may ask you to pan the camera around the space.

No reference material - Foundation is a closed-book exam

You cannot use the PRINCE2 manual, notes, flashcards or printed summaries during the exam, so revise definitions and process flows into memory beforehand.

Writing materials (only if permitted)

Some sittings allow a pen and a blank or erasable sheet for rough work; others provide it or forbid it. Check what is permitted for your delivery mode with the provider.

Know the paper structure cold

Foundation is a multiple-choice exam of 60 questions in 60 minutes, closed book, with a pass mark of 55% (33 of 60). Knowing this shapes your pacing: roughly one minute per question.

Logistics and travel plan (test-centre sittings)

Plan your route in advance and allow a generous buffer for check-in and security. The exact arrival/check-in window is set by the venue - confirm it with the provider.

Approved access arrangements, if you need them

Extra time or other reasonable adjustments are normally requested in advance, not on the day. If you need any, confirm the process and deadlines with the provider well before the exam.

Completed practice papers

Before exam day, do at least one or two full-length timed practice sets so you know your pace and can recognise the 'which principle/theme/process is this' style of question quickly.

A one-page revision sheet for the final hour

Condense the 7 principles, 7 themes and 7 processes plus the purpose of each process into a single page. Use it before you travel, then put it away - it cannot go into the exam room.

Water and a settled routine

Bring water if the venue or remote-exam rules allow it (confirm with the provider) and avoid last-minute cramming that leaves you tired.

Plan the day

72 hours before

Confirm the appointment details - date, time, time zone, venue or remote-exam platform - and re-read the provider's candidate instructions so there are no surprises about ID or check-in.

72 hours before

Run one full timed practice set under exam conditions (60 questions, 60 minutes, no notes). Mark it, then spend the review time on the areas that were weakest.

72 hours before

Test your technology for a remote sitting: webcam, microphone, browser compatibility, any proctoring software, and the room you will use. Fix issues now rather than on the day.

24 hours before

Do a light, structured review only: the 7 principles, the purpose of each of the 7 themes, the purpose and key inputs/outputs of each of the 7 processes, and the project-management team roles.

24 hours before

Lay out ID, confirmation, directions or login details, and decide what you will wear and eat. Aim to stop studying early and sleep properly.

24 hours before

Confirm whether any permitted items (pen, rough paper, water) are allowed for your delivery mode - do not assume.

Morning of the exam

Eat normally and avoid new stress. Do a 20-minute skim of your one-page summary, then close the notes for good.

Morning of the exam

Leave for the test centre with a buffer, or log in and complete any identity/system checks before your start time so you begin calm rather than catching up.

During the exam - first pass

Work at about one minute per question. Answer everything you are sure of, and flag anything that needs thinking rather than stalling on it.

During the exam - second pass

Return to flagged questions, eliminate clearly wrong options, and use the process of elimination to choose between the remaining two. Watch for questions asking for the BEST or FIRST action.

During the exam - final minutes

Check that no question is left unanswered and that your answers match the numbering. Only change an answer if you have a concrete reason - second-guessing rarely helps.

Rules to check

  • Bring the original, valid photo ID in the name on the booking. The accepted document types are set by the provider, so confirm them in advance rather than assuming any photo ID will do.

  • All electronic devices - phones, smart watches, earbuds, second screens - must be off and away from your desk for the whole sitting. For remote exams, a device in the room can void your result.

  • The Foundation exam is closed book: no manual, notes, printed summaries or unauthorised materials. Using them can lead to the exam being invalidated.

  • Breaks are generally not permitted during the exam; if you have an approved access arrangement covering breaks, confirm how it is administered with the provider before the day.

  • Results are usually shown or issued shortly after the exam, but the formal outcome and any certificate/receipt process vary by delivery mode - confirm how and when your result will be issued with the provider.

  • Passing Foundation (55%, i.e. 33 of 60) is the prerequisite for the Practitioner exam, so keep your Foundation result documentation safe if you plan to progress.

  • If anything goes wrong - technical failure, illness, ID not accepted - stop and notify the invigilator or provider support immediately rather than attempting to continue; the provider controls any rescheduling or special-consideration policy, so confirm the process with them.

PRINCE2 Foundation FAQ

How many PRINCE2 Foundation practice questions are available?

The practice set has 200 PRINCE2 Foundation questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many PRINCE2 Foundation flashcards are available?

The flashcard set has 32 PRINCE2 Foundation cards. Each card shows the term and its definition.

Which topics does the PRINCE2 Foundation study material cover?

The PRINCE2 Foundation study material has 4 sections, including Principles: the non-negotiable foundations of PRINCE2, People: leadership, roles and working together, and Practices: the seven management disciplines.

What format facts does the catalog list for the PRINCE2 Foundation exam?

The catalog lists these item types: multiple choice for the PRINCE2 Foundation exam.