75 of 335 questions · Page 3/5 · People: organizations, teams, and leadership · Answers revealed
What is the key output of the 'Starting Up a Project' process?
The Project Brief is created during Starting Up a Project.
Why this answer
The Project Brief is the key output of the Starting Up a Project process, providing the initial information to decide whether to proceed to initiation.
Which THREE of the following are responsibilities of the Project Manager in PRINCE2?
The PM is responsible for creating the PID.
Why this answer
Option A is correct because the Project Manager is responsible for producing the Project Initiation Documentation (PID) in PRINCE2. The PID is a key deliverable that consolidates the project's scope, business justification, plans, and controls, and the Project Manager compiles it based on input from the Project Board and other stakeholders. This responsibility is explicitly defined in the PRINCE2 Project Manager role description.
Exam trap
The trap here is confusing the Project Manager's responsibility for maintaining the Business Case with the authority to approve it, which is reserved for the Project Board or Senior User.
During the Managing a Stage Boundary process, the Project Manager produces an Exception Plan. What triggers this?
An Exception Plan replaces the current plan when tolerances are breached.
Why this answer
An Exception Plan is produced when a stage is forecast to exceed its tolerances, as an alternative to the current Stage Plan, for approval by the Project Board.
A Project Manager delegates the management of a Work Package to a Team Manager. What is the Team Manager's responsibility?
The Team Manager manages the work and reports to the PM.
Why this answer
The Team Manager is responsible for delivering the Work Package within agreed tolerances and reporting progress via Checkpoint Reports.
Which document is the key output of the Initiating a Project process?
The PID is the comprehensive document created during Initiation.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a foundation for the project.
In PRINCE2, what is the primary difference between Project Assurance and a quality review?
Project Assurance is about governance; quality review is about product verification.
Why this answer
Option B is correct because Project Assurance and quality reviews serve distinct purposes in PRINCE2. Project Assurance is an independent oversight function that ensures the project remains viable, compliant, and on track against the business case and plans. A quality review, on the other hand, is a structured technique used to assess whether a specific product meets its defined quality criteria and is fit for purpose.
Exam trap
The trap here is that candidates often confuse the independent oversight role of Project Assurance with the product-focused checking of a quality review, leading them to think they are the same or that the Project Manager performs assurance.
How to eliminate wrong answers
Option A is wrong because Project Assurance and a quality review are not synonymous; they have different objectives, participants, and timing within the project lifecycle. Option C is wrong because Project Assurance is performed by an independent person or group (often from the corporate, programme management, or customer side), not by the Project Manager; the Project Manager is responsible for day-to-day management, not assurance. Option D is wrong because Project Assurance is a role (or set of responsibilities), not a process; a quality review is a technique (or activity), not a role.
A project is in the Initiating a Project process. Which document is the key output of this process?
The PID is the key output of Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. Option B is correct.
Which role is responsible for maintaining the Business Case throughout the project?
The Executive is accountable for the Business Case and its maintenance.
Why this answer
The Executive (Senior Responsible Owner) is the role accountable for the Business Case and its ongoing justification throughout the project. PRINCE2 requires the Business Case to be maintained and reviewed at every stage boundary to ensure continued viability, and this responsibility rests with the Executive, not the Project Manager or Team Manager.
Exam trap
PeopleCert often tests the misconception that the Project Manager is responsible for the Business Case because they create it, but the exam emphasizes that accountability (maintenance and approval) belongs to the Executive.
How to eliminate wrong answers
Option A is wrong because the Team Manager is responsible for delivering the work packages within a stage, not for maintaining the Business Case. Option C is wrong because the Project Manager manages the day-to-day project activities and produces the Business Case, but the accountability for its maintenance and approval lies with the Executive. Option D is wrong because the Senior User represents the users' interests and specifies the requirements, but does not own or maintain the Business Case.
During the Controlling a Stage process, the Project Manager identifies that the project is forecast to exceed the agreed cost tolerance for the current stage. What should the Project Manager do?
This is the correct escalation procedure per management by exception.
Why this answer
Option D is correct because PRINCE2's Controlling a Stage process requires the Project Manager to escalate any forecast deviation beyond the agreed stage tolerance to the Project Board via an Exception Report. The Project Manager cannot proceed without the Board's direction, as the tolerance is a delegated authority limit set by the Board.
Exam trap
PeopleCert often tests the misconception that the Project Manager can handle tolerance breaches by continuing and reporting later, but PRINCE2 mandates immediate escalation when tolerance is forecast to be exceeded.
How to eliminate wrong answers
Option A is wrong because the Project Manager does not have the authority to increase the project budget unilaterally; budget changes require Project Board approval. Option B is wrong because a cost overrun within a stage does not automatically invalidate the Business Case; the Board must assess viability after receiving the Exception Report. Option C is wrong because the Project Manager must report the issue immediately via an Exception Report, not wait for the next Highlight Report, as the deviation exceeds the agreed tolerance.
Which TWO of the following are true about Project Assurance?
Yes, that is the primary role.
Why this answer
Project Assurance provides an independent view of the project's progress, ensuring that the project remains viable and adheres to the business case. It reports directly to the Project Board, not the Project Manager, to maintain objectivity. This independence is critical for the Board to make informed decisions about project continuation.
Exam trap
The trap here is confusing Project Assurance with Project Support or the Project Manager's duties, leading candidates to think the Project Manager can step in for assurance or that administrative tasks belong to assurance.
What is the difference between a Request for Change and an Off-specification?
An RFC is a request to change an approved product; an Off-specification is a non-conformance already present.
Why this answer
A Request for Change is a proposal for a change to a product that has been approved, while an Off-specification is an actual deviation from the specification (something that was supposed to be done but wasn't done correctly).
A project manager notices that team members from different departments are unclear about their roles and responsibilities. According to PRINCE2, which management product should be used to clarify this?
The PID defines roles and responsibilities.
Why this answer
In PRINCE2, the Project Initiation Documentation (PID) provides a comprehensive baseline for the project, including defined roles and responsibilities. When team members are unclear about their roles, the PID is the management product that formally documents these assignments, ensuring everyone understands their accountabilities. This aligns with the PRINCE2 principle of 'defined roles and responsibilities' and the 'People' domain focus on organizational clarity.
Exam trap
PeopleCert often tests the distinction between the PID as the comprehensive 'rulebook' for the project and other registers or documents that serve narrower, specific purposes, leading candidates to mistakenly choose a register that tracks outputs rather than defines responsibilities.
How to eliminate wrong answers
Option B is wrong because the Business Case documents the justification for the project, including costs, benefits, and risks, but it does not define individual roles or responsibilities. Option C is wrong because the Risk Register captures identified risks, their analysis, and responses, not role assignments. Option D is wrong because the Quality Register records planned and executed quality activities and their results, not who is responsible for specific tasks or deliverables.
A project is in the Initiating a Project process. Which key document is produced as an output of this process?
The PID is the main output of Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the key document produced as an output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single source of information that defines the project's scope, objectives, and controls, and is used to obtain authorization to proceed.
Exam trap
PeopleCert often tests the distinction between documents produced in different processes; the trap here is confusing the Project Brief (output of Starting Up a Project) with the PID (output of Initiating a Project), leading candidates to select the Brief as the key output of the initiation process.
How to eliminate wrong answers
Option B (Project Brief) is wrong because the Project Brief is created during the Starting Up a Project process, not Initiating a Project; it serves as input to the Initiating a Project process. Option C (Stage Plan) is wrong because Stage Plans are produced during the Managing a Stage Boundary process, not Initiating a Project; the PID includes the Project Plan, not a Stage Plan. Option D (Benefits Review Plan) is wrong because the Benefits Review Plan is created during the Initiating a Project process but is a separate document, not the key document; the PID is the primary output that contains the project strategy and controls.
What is the key difference between Project Assurance and a quality review?
This captures the continuous vs event-based distinction.
Why this answer
Project Assurance is a continuous, independent oversight function that ensures the project remains viable and compliant with standards throughout its lifecycle, while a quality review is a specific, time-boxed event focused on examining a product's fitness for purpose. In PRINCE2, Project Assurance is a role (often assigned to the Project Board or a separate person) that provides objective checks, whereas a quality review is a technique within the quality management approach used to verify that a product meets its quality criteria. This distinction is fundamental because it separates ongoing governance from discrete product verification activities.
Exam trap
The trap here is that candidates confuse the continuous, role-based nature of Project Assurance with the event-based, technique-driven nature of a quality review, often assuming both are 'checks' that serve the same purpose or that a quality review is a process rather than a technique.
How to eliminate wrong answers
Option B is wrong because Project Assurance covers all aspects of the project (including Business Case, risks, quality, and progress), not just the Business Case, and a quality review examines any product (not just the Project Plan) against its quality criteria. Option C is wrong because while Project Assurance is indeed a role, a quality review is a technique (not a process) that can be used in multiple PRINCE2 processes, including Managing Product Delivery and Managing a Stage Boundary, not exclusively the latter. Option D is wrong because Project Assurance is performed by an independent role (often a Project Board member or a dedicated assurance person), not by the Project Manager, and a quality review is performed by a review team (including the producer, reviewers, and a chair), not by the Project Board.
Which TWO of the following are differences between Project Assurance and a quality review?
Assurance is continuous; a quality review is a scheduled check.
Why this answer
Project Assurance is a continuous role monitoring compliance and governance, while a quality review is a specific event to examine a product. Assurance is independent; quality reviews involve peers.
In the RACI model used in PRINCE2, what is the difference between accountability (A) and responsibility (R)?
This correctly distinguishes the two concepts.
Why this answer
Accountability means ultimate ownership and final decision-making authority, while responsibility means performing the work. Option A is correct.
In PRINCE2, which role provides independent assurance to the Project Board that the project is being conducted correctly?
Project Assurance is an independent role that assures the Project Board.
Why this answer
Project Assurance is independent from the Project Manager and reports to the Project Board.
Which of the following is NOT a responsibility of the Project Manager?
Project Assurance is independent and cannot be performed by the PM.
Why this answer
Project Assurance is independent and cannot be delegated to the Project Manager.
What is the key difference between Project Assurance and a quality review?
Assurance provides continuous oversight; quality reviews are discrete checks on specific products.
Why this answer
Project Assurance is an independent, ongoing role to ensure the project remains aligned with the Business Case and standards. A quality review is a specific technique to assess the quality of a product. Assurance is a role; quality review is a process.
Which THREE of the following are responsibilities of the Project Manager?
The PM manages the project on a day-to-day basis.
Why this answer
Option A is correct because the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes monitoring progress, managing the team, and ensuring that work packages are delivered on time and within budget. The Project Manager must operate within these tolerances and only escalate to the Project Board when forecasts deviate beyond them.
Exam trap
The trap here is confusing the Project Manager's operational responsibilities with the strategic or assurance roles of the Project Board and Project Assurance, leading candidates to incorrectly select 'Maintaining the Business Case' or 'Providing independent assurance'.
A project is in the Initiating a Project process. Which role is responsible for preparing the Project Initiation Documentation (PID)?
The PM prepares the PID.
Why this answer
In PRINCE2, the Project Manager is responsible for preparing the Project Initiation Documentation (PID) during the Initiating a Project process. The PID is a key management product that defines the project's scope, objectives, and controls, and the Project Manager must compile it based on input from the project board and other stakeholders.
Exam trap
The trap here is that candidates often confuse the Project Manager's role in preparing the PID with the Project Board's role in approving it, or mistakenly assign the task to the Senior Responsible Owner due to the SRO's authority over the business case.
How to eliminate wrong answers
Option A is wrong because the Team Manager is responsible for delivering the work packages within a stage, not for creating the PID. Option B is wrong because the Senior Responsible Owner (SRO) is the executive role that owns the business case and provides overall direction, but does not prepare the PID. Option D is wrong because Project Assurance provides independent oversight and checks the PID for compliance, but does not prepare it.
Which statement correctly describes the relationship between Project Assurance and quality review?
Correct distinction.
Why this answer
Project Assurance is a role within the PRINCE2 framework, responsible for ensuring that the project remains viable and compliant with its business case, while quality review is a technique used to assess the quality of products. The correct relationship is that Project Assurance is a role, and quality review is a technique, making option C correct. They are distinct concepts: one is a governance role, the other is a specific method for evaluating deliverables.
Exam trap
The trap here is that candidates often confuse the governance role of Project Assurance with the execution of quality activities, leading them to incorrectly select option D, when in fact Project Assurance oversees quality but does not perform the quality review technique itself.
How to eliminate wrong answers
Option A is wrong because Project Assurance and quality review are not the same thing; Project Assurance is a role focused on objective oversight, while quality review is a technique for product evaluation. Option B is wrong because quality review is not a part of Project Assurance; rather, Project Assurance may use quality reviews as one of many techniques to fulfill its responsibilities, but quality review is a separate technique defined in the PRINCE2 quality theme. Option D is wrong because Project Assurance does not perform quality reviews; quality reviews are conducted by a review team including the producer, reviewers, and a chair, while Project Assurance provides independent oversight and may attend but does not execute the review itself.
Why does PRINCE2 separate the Project Manager role from Project Assurance?
Independence is key to avoid bias.
Why this answer
Separation ensures independent oversight. Project Assurance provides an objective check on the project's health, free from the PM's day-to-day pressures.
What is the purpose of the Managing a Stage Boundary process?
Correct. The process enables stage boundary review and approval.
Why this answer
The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next Stage Plan, and decide whether to continue the project. It ensures that the project remains viable by assessing progress against the Business Case and updating plans accordingly.
Exam trap
PeopleCert often tests the distinction between processes that produce plans (Initiating a Project) versus processes that review and approve stage-level plans (Managing a Stage Boundary), leading candidates to confuse the production of the Project Initiation Documentation with stage boundary activities.
How to eliminate wrong answers
Option B is wrong because authorizing the start of the project is the purpose of the Starting Up a Project process, not Managing a Stage Boundary. Option C is wrong because controlling day-to-day work is the responsibility of the Managing Product Delivery process, which handles work package assignments and progress reporting. Option D is wrong because producing the Project Initiation Documentation is the output of the Initiating a Project process, which occurs before any stage boundaries are managed.
Who is responsible for producing the Checkpoint Report?
Correct: The Team Manager produces the Checkpoint Report.
Why this answer
The Team Manager produces the Checkpoint Report for the Project Manager to report progress of a Work Package.
In PRINCE2, why is the Project Assurance role separated from the Project Manager?
Independence ensures that Project Assurance can objectively monitor the project.
Why this answer
Project Assurance provides independent oversight to ensure that the project is managed correctly. If the Project Manager also performed assurance, it would compromise objectivity and independence.
A stakeholder is concerned that the project is not delivering value for money. Which role should this concern be raised with?
Correct.
Why this answer
The Executive is ultimately accountable for the project's business justification, including ensuring value for money. Concerns about cost versus benefits must be escalated to the Executive, who owns the Business Case and has the authority to approve changes or stop the project if value is not being delivered.
Exam trap
The trap here is confusing the Project Manager's responsibility for day-to-day cost control with the Executive's accountability for overall value for money and the Business Case.
How to eliminate wrong answers
Option A is wrong because the Senior User represents the users' needs and specifies the expected benefits, but is not accountable for overall value for money or the business case. Option B is wrong because Project Assurance provides independent oversight and checks compliance, but does not have the authority to make decisions on value for money; it reports issues to the Executive. Option D is wrong because the Project Manager manages day-to-day activities and escalates issues, but is not accountable for the business justification or value for money decisions.
Which document is the key output of the Initiating a Project process?
The PID is the formal document that defines the project and is created during Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides a baseline for the project and is used by the Project Board to decide whether to proceed.
What is the difference between a Request for Change and an Off-specification?
This correctly describes the difference.
Why this answer
Option D is correct because in PRINCE2, a Request for Change (RFC) is a formal proposal to modify a baselined product, while an Off-specification (Off-spec) is a notification that a product does not meet its agreed specification. The key distinction is that an RFC addresses a change to a product that has already been approved, whereas an Off-spec identifies a failure to meet the original requirements. This aligns with PRINCE2's change control approach, where both are captured in the Issue Register but serve different purposes.
Exam trap
The trap here is that candidates confuse the terms by associating RFCs with scope changes and Off-specs with quality defects, when in fact both can relate to any aspect of a product's specification, and the true difference lies in whether the product is baselined (RFC) or non-conforming (Off-spec).
How to eliminate wrong answers
Option A is wrong because it incorrectly associates RFCs solely with scope changes and Off-specs solely with quality changes; in PRINCE2, RFCs can affect any baselined aspect (scope, quality, time, cost) and Off-specs are about non-conformance to any specification, not just quality. Option B is wrong because RFCs and Off-specs are distinct concepts with different triggers and actions; they are not synonyms. Option C is wrong because both RFCs and Off-specs can be raised by any project stakeholder, not exclusively by the Project Manager or Team Manager; the PRINCE2 guidance states that anyone can raise an issue, which is then logged and assessed.
Which document is produced by the Team Manager to report progress on a Work Package?
Correct. The Team Manager produces Checkpoint Reports for the Project Manager.
Why this answer
The Checkpoint Report is produced by the Team Manager and sent to the Project Manager to report progress on a Work Package.
A project is forecast to exceed its stage cost tolerance. What should the Project Manager do?
Correct action: escalate immediately via Exception Report.
Why this answer
In PRINCE2, when a project manager forecasts that a stage will exceed its cost tolerance, they must escalate the issue to the Project Board by raising an Exception Report. This is because tolerances are delegated limits, and exceeding them requires board-level decision-making, not just reporting or self-authorization. The Exception Report triggers an Exception Plan to recover or adjust the project.
Exam trap
PeopleCert often tests the distinction between reporting (Highlight Report) and escalation (Exception Report), trapping candidates who think a simple status update suffices when tolerances are breached.
How to eliminate wrong answers
Option A is wrong because a Highlight Report is a periodic status update, not an escalation mechanism for tolerance breaches; the Project Manager must raise an Exception Report immediately, not wait for the next Highlight Report. Option C is wrong because exceeding stage cost tolerance does not automatically invalidate the Business Case; the Project Board must assess viability and decide on corrective action, not unilaterally close the project. Option D is wrong because the Project Manager cannot increase the stage budget without authorization; tolerances are set by the Project Board, and only they can approve budget changes through an Exception Plan.
In PRINCE2, who is responsible for maintaining the Business Case throughout the project?
The SRO is accountable for the Business Case throughout the project.
Why this answer
In PRINCE2, the Executive (also known as the Senior Responsible Owner) is accountable for the Business Case and must ensure it remains viable throughout the project. The Business Case is the key document that justifies the project's initiation and continued existence, and only the Executive has the authority to approve changes to it or decide to close the project if the Business Case is no longer viable.
Exam trap
The trap here is confusing the Project Manager's responsibility for 'managing' the Business Case (updating it, tracking benefits) with the Executive's accountability for 'maintaining' it (owning it, approving changes, deciding to continue or stop).
How to eliminate wrong answers
Option B is wrong because the Project Manager is responsible for creating, updating, and managing the Business Case on a day-to-day basis, but they do not own it; they cannot approve changes or decide to stop the project based on it. Option C is wrong because the Senior Supplier is responsible for providing the project's products and ensuring supplier interests are met, but they do not own the Business Case. Option D is wrong because Project Assurance is an independent monitoring function that checks the Business Case is being managed correctly, but they are not responsible for maintaining it.
Which role is responsible for maintaining the Business Case throughout the project?
The SRO/Executive is accountable for the Business Case.
Why this answer
The Senior Responsible Owner (SRO/Executive) owns the Business Case and is accountable for ensuring it remains viable. The Project Manager maintains the Business Case on behalf of the Executive.
Which PRINCE2 principle ensures that the Project Board delegates decision-making to the Project Manager within defined tolerances?
This principle defines tolerance-based delegation.
Why this answer
Management by Exception means the PM is empowered within tolerances, and only escalates when tolerances are forecast to be exceeded.
Why does PRINCE2 recommend separating the role of Project Manager from Project Assurance?
Independence is key to effective assurance.
Why this answer
Separating Project Manager from Project Assurance ensures objectivity and independence of assurance activities. The Project Manager is responsible for day-to-day management and cannot objectively assess their own work.
Which TWO roles are part of the Project Board?
The Senior User is a board role.
Why this answer
The Project Board consists of the Executive (SRO), Senior User(s), and Senior Supplier(s).
In a project, a Team Manager reports progress to the Project Manager using which report?
The Team Manager produces Checkpoint Reports for the PM.
Why this answer
The Team Manager produces a Checkpoint Report to inform the Project Manager of progress against the Work Package plan.
Which TWO of the following are characteristics of the Project Assurance role?
Assurance reports to the Board, not the PM.
Why this answer
Option C is correct because the Project Assurance role is specifically tasked with monitoring and reporting on the project's adherence to PRINCE2 standards, and it reports directly to the Project Board to provide independent oversight. This ensures that the Project Board receives objective assessments of the project's progress and compliance, separate from the Project Manager's perspective.
Exam trap
PeopleCert often tests the misconception that Project Assurance is a subset of Project Support or can be performed by the Project Manager, but PRINCE2 strictly requires independence to maintain objective oversight.
How often should the Project Board meet during a PRINCE2 project?
The Project Board meets at stage boundaries and when an exception is raised.
Why this answer
Project Board meetings are held at key decision points (end of stages) and when exceptions occur. They are not scheduled at regular intervals but are exception-driven.
Which role is responsible for ensuring that the project's products meet specified quality criteria?
The Senior User represents the users who will use the product and defines quality needs.
Why this answer
The Senior User is responsible for specifying the requirements and ensuring the final product meets the agreed quality criteria.
Which THREE of the following are roles on the PRINCE2 Project Board?
Yes, this is the chair of the Project Board.
Why this answer
The Project Board consists of the Senior Responsible Owner (Executive), Senior User, and Senior Supplier.
What is the purpose of the Managing a Stage Boundary process?
This is the correct purpose.
Why this answer
Managing a Stage Boundary allows the Project Board to review the current stage's performance, approve the next Stage Plan, and update the Business Case.
A project is in its Initiating a Project process. The Project Manager has prepared the Project Initiation Documentation (PID). Which role is responsible for approving the PID?
The Project Board collectively approves the PID to authorize the project.
Why this answer
The PID is approved by the Project Board, which includes all three roles (Executive, Senior User, Senior Supplier). The Project Manager prepares it but does not approve it.
In PRINCE2, what is the key difference between the Project Assurance role and a quality review?
Project Assurance is a role that ensures the project remains viable; quality review is a technique to verify product quality.
Why this answer
Project Assurance provides ongoing independent oversight of the project, while a quality review is a specific inspection technique used to assess the quality of a product.
What is the purpose of the Managing a Stage Boundary process?
Correct: The process provides a review and decision point for the Project Board.
Why this answer
The Managing a Stage Boundary process is designed to provide the Project Board with the information needed to review the current stage's performance, assess the updated Business Case, and approve the next Stage Plan. This process ensures that the project remains viable and aligned with business objectives before committing resources to the next stage. Option C correctly captures this review and approval purpose.
Exam trap
The trap here is confusing the purpose of Managing a Stage Boundary with Controlling a Stage (option B), as both involve stage-level activities, but only Managing a Stage Boundary focuses on the boundary review and approval of the next stage, not the day-to-day management of work.
How to eliminate wrong answers
Option A is wrong because the Project Plan is created during the Initiating a Project process, not during Managing a Stage Boundary. Option B is wrong because managing the work of the current stage is the purpose of the Controlling a Stage process, not Managing a Stage Boundary. Option D is wrong because closing the project is the purpose of the Closing a Project process, which occurs after all stages are complete.
Which TWO of the following are responsibilities of the Project Manager?
Correct.
Why this answer
Option C is correct because the Project Manager is responsible for preparing Highlight Reports to keep the Project Board informed of progress, achievements, and exceptions at regular intervals. Option E is correct because the Project Manager is accountable for the day-to-day management of the project, ensuring tasks are completed, risks are managed, and the project remains on track within the tolerances set by the Project Board.
Exam trap
The trap here is that candidates often confuse the Project Manager's operational responsibilities (like preparing reports and daily management) with the Project Board's governance duties (like chairing meetings and approving plans), leading them to select options that sound plausible but are actually Board-level tasks.
A Team Manager receives a Work Package from the Project Manager. During delivery, the Team Manager identifies a potential issue that may cause a delay. What should the Team Manager do first?
The Team Manager reports progress and issues to the PM via Checkpoint Reports.
Why this answer
The Team Manager should report the issue to the Project Manager via a Checkpoint Report or exception process, as they are accountable for delivery within tolerances.
Which THREE of the following are responsibilities of the Project Board?
The Board directs the project.
Why this answer
The Board approves stage plans (A), authorizes tolerances (C), and makes key decisions (E). B and D are PM responsibilities.
During the Managing a Stage Boundary process, the Project Manager updates the business case. Who is accountable for approving the updated business case?
The SRO owns the business case and approves updates.
Why this answer
The Senior Responsible Owner (Executive) is accountable for the business case and approves updates at stage boundaries.
Which role is responsible for managing the delivery of a Work Package?
The Team Manager manages the delivery of Work Packages.
Why this answer
The Team Manager is responsible for managing the delivery of a Work Package within a PRINCE2 project. This role coordinates the team members, ensures the work is completed according to the agreed specifications, and reports progress back to the Project Manager. The Team Manager acts as the direct interface between the project management team and the team members executing the work.
Exam trap
PeopleCert often tests the distinction between the Project Manager's overall responsibility and the Team Manager's delegated authority for Work Package delivery, leading candidates to incorrectly select the Project Manager as the answer.
How to eliminate wrong answers
Option B (Senior User) is wrong because the Senior User represents the interests of those who will use the project's products and is responsible for specifying the requirements and benefits, not for managing the delivery of a Work Package. Option C (Project Assurance) is wrong because Project Assurance is an independent monitoring function that checks compliance with PRINCE2 standards and project controls, not a role that manages work package delivery. Option D (Project Manager) is wrong because the Project Manager is responsible for the overall planning, monitoring, and control of the project, but delegates the day-to-day management of a Work Package to the Team Manager.
Which THREE of the following are true about Project Assurance in PRINCE2?
Project Assurance is mandatory, though it can be performed by multiple people.
Why this answer
Option A is correct because PRINCE2 mandates the Project Assurance role to ensure that the project remains aligned with its business case, quality standards, and governance requirements. This role is separate from the Project Manager and cannot be combined with it, as it provides an independent check on the project's ongoing viability and compliance.
Exam trap
The trap here is that candidates often confuse Project Assurance with the Project Manager's responsibilities, assuming that the Project Manager can self-assure, or they mistakenly think assurance is only needed at stage boundaries, when in fact PRINCE2 requires continuous independent oversight throughout the project.
Which report is produced by the Team Manager and used by the Project Manager to update the Project Board?
Correct.
Why this answer
The Checkpoint Report is produced by the Team Manager and sent to the Project Manager. The Project Manager then uses it to compile the Highlight Report for the Project Board.
In a PRINCE2 project, the Project Manager has also been assigned the Project Assurance role. Which PRINCE2 principle is being violated?
PRINCE2 requires separation of Project Manager and Project Assurance to ensure independence.
Why this answer
PRINCE2 requires that Project Assurance be independent of the Project Manager to provide objective oversight. Combining the roles violates the 'defined roles and responsibilities' principle and the management of risk.
Match each PRINCE2 role to its responsibility.
Drag a concept onto its matching description — or click a concept then click the description.
Manages the project on a day-to-day basis.
Specifies the user requirements and ensures the project delivers benefits.
Provides the resources and expertise to produce the project's products.
Owns the business case and chairs the project board.
Monitors all aspects of the project's performance independently.
Why these pairings
These are key roles in the PRINCE2 project management team.
A Senior Supplier is concerned that a proposed change will impact the project's technical feasibility. What should the Senior Supplier do?
The Senior Supplier should bring the concern to the Project Board as part of their role in representing supplier interests.
Why this answer
The Senior Supplier is a member of the Project Board and should raise their concern at the Project Board meeting or via an Exception Report if the change requires Board decision. The Senior Supplier ensures that supplier interests are represented.
Which role is responsible for delivering Work Packages and reporting progress to the Project Manager?
The Team Manager is responsible for delivering Work Packages and reporting to the PM.
Why this answer
The Team Manager manages the delivery of Work Packages and reports to the Project Manager. Option C is correct.
In PRINCE2, why is the Project Manager not allowed to also perform Project Assurance?
Correct. Independence is key to effective assurance.
Why this answer
In PRINCE2, Project Assurance is a separate role from the Project Manager to ensure objective oversight of the project's adherence to standards, plans, and business justification. The Project Manager is responsible for day-to-day management and delivery, so allowing them to also perform Project Assurance would create a conflict of interest, as they would be reviewing their own work. This independence is critical for the integrity of the assurance function, which must provide unbiased checks on the Project Manager's decisions and outputs.
Exam trap
The trap here is that candidates may think Project Assurance is optional or not a formal role (Option B), or they may assume the reason is practical (Option D), but PRINCE2 explicitly enforces role separation to prevent conflicts of interest.
How to eliminate wrong answers
Option B is wrong because Project Assurance is explicitly defined as a PRINCE2 role, responsible for monitoring compliance and providing independent oversight. Option C is wrong because PRINCE2 does not reduce roles to simplify; it mandates distinct roles (e.g., Project Manager, Project Assurance, Senior User) to ensure separation of duties and accountability. Option D is wrong because the reason is not about the Project Manager's workload or time constraints; it is a governance principle to maintain objectivity and avoid self-review.
Which role is responsible for project assurance activities in a PRINCE2 project?
Project Assurance is the role responsible for independent assurance.
Why this answer
Project Assurance is the correct answer because in PRINCE2, Project Assurance is a distinct role responsible for monitoring and reporting on the project's adherence to the management and technical standards, independent of the Project Manager. It ensures that the project remains aligned with the business case, quality requirements, and stakeholder expectations, acting as the 'eyes and ears' of the Project Board.
Exam trap
The trap here is that candidates often confuse the Project Manager's responsibility for managing the project with the independent oversight role of Project Assurance, leading them to incorrectly select the Project Manager as the answer.
How to eliminate wrong answers
Option A is wrong because the Project Manager is responsible for day-to-day management and execution, not for independent assurance; they are the subject of assurance checks. Option B is wrong because the Senior Supplier is a member of the Project Board who provides supplier-side input and decision-making, but does not perform the ongoing, independent monitoring of project assurance activities. Option D is wrong because the Team Manager is responsible for delivering the work within a work package, not for project-level assurance, which is a higher-level oversight function.
In a PRINCE2 project, the project board is concerned that the project manager is not effectively communicating with key stakeholders. The project manager recently presented a detailed risk report to the board, but several board members were unaware of the critical risks identified. Which communication management activity should the project manager have performed to ensure the board was properly informed?
The strategy defines how and when to communicate risks to each stakeholder.
Why this answer
The correct answer is D because the PRINCE2 communication management strategy defines how, when, and to whom information should be communicated. The project manager should have agreed on this strategy with the board upfront, ensuring that critical risks are reported in a format and frequency that meets the board's needs. Without this agreement, the board was not properly informed despite the detailed risk report being presented.
Exam trap
The trap here is that candidates often confuse operational reporting tasks (like updating the risk register or preparing a highlight report) with the strategic management activity of agreeing on the communication management strategy, which is the foundational step to ensure stakeholders receive the right information in the right way.
How to eliminate wrong answers
Option A is wrong because including critical risks in the project plan is not a communication management activity; the project plan focuses on schedule, cost, and scope, not on defining stakeholder communication needs. Option B is wrong because a highlight report is a summary for the board, but the core issue is the lack of agreement on communication methods, not the type of report used. Option C is wrong because updating the risk register and sending it to the board is an operational task, not a strategic communication management activity; it does not address the need for the board to agree on how and when risks should be communicated.
Which THREE of the following are responsibilities of the Senior Supplier role on the Project Board?
Quality of supplier deliverables is a key responsibility.
Why this answer
The Senior Supplier role on the Project Board is responsible for ensuring that the supplier's products meet the agreed quality requirements. This includes providing the necessary resources and expertise to deliver the project's products, and contributing to the Business Case from a supplier perspective, particularly regarding the feasibility and cost of the supplier's work.
Exam trap
The trap here is that candidates often confuse the day-to-day management responsibilities of the Project Manager with the strategic oversight responsibilities of the Senior Supplier on the Project Board, leading them to incorrectly select Option A.
Which role can delegate change control decisions to a Change Authority?
Correct: The Project Board can set up a Change Authority to approve changes within defined tolerances.
Why this answer
In PRINCE2, the Project Board is responsible for overall project governance and can delegate its change control authority to a Change Authority. This delegation is formalized in the Project Initiation Documentation (PID) and allows the Change Authority to approve or reject change requests within predefined limits, such as cost or time thresholds, without needing to escalate every decision back to the Board.
Exam trap
The trap here is that candidates often confuse the Project Board with its individual members (Executive or Senior User) and mistakenly think one person can delegate change authority, but PRINCE2 requires collective Board approval for such delegation.
How to eliminate wrong answers
Option A is wrong because the Project Manager manages day-to-day activities and can recommend changes but does not have the authority to delegate change control decisions; that authority rests with the Project Board. Option C is wrong because the Executive is a single role on the Project Board, not the collective decision-making body; delegation of change control is a Board-level decision, not an individual one. Option D is wrong because the Senior User represents user interests on the Project Board but, like the Executive, cannot unilaterally delegate change authority; only the full Project Board can do so.
Which role manages the day-to-day execution of a Work Package?
The Team Manager manages the day-to-day execution of a Work Package.
Why this answer
The Team Manager is the role responsible for the day-to-day management of a Work Package within a PRINCE2 project. They report to the Project Manager and ensure that the work is completed according to the agreed tolerances, quality criteria, and schedule. This is defined in the PRINCE2 manual under the 'Organizing' theme, where the Team Manager is specifically tasked with coordinating the team's work and reporting progress.
Exam trap
The trap here is that candidates often confuse the Project Manager's overall responsibility with the Team Manager's specific duty to manage the day-to-day execution of a Work Package, leading them to incorrectly select the Project Manager.
How to eliminate wrong answers
Option A is wrong because Project Support provides administrative and advisory services to the project, such as maintaining files and providing tools, but does not manage the execution of a Work Package. Option C is wrong because the Senior User represents the interests of those who will use the project's products and specifies requirements, but does not manage day-to-day Work Package execution. Option D is wrong because the Project Manager delegates the management of Work Packages to the Team Manager and focuses on overall project planning and control, not the daily execution of individual Work Packages.
A Team Manager receives a Work Package from the Project Manager. To whom should the Team Manager report progress?
The Team Manager reports to the Project Manager.
Why this answer
In PRINCE2, the Team Manager is responsible for delivering the Work Package and reports progress directly to the Project Manager, who is the single point of accountability for the project. The Project Manager uses this information to update the Project Plan and report to the Project Board. This ensures a clear line of control and avoids bypassing the management layer.
Exam trap
The trap here is that candidates confuse the reporting line with oversight roles, assuming that Project Assurance or the Board needs direct progress updates, when PRINCE2 explicitly mandates that the Team Manager reports only to the Project Manager to preserve the single point of control.
How to eliminate wrong answers
Option A is wrong because the Project Board is the ultimate decision-making body and does not receive direct progress reports from the Team Manager; the Project Manager reports to the Board. Option B is wrong because the Senior User represents user interests and is not involved in day-to-day progress reporting from the Team Manager. Option C is wrong because Project Assurance is an independent oversight function that reviews compliance and quality, not a recipient of routine progress reports from the Team Manager.
Which TWO of the following statements about the Change Authority role are correct?
Correct.
Why this answer
Option B is correct because the Change Authority role is optional in PRINCE2. It is only established if the Project Board decides to delegate authority for making change decisions within defined limits, rather than handling all change requests themselves.
Exam trap
The trap here is that candidates often assume the Change Authority is mandatory or always the Project Manager, confusing it with the Change Control approach or the Project Manager's responsibilities, when PRINCE2 explicitly makes it an optional delegation by the Project Board.
In PRINCE2, what is the difference between a Request for Change (RFC) and an Off-Specification (Off-spec)?
This is the core distinction: proactive vs. non-conformance.
Why this answer
Option C is correct because in PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product, its specification, or the project's baseline, while an Off-Specification (Off-spec) is a product that has been completed but does not meet its agreed specification. The key distinction is that an RFC seeks to change what is required, whereas an Off-spec identifies a deviation from what was required.
Exam trap
The trap here is that candidates confuse the raising authority or approval outcome with the core definition, leading them to choose options that describe procedural roles rather than the fundamental difference in what each term represents.
How to eliminate wrong answers
Option A is wrong because both RFCs and Off-specs can be raised by any project stakeholder, not exclusively by the Project Board or Project Manager; the Project Board may approve them, but raising is not restricted. Option B is wrong because RFC and Off-spec are distinct concepts with different definitions and purposes in PRINCE2; they are not interchangeable. Option D is wrong because an Off-spec is not always rejected; it may be accepted as a concession if the deviation is deemed acceptable, and an RFC is not always approved by the Change Authority—it can be rejected or deferred.
Who is responsible for managing the delivery of a Work Package?
The Team Manager manages Work Package delivery.
Why this answer
The Team Manager is responsible for the delivery of one or more Work Packages and reports progress to the Project Manager.
Which of the following is NOT a role in the PRINCE2 project management team?
PRINCE2 uses the term SRO, not Sponsor.
Why this answer
The PRINCE2 project management team structure includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optionally the Change Authority. The Project Sponsor is not a defined role in PRINCE2; instead, the Executive role fulfills the sponsorship responsibilities. Therefore, option A is correct as the role that does NOT exist in the PRINCE2 framework.
Exam trap
The trap here is that candidates often confuse the generic term 'Project Sponsor' with the PRINCE2-specific 'Executive' role, leading them to incorrectly select a wrong option like Change Authority or Team Manager.
How to eliminate wrong answers
Option A is correct because 'Project Sponsor' is not a PRINCE2 role; the Executive is the equivalent. Option B is wrong because Change Authority is a valid PRINCE2 role, responsible for authorizing change requests within delegated limits. Option C is wrong because Team Manager is a valid PRINCE2 role, responsible for delivering the work packages assigned by the Project Manager.
Option D is wrong because Project Manager is a core PRINCE2 role, managing the day-to-day project activities and reporting to the Project Board.
What is the difference between Project Assurance and a quality review?
Project Assurance is a role; quality review is a technique for reviewing products.
Why this answer
Project Assurance is ongoing and independent; a quality review is a specific technique to review products.
A project is forecast to exceed its cost tolerance. What should the Project Manager do?
Correct action per management by exception.
Why this answer
When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is management by exception.
Which role is responsible for providing independent assurance to the Project Board that the project is on track?
Project Assurance is an independent role that reports to the Project Board.
Why this answer
Project Assurance is independent of the Project Manager and provides assurance to the Project Board that the project is being managed correctly and remains viable.
Which role is accountable for the project's Business Case throughout the project?
The Executive is accountable for the Business Case.
Why this answer
The Executive (Senior Responsible Owner) is accountable for the Business Case and its maintenance throughout the project.
Which TWO of the following statements about the Change Authority role are correct?
By handling changes within limits, the Board is less burdened.
Why this answer
The Change Authority is an optional role that can be set up to make decisions on change requests within agreed limits, thereby relieving the Project Board from reviewing every change.
Which document is the key output of the Initiating a Project process?
Correct. The PID is the formal documentation of the project.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process because it consolidates all essential information needed to justify and manage the project, including the Business Case, Project Plan, and controls. It serves as the foundation for decision-making by the Project Board and is formally approved at the end of the initiation stage.
Exam trap
The trap here is that candidates often confuse the Business Case as the key output because it is the most prominent justification document, but PRINCE2 explicitly defines the PID as the consolidated output that includes the Business Case and all other baseline management products.
How to eliminate wrong answers
Option A is wrong because the Business Case is a component of the PID, not the key output itself; it is developed and refined during the Initiating a Project process but is not the single document that captures the entire project baseline. Option C is wrong because the Project Plan is one of the management products within the PID, but the PID is the overarching document that includes the Project Plan along with other critical elements like risk management and quality controls. Option D is wrong because a Stage Plan is produced during the Managing a Stage Boundary process, not during Initiating a Project; it details work for a specific stage, whereas the PID covers the whole project.
Which of the following best describes the relationship between the Senior Responsible Owner (SRO) and the Project Sponsor in PRINCE2?
Correct. The Executive is the SRO and acts as the project sponsor.
Why this answer
In PRINCE2, the Senior Responsible Owner (SRO) is the same role as the Project Sponsor, but PRINCE2 uses the term 'Executive' for this role. The Executive is the single point of accountability for the project's success, representing the business interests and owning the business case. Option B correctly identifies this equivalence, which is a fundamental concept in PRINCE2's organizational structure.
Exam trap
The trap here is that candidates often confuse the PRINCE2 Executive with the Project Sponsor from other frameworks (like PMP or Agile), assuming they are different roles or that the Project Sponsor reports to the SRO, when in fact PRINCE2 explicitly uses 'Executive' as the single accountable role equivalent to the SRO.
How to eliminate wrong answers
Option A is wrong because the Project Sponsor (Executive) is not the Project Manager; the Project Manager is a separate role responsible for day-to-day management, while the Executive provides strategic direction and accountability. Option C is wrong because the Project Sponsor (Executive) is not a separate role reporting to the SRO; in PRINCE2, the Executive is the SRO, and there is no hierarchical reporting between them. Option D is wrong because the Project Sponsor (Executive) is not the Senior User; the Senior User represents the users' needs and is a distinct role on the project board, not synonymous with the Executive.
Who chairs the Project Board?
Correct.
Why this answer
The Executive chairs the Project Board in PRINCE2. This is because the Executive is the ultimate decision-maker, accountable for the project's business justification and overall success. The Project Board is chaired by the Executive, not the Project Manager, Senior Supplier, or Senior User, as the Executive represents the business interests and has the authority to approve key decisions.
Exam trap
The trap here is that candidates often assume the Project Manager chairs the Project Board due to their visible leadership role, but PRINCE2 explicitly assigns the chair to the Executive to maintain separation of management and governance.
How to eliminate wrong answers
Option A is wrong because the Project Manager manages the project on a day-to-day basis and reports to the Project Board, but does not chair it; the Project Manager is a member of the project management team, not the board. Option B is wrong because the Senior Supplier represents the supplier's interests and provides resources, but does not chair the board; the chair role is held by the Executive, who balances business, user, and supplier views. Option C is wrong because the Senior User represents the users' needs and benefits, but does not chair the board; the Executive chairs to ensure business justification drives decisions.
Ready to test yourself?
Try a timed practice session using only People: organizations, teams, and leadership questions.