75 of 312 questions · Page 1/5 · People: organizations, teams, and leadership · Answers revealed
In PRINCE2, who is responsible for day-to-day management of the project within tolerances?
The PM has delegated authority for day-to-day management.
Why this answer
The Project Manager manages the project on a day-to-day basis within the tolerances set by the Project Board.
Which TWO of the following are responsibilities of the Project Manager?
The PM manages the stage boundary process, including preparing the next Stage Plan.
Why this answer
The Project Manager is responsible for day-to-day management, including preparing Highlight Reports for the Project Board and managing stage boundaries. Project Assurance is independent, and the Project Board defines tolerances.
In PRINCE2, why is the Project Manager role separated from the Project Assurance role?
Independence is the key reason.
Why this answer
Separation ensures independence and objectivity in assurance, preventing conflicts of interest where the PM would be checking their own work.
Who is responsible for providing independent assurance to the Project Board that the project is on track?
Project Assurance is the correct role.
Why this answer
Project Assurance provides independent oversight, reporting to the Project Board, and cannot be delegated to the Project Manager.
During the Managing a Stage Boundary process, the Project Manager prepares an Exception Plan. What is the trigger for this activity?
The Exception Report triggers the need for an Exception Plan.
Why this answer
In PRINCE2, the trigger for preparing an Exception Plan during the Managing a Stage Boundary process is the raising of an Exception Report. This report is created when the Project Manager forecasts that stage tolerances will be exceeded, indicating that the current Stage Plan cannot be completed within its agreed tolerances. The Exception Plan then replaces the existing Stage Plan to bring the project back within tolerance.
Exam trap
The trap here is that candidates often confuse the trigger for an Exception Plan with the routine end-of-stage planning, forgetting that an Exception Plan is a corrective response to a forecast tolerance breach, not a normal planning activity.
How to eliminate wrong answers
Option A is wrong because the Project Board does not request a new Stage Plan as a trigger; they may approve an Exception Plan, but the trigger is the Exception Report. Option B is wrong because the end of a stage triggers the normal production of a Stage Plan for the next stage, not an Exception Plan. Option C is wrong because a completed Work Package is a routine event that triggers the next activity in the Controlling a Stage process, not the creation of an Exception Plan.
Which document is produced in the Initiating a Project process and defines how the project will be managed?
The PID is the output of Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the key output of Initiating a Project and defines the project's approach, controls, and plans.
In PRINCE2, what is the difference between a Request for Change (RFC) and an Off-specification?
This is the core distinction.
Why this answer
In PRINCE2, a Request for Change (RFC) is a formal proposal to change a product, baseline, or agreed scope, while an Off-specification is a formal notification that a product or deliverable does not meet its specified requirements. The key distinction is that an RFC is a proactive suggestion for change, whereas an Off-specification is a reactive report of a deviation or failure against an agreed specification.
Exam trap
The trap here is that candidates confuse the proactive nature of an RFC with the reactive nature of an Off-specification, often assuming both are just 'problems' or that they are interchangeable terms for any issue.
How to eliminate wrong answers
Option A is wrong because RFC and Off-specification are distinct concepts with different purposes and triggers; they are not synonyms. Option B is wrong because an RFC is not always approved—it goes through change control and can be rejected, and an Off-specification is not always rejected; it can be resolved via a concession or corrective action. Option C is wrong because an RFC can involve cost, time, scope, or quality changes, and an Off-specification can relate to any requirement failure, not just time.
Who is responsible for maintaining the Business Case throughout the project?
The SRO is accountable for the Business Case and its maintenance throughout the project.
Why this answer
The Senior Responsible Owner (SRO) is accountable for the Business Case and ensures it remains viable throughout the project.
Which TWO of the following are responsibilities of the Project Board?
The Project Board approves exceptions beyond their delegated tolerances.
Why this answer
The Project Board is responsible for overall project governance, including authorizing expenditure beyond the delegated authority of the Project Manager. This ensures that financial control remains at the senior management level, preventing unauthorized spending that could jeopardize the project's budget.
Exam trap
PeopleCert often tests the distinction between strategic and operational responsibilities, where candidates mistakenly assign day-to-day management or plan production to the Project Board instead of the Project Manager.
Which THREE of the following are characteristics of Project Assurance?
Assurance must be independent to provide objective oversight.
Why this answer
Project Assurance is a PRINCE2 role that provides an independent, objective view of the project's progress, ensuring that it remains viable and compliant with the business case, quality standards, and risks. Option A is correct because the Project Assurance role must be independent of the Project Manager to avoid conflicts of interest and provide unbiased oversight to the Project Board.
Exam trap
PeopleCert often tests the distinction between Project Assurance (independent oversight) and Project Support (administrative tasks), leading candidates to confuse the two roles.
Refer to the exhibit. According to PRINCE2, to whom should the Team Manager report the potential delay?
Correct: 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 to the Project Manager on progress, issues, and risks. The Project Manager (Sarah Lee) is the single point of contact for the Team Manager within the project management team. Therefore, any potential delay must be reported to the Project Manager, who will then escalate to the Project Board if necessary.
Exam trap
The trap here is that candidates confuse the reporting lines within the project management team, mistakenly thinking a Team Manager should report directly to a Project Board member (Executive, Senior User, or Project Assurance) rather than to the Project Manager who coordinates all delivery-level communications.
How to eliminate wrong answers
Option A is wrong because the Executive (John Smith) is the project's business representative and chair of the Project Board, not the direct line of communication for a Team Manager; the Team Manager reports to the Project Manager, not to the Executive. Option C is wrong because Project Assurance (Peter Black) is an independent oversight role that monitors compliance and performance, not a recipient of operational progress reports from the Team Manager. Option D is wrong because the Senior User (Mary Johnson) represents user requirements and benefits, but the Team Manager's reporting line is to the Project Manager, not to any individual Project Board member.
In PRINCE2, who is responsible for the day-to-day management of the project within the tolerances set by the Project Board?
The Project Manager is responsible for day-to-day management.
Why this answer
The Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, delegating, monitoring, and controlling all aspects of the project, while reporting any deviations that exceed the agreed tolerances to the Project Board.
Exam trap
The trap here is confusing the Project Manager's operational role with the strategic or representational roles of the Executive, Senior User, or Senior Supplier, leading candidates to incorrectly select a board member for day-to-day management.
How to eliminate wrong answers
Option A is wrong because the Executive (Senior Responsible Owner) is the project's business champion, responsible for the business case and overall project justification, not for day-to-day management. Option B is wrong because the Senior User represents the interests of those who will use the project's outputs and specifies user requirements, but does not manage the project on a daily basis. Option C is wrong because the Senior Supplier represents the interests of those providing the project's products and ensures supplier resources are available, but is not involved in daily project management.
Which document describes the detailed activities, resources, and costs for a single management stage?
The Stage Plan details activities, resources, and costs for a specific stage.
Why this answer
The Stage Plan is the detailed plan for each management stage, created at the end of the previous stage.
During a project, the Project Board is informed that a major change to the project scope is required. Which role is best placed to assess the impact on the Business Case?
Project Assurance independently assesses impacts on the Business Case and advises the Board.
Why this answer
Project Assurance provides independent assessment of project issues, including impact on the Business Case, to the Project Board.
Drag and drop the steps to close a project in PRINCE2 into the correct order.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Why this order
Closing a Project involves preparing closure, handing over products, evaluating, recommending closure, and then formally closing.
In PRINCE2, who 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 one or more Work Packages as assigned by the Project Manager.
In PRINCE2, how often does the Project Board typically meet?
The Project Board meets when needed, typically at stage boundaries or for exceptions.
Why this answer
In PRINCE2, the Project Board is not a day-to-day management body; it meets only when decisions are needed outside the delegated authority of the Project Manager. The correct frequency is exception-driven, meaning the Board convenes when a stage boundary is reached, an exception report is raised, or the project is ready for closure. This aligns with PRINCE2's principle of management by exception, where the Board's involvement is triggered by specific events rather than a fixed schedule.
Exam trap
The trap here is that candidates often confuse the Project Board's meeting frequency with that of a daily stand-up or weekly team meeting, failing to recognize PRINCE2's core principle of management by exception, which dictates that the Board only convenes when triggered by specific events or stage boundaries.
How to eliminate wrong answers
Option A is wrong because daily meetings would imply hands-on, operational management, which contradicts the Project Board's strategic, governance role in PRINCE2. Option B is wrong because a fixed monthly schedule would force unnecessary meetings even when no decisions are required, violating the management-by-exception principle. Option D is wrong because weekly meetings are too frequent for a board that should only intervene when the Project Manager exceeds tolerances or a stage boundary is reached.
Who is responsible for maintaining the Business Case throughout the project?
The SRO owns the Business Case and ensures its viability.
Why this answer
The Senior Responsible Owner (SRO/Executive) owns the Business Case and is responsible for ensuring it remains viable throughout the project.
Which role provides independent assurance to the Project Board that the project is being managed correctly?
Project Assurance provides independent oversight to the Project Board.
Why this answer
Project Assurance is independent of the Project Manager and reports to the Project Board.
Who is responsible for appointing the Project Manager?
The Project Board appoints the Project Manager, usually on the recommendation of the Executive.
Why this answer
In PRINCE2, the Project Board is responsible for appointing the Project Manager. This is because the Project Board represents the business, user, and supplier interests and has the authority to delegate day-to-day management to the Project Manager. The Project Board's responsibility includes ensuring the right person is appointed to manage the project on their behalf.
Exam trap
The trap here is that candidates may confuse the Project Board's collective responsibility with the individual roles of Senior User or Senior Supplier, or mistakenly think the Change Authority has broader management powers than it actually does.
How to eliminate wrong answers
Option B is wrong because the Senior User is a member of the Project Board and does not have sole authority to appoint the Project Manager; that responsibility lies with the Project Board as a whole. Option C is wrong because the Senior Supplier, like the Senior User, is a single role on the Project Board and cannot unilaterally appoint the Project Manager. Option D is wrong because the Change Authority is a role responsible for authorizing changes to project baselines, not for appointing the Project Manager.
Which role chairs the Project Board?
The Executive chairs the Project Board.
Why this answer
The Executive (SRO) chairs the Project Board and is accountable for the project's success.
Which role is responsible for managing the delivery of a Work Package?
The Team Manager manages the delivery of the Work Package.
Why this answer
The Team Manager is responsible for delivering the Work Package as defined by the Project Manager.
A project is in its Controlling a Stage process. The Team Manager reports that a Work Package is likely to be completed late. The Project Manager reviews the Stage Plan and sees that stage tolerance is not forecast to be exceeded. What should the Project Manager do?
The Project Manager can manage within tolerances without escalation.
Why this answer
Since stage tolerance is not threatened, the Project Manager can take corrective action within the delegated tolerances, such as re-planning or re-assigning resources, without escalating to the Project Board.
During the Initiating a Project process, which document is created to define the project's scope, objectives, and how it will be managed?
The PID is the comprehensive document created during initiation.
Why this answer
The Project Initiation Documentation (PID) is the definitive document created during the Initiating a Project process. It consolidates the project's scope, objectives, and management controls, serving as the foundation for project governance and decision-making. PRINCE2 mandates the PID to ensure all stakeholders have a single source of truth for how the project will be managed.
Exam trap
PeopleCert often tests the distinction between the Project Brief (created in Starting Up a Project) and the PID (created in Initiating a Project), leading candidates to confuse the two documents and their respective purposes.
How to eliminate wrong answers
Option A is wrong because the Project Brief is created during the Starting Up a Project process, not Initiating a Project, and it provides initial context and justification but does not define detailed management approaches. Option C is wrong because the Business Case is a component of the PID, not a standalone document that defines scope and management; it focuses on justification and benefits. Option D is wrong because the Benefits Management Approach is a separate management product that details how benefits will be realized and measured, but it does not define the project's overall scope or management structure.
Who chairs the Project Board in PRINCE2?
The SRO/Executive chairs the Project Board.
Why this answer
In PRINCE2, the Project Board is chaired by the Executive (also known as the Senior Responsible Owner in many organizations). The Executive is ultimately accountable for the project's success, provides business justification, and ensures the project remains viable. The chairperson role is explicitly assigned to the Executive in the PRINCE2 management structure, not to the Senior Supplier, Senior User, or Project Manager.
Exam trap
The trap here is that candidates often confuse the Project Manager as the chair because they lead project meetings, but PRINCE2 explicitly assigns the Project Board chair to the Executive, not the Project Manager.
How to eliminate wrong answers
Option B (Senior Supplier) is wrong because the Senior Supplier represents the interests of those providing the project's products and resources, but does not chair the Project Board; they are a board member, not the chair. Option C (Senior User) is wrong because the Senior User represents the users' needs and operational requirements, but they are also a board member without the chairing authority. Option D (Project Manager) is wrong because the Project Manager is responsible for day-to-day management and reporting to the Project Board, but they are not a member of the board and certainly do not chair it.
What is the difference between a Request for Change (RFC) and an Off-specification (Off-spec)?
This correctly distinguishes the two.
Why this answer
In PRINCE2, a Request for Change (RFC) is a formal proposal to change any baselined product, while an Off-specification (Off-spec) is a product that has been identified as not meeting its agreed specification. Option D correctly captures this distinction: an RFC seeks a change to an agreed product, whereas an Off-spec reports a deviation from the specification. This is a fundamental difference in issue handling within PRINCE2's change control approach.
Exam trap
The trap here is that candidates often assume RFCs and Off-specs are the same or that only certain roles can raise them, but PRINCE2 explicitly distinguishes them by purpose and allows any stakeholder to raise either type of issue.
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 Manager or Project Board. Option B is wrong because an Off-spec can affect the Business Case if the deviation impacts costs, benefits, or risks, just as an RFC can. Option C is wrong because the terms are not interchangeable; they represent distinct types of issues with different purposes and handling procedures.
Which TWO of the following are elements of a Work Package?
Work Packages include the description of the products to be produced.
Why this answer
A Work Package is a set of information about one or more required products that the project manager delegates to a team manager or team member. The product description(s) to be delivered are a core element because they define exactly what the team must produce, including quality criteria and acceptance methods. Reporting requirements are also a mandatory element, specifying how and when the team manager must report progress, issues, and completion to the project manager.
Exam trap
The trap here is that candidates confuse project-level documents (Business Case, risk register) or team structure details with the specific information that must be formally delegated in a Work Package, leading them to select options that are relevant to the project but not elements of a Work Package.
Which THREE of the following are responsibilities of the Senior Supplier on the Project Board?
The Senior Supplier secures supplier resources.
Why this answer
The Senior Supplier is responsible for providing supplier resources, ensuring the quality of supplier deliverables, and advising on design and feasibility. The Senior Supplier does not define user acceptance criteria (that's the Senior User) nor manage the project budget (that's the SRO/Executive).
Which THREE of the following are responsibilities of the Project Manager?
The PM prepares stage plans.
Why this answer
The Project Manager is responsible for preparing the Stage Plan for approval by the Project Board. This is a key task in the PRINCE2 'Planning' process, where the Project Manager develops detailed plans for each management stage based on the Project Plan and stage-level tolerances.
Exam trap
The trap here is confusing the Project Manager's role with that of the Project Board or Project Assurance, leading candidates to incorrectly select 'Set project tolerances' (a board responsibility) or 'Provide independent assurance' (an assurance responsibility) instead of focusing on the manager's operational duties.
Which TWO of the following are responsibilities of the Project Board?
The Board approves Stage Plans.
Why this answer
The Project Board is responsible for approving Stage Plans for the next stage (Option A) and authorizing deviations from stage tolerances (Option E). Option B (Preparing the Highlight Report) is the Project Manager's responsibility. Option C (Maintaining the Business Case) is primarily the Senior User's role, with the Project Manager supporting.
Option D (Managing the delivery of Work Packages) is the Team Manager's responsibility. Thus, only A and E are correct.
Which role is responsible for managing the delivery of Work Packages and reporting progress to the Project Manager?
Correct role.
Why this answer
In PRINCE2, the Team Manager is responsible for managing the delivery of Work Packages and reporting progress to the Project Manager. This role ensures that the products defined in the Work Package are created to the required quality, within time and cost constraints, and provides regular progress reports to the Project Manager.
Exam trap
The trap here is that candidates often confuse the Team Manager with the Project Manager, assuming the Project Manager directly manages all work, but PRINCE2 explicitly separates these roles to enable delegation and management by exception.
How to eliminate wrong answers
Option A is wrong because the Project Manager is responsible for overall project management, not for the direct delivery of Work Packages; they delegate that to the Team Manager. Option B is wrong because the Senior Supplier represents the supplier interests on the Project Board and is not involved in day-to-day Work Package delivery or progress reporting to the Project Manager. Option D is wrong because Project Support provides administrative and advisory services, such as maintaining registers and providing planning support, but does not manage Work Packages or report progress on their delivery.
In PRINCE2, what is the purpose of the 'Managing a Stage Boundary' process?
This is the correct purpose of the Managing a Stage Boundary process.
Why this answer
The 'Managing a Stage Boundary' process in PRINCE2 is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and confirm continued business justification. This process ensures that the project remains viable and that the Project Board can make informed go/no-go decisions before committing resources to the next stage.
Exam trap
The trap here is that candidates often confuse the primary purpose of 'Managing a Stage Boundary' (review and approval of the next stage) with the specific activity of producing an Exception Plan, which is a conditional output, not the core purpose.
How to eliminate wrong answers
Option A is wrong because managing the delivery of work packages and monitoring progress is the purpose of the 'Controlling a Stage' process, not 'Managing a Stage Boundary'. Option B is wrong because defining the project scope and creating the Project Plan is the purpose of the 'Initiating a Project' process. Option C is wrong because producing an Exception Plan is an activity that occurs within the 'Managing a Stage Boundary' process when tolerances are forecast to be exceeded, but it is not the primary purpose of the process; the main purpose is to enable the Project Board to review and approve the next stage.
The Project Board consists of three roles. Which of the following is NOT a mandatory role on the Project Board?
The Project Manager attends Project Board meetings but is not a member.
Why this answer
The mandatory roles are Senior User, Senior Supplier, and Senior Responsible Owner. The Project Manager is not a member of the Project Board.
In PRINCE2, what is the main reason for separating the Project Manager role from the Project Assurance role?
Project Assurance provides an independent view to the Project Board, not influenced by the Project Manager.
Why this answer
Separation ensures independent and objective assurance that the project is running correctly, free from the biases or conflicts of day-to-day management.
According to PRINCE2, who is responsible for authorizing the work packages to be executed by the team?
The Project Manager authorizes work packages.
Why this answer
In PRINCE2, the Project Manager is responsible for authorizing work packages to be executed by the team. This is because the Project Manager manages the day-to-day activities and has the authority to assign work to team members or Team Managers, ensuring that the work packages align with the project plan and stage tolerances. The Project Board provides overall direction and approves stage plans, but the authorization of individual work packages is delegated to the Project Manager.
Exam trap
The trap here is that candidates often confuse the Project Board's high-level authority with the Project Manager's delegated authority for operational work package authorization, leading them to incorrectly select the Project Board.
How to eliminate wrong answers
Option A is wrong because the Project Board is responsible for overall project direction, approving stage plans, and making key decisions, but they do not authorize individual work packages—that is delegated to the Project Manager. Option B is wrong because the Senior Responsible Owner (SRO) is a role in PRINCE2 for the business case and project assurance, not for authorizing work packages; the SRO is part of the Project Board but does not handle operational work package authorization. Option D is wrong because the Team Manager is responsible for coordinating and managing the team's work on assigned work packages, but they do not authorize them—they receive authorized work packages from the Project Manager.
Which TWO of the following statements about the Project Board are correct?
Correct: Project Board meetings are held at stage boundaries or when exceptions occur.
Why this answer
The Project Board in PRINCE2 is designed to be an exception-driven body; it convenes only when decisions are required, such as approving stage plans or exception plans, rather than on a fixed schedule. This aligns with the PRINCE2 principle of management by exception, where the board delegates day-to-day management to the Project Manager and escalates only when tolerances are forecast to be exceeded.
Exam trap
The trap here is that candidates often confuse the Project Board's meeting frequency with a typical steering committee that meets regularly, but PRINCE2 specifically mandates an exception-driven approach, not a fixed schedule.
What is the minimum frequency of Project Board meetings?
The Project Board meets at key decision points and when exceptions arise.
Why this answer
The Project Board meets at predetermined points (stage boundaries) and when an exception is raised. They are exception-driven, so there is no fixed minimum frequency.
The Project Board has delegated authority for change control decisions to a separate body. What is this body called?
The Change Authority is an optional role to which the Project Board delegates change control decisions.
Why this answer
In PRINCE2, the Change Authority is a body to which the Project Board delegates responsibility for making decisions on change requests and off-specifications, within defined limits. This allows the board to focus on strategic oversight while empowering a separate group to handle change control efficiently. The Change Authority is formally defined in the 'Organize' process and its authority is documented in the Project Initiation Documentation.
Exam trap
The trap here is that candidates confuse the Change Authority with Project Assurance, mistakenly thinking that assurance includes decision-making power, when in fact Project Assurance is an independent oversight function, not a decision-making body for change control.
How to eliminate wrong answers
Option B (Project Support) is wrong because Project Support provides administrative and clerical services to the project management team, not decision-making authority for change control. Option C (Project Assurance) is wrong because Project Assurance is responsible for monitoring and checking compliance with standards and plans, not for making change control decisions. Option D (Senior Supplier) is wrong because the Senior Supplier is a specific role on the Project Board representing the interests of those providing the project's products, not a separate delegated body for change control.
Which role is responsible for the day-to-day management of the project within the tolerances set by the Project Board?
This is a core responsibility of the Project Manager.
Why this answer
The Project Manager manages the project on a day-to-day basis within the tolerances delegated by the Project Board.
In PRINCE2, what is the role of the Senior Supplier on the Project Board?
The Senior Supplier ensures the project has the required supplier resources and that the supplier's view is represented.
Why this answer
The Senior Supplier represents those who provide the necessary goods, services, and expertise to the project.
The Project Manager notes that a Work Package is at risk of being delivered late. What should the Project Manager do?
The PM manages within stage tolerances and works with the Team Manager.
Why this answer
In PRINCE2, when a Work Package is at risk of being delivered late but remains within its agreed tolerances, the Project Manager should agree corrective actions with the Team Manager. This is because the Team Manager is responsible for day-to-day management of the Work Package, and the Project Manager's role is to support and guide without escalating unless tolerances are forecast to be exceeded. Corrective actions within tolerance keep the project on track without unnecessary escalation.
Exam trap
The trap here is confusing 'at risk of being delivered late' with 'forecast to exceed tolerances,' leading candidates to incorrectly escalate to the Project Board (Option C) instead of managing within tolerance.
How to eliminate wrong answers
Option B is wrong because updating the Project Plan immediately is a reactive administrative action that does not address the root cause of the delay; the plan should only be updated after corrective actions are agreed and implemented. Option C is wrong because escalation to the Project Board is only required when the Work Package is forecast to exceed its tolerances, not when it is merely at risk within tolerance. Option D is wrong because canceling the Work Package and reassigning it to another team is a drastic, disruptive action that bypasses the proper management-by-exception process and ignores the Team Manager's responsibility to resolve issues within tolerance.
Which PRINCE2 role is optional and provides administrative support to the project?
Project Support is optional and provides admin support.
Why this answer
In PRINCE2, Project Support is an optional role that provides administrative services to the project, such as maintaining files, collecting progress data, and managing project documentation. The role is not mandatory because the project manager can perform these tasks or they can be delegated to a separate support function. This distinguishes it from the other roles, which have specific governance or delivery responsibilities.
Exam trap
The trap here is that candidates often confuse Project Support with Project Assurance, thinking both are mandatory oversight roles, but PRINCE2 explicitly separates administrative support (optional) from independent assurance (optional but distinct).
How to eliminate wrong answers
Option A is wrong because the Change Authority is a role that authorizes changes to baselines, not administrative support; it is optional but focuses on change control decisions. Option B is wrong because Project Assurance is an optional role that provides independent oversight and checks compliance with PRINCE2, not administrative support. Option C is wrong because the Team Manager is an optional role that manages the technical delivery of products within a team, not administrative support for the project.
Which of the following is an optional role in the PRINCE2 project management team?
Project Support is optional and can be provided by a separate team member.
Why this answer
In PRINCE2, the Project Support role is optional and is only required when the project is large or complex enough to need administrative or specialist support. The PRINCE2 manual explicitly lists Project Support as a role that may be filled, whereas the Executive, Senior User, and Project Manager are mandatory roles on every project.
Exam trap
The trap here is that candidates often assume all roles listed in the PRINCE2 team structure are mandatory, but PRINCE2 explicitly designates Project Support as optional, while the Executive, Senior User, and Project Manager are always required.
How to eliminate wrong answers
Option A is wrong because the Executive is a mandatory role who owns the business case and provides overall accountability for the project. Option B is wrong because the Senior User is a mandatory role who represents the interests of those who will use the project's outputs. Option D is wrong because the Project Manager is a mandatory role who manages the day-to-day work and is required on every PRINCE2 project.
During which process is the Project Initiation Documentation (PID) created?
The PID is the key output of the Initiating a Project process.
Why this answer
The Project Initiation Documentation (PID) is created during the Initiating a Project process. This process takes the initial project mandate and outline business case from Starting Up a Project and develops them into a comprehensive, baselined set of documents that define the project's scope, objectives, risks, and controls. The PID is formally approved by the Project Board during this process, providing the authority to proceed with the project.
Exam trap
The trap here is confusing the creation of the PID with its approval or subsequent updates; candidates often select Starting Up a Project because they think the PID is created early, but PRINCE2 clearly separates the initial Project Brief from the detailed PID developed in Initiating a Project.
How to eliminate wrong answers
Option A is wrong because Starting Up a Project produces the Project Brief, not the PID; the PID is developed later in Initiating a Project. Option C is wrong because Managing a Stage Boundary updates the PID (e.g., revising the Business Case or Risk Register) but does not create it from scratch. Option D is wrong because Directing a Project is the decision-making process where the Project Board approves the PID, but the actual creation of the PID occurs in Initiating a Project.
Why does PRINCE2 separate the Project Manager role from Project Assurance?
Independence is key to effective assurance.
Why this answer
PRINCE2 separates the Project Manager from Project Assurance to ensure independent oversight of the project's ongoing viability, compliance, and quality. The Project Manager is responsible for day-to-day management and delivery, while Project Assurance provides an objective check that the project remains aligned with business justifications, standards, and controls. This separation prevents the Project Manager from being both the doer and the sole judge of their own work, avoiding conflicts of interest that could compromise governance.
Exam trap
The trap here is that candidates confuse Project Assurance with a support or delegation function, rather than recognizing it as a mandatory independent oversight role that cannot be combined with the Project Manager's responsibilities.
How to eliminate wrong answers
Option B is wrong because PRINCE2 does not define 'technical tasks' as a primary focus for the Project Manager; the role is about management, coordination, and control, not technical execution. Option C is wrong because workload reduction is not the purpose of the separation; the roles are distinct to provide checks and balances, not to lighten the Project Manager's load. Option D is wrong because the Project Board cannot delegate Project Assurance to the Project Manager; doing so would eliminate the independent oversight that the role is designed to provide, violating the principle of separation of duties.
A Project Manager is appointed to a project during the Starting Up a Project process. The project has a complex technical scope. The SRO wants to ensure that the Project Board receives independent assurance on technical decisions. Who should provide this assurance?
Project Assurance is independent and can be staffed with technical expertise.
Why this answer
Project Assurance is an independent oversight role that reports to the Project Board. The SRO can assign technical assurance to an individual with appropriate skills, separate from the Project Manager.
Which role is responsible for ensuring that the project is being managed correctly from the business perspective?
Project Assurance is independent and assures the Project Board.
Why this answer
Project Assurance provides independent oversight to the Project Board, ensuring the project is managed correctly from business, user, and supplier perspectives. The Executive is accountable but Project Assurance performs the checks.
Which TWO of the following are true about Project Assurance?
Assurance ensures compliance with standards and processes.
Why this answer
Project Assurance is a PRINCE2 role that verifies the project is being conducted correctly, meaning it checks that the project remains viable, adheres to its business case, and follows the defined management stages. It is not about doing the work but about ensuring compliance with the project's plans, controls, and standards. This aligns with PRINCE2's principle of continued business justification and the need for independent oversight.
Exam trap
The trap here is that candidates often confuse Project Assurance with Project Support or Quality Management, or assume the Project Manager can double-hat as the assurance role, but PRINCE2 explicitly requires independence to avoid bias and ensure objective oversight.
Which TWO statements about the project board are correct? (Choose two.)
The board provides unified direction.
Why this answer
The project board provides unified direction to the project, ensuring that the business, user, and supplier interests are represented and aligned. This is a core PRINCE2 principle: the board makes key decisions and approves stage plans, but does not get involved in day-to-day management.
Exam trap
The trap here is confusing accountability with responsibility: candidates often think the board handles day-to-day tasks or product creation, but PRINCE2 strictly separates strategic oversight from operational management.
Why does PRINCE2 separate the Project Manager from Project Assurance?
Correct. Project Assurance is independent from the PM.
Why this answer
Separation ensures independent oversight of the Project Manager's work, preventing conflicts of interest and providing objective assurance to the Project Board.
In PRINCE2, what is the difference between a Request for Change (RFC) and an Off-specification?
Correct distinction.
Why this answer
In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product or process that has already been baselined, while an Off-specification is a notification that a product does not meet its agreed specification. Option D correctly captures this distinction: an RFC seeks to change the baseline, whereas an Off-specification identifies a deviation from the existing specification. This is a core concept in PRINCE2's change control approach, ensuring that baselines are protected and issues are properly categorized.
Exam trap
In PRINCE2 exams, candidates often confuse RFC and Off-specification as synonyms or think one is always approved/rejected. The key trap is forgetting that an RFC proposes a change to a baseline, while an Off-specification reports a product not meeting its specification.
How to eliminate wrong answers
Option A is wrong because RFC and Off-specification are distinct issue types in PRINCE2; an RFC proposes a change to an agreed baseline, while an Off-specification identifies a product that fails to meet its specification, and they are not interchangeable. Option B is wrong because neither an RFC nor an Off-specification has a predetermined outcome; both can be approved or rejected by the appropriate authority (e.g., the Change Authority or Project Board) based on impact assessment. Option C is wrong because both an RFC and an Off-specification can be raised by any stakeholder, not exclusively by the Project Board or Project Manager; the PRINCE2 guidance emphasizes that anyone can raise an issue, though the Project Manager typically logs and manages them.
In PRINCE2, who manages the delivery of Work Packages?
Correct. The Team Manager manages Work Package delivery.
Why this answer
The Team Manager is responsible for managing the delivery of one or more Work Packages and reports to the Project Manager.
Which role delegates change control decisions to a Change Authority?
The Project Board delegates change control decisions to the Change Authority.
Why this answer
In PRINCE2, the Project Board is responsible for overall project governance, including delegating change control decisions to a Change Authority. This delegation allows the Change Authority to approve or reject change requests within predefined limits, freeing the Board from day-to-day change management while retaining strategic oversight.
Exam trap
The trap here is that candidates often confuse the Project Manager's role in recommending changes with the authority to delegate change control, but PRINCE2 explicitly reserves that delegation power for the Project Board.
How to eliminate wrong answers
Option A is wrong because the Team Manager focuses on delivering the work packages within their team and does not have authority over change control decisions. Option C is wrong because the Senior Supplier is a specific role on the Project Board representing the supplier's interests, not a separate role that delegates change authority. Option D is wrong because the Project Manager manages day-to-day activities and may recommend changes but does not have the authority to delegate change control decisions; that authority rests with the Project Board.
Which role is responsible for the independent assurance that the project remains on track?
Project Assurance provides independent assurance to the Project Board.
Why this answer
Project Assurance is the role responsible for providing independent assurance that the project remains on track, as defined by PRINCE2. It ensures that the project is being conducted correctly, adheres to the business case, and meets quality standards, without being involved in the day-to-day management. This role is separate from the Project Manager and Project Support to maintain objectivity.
Exam trap
The trap here is that candidates often confuse Project Assurance with Project Support, thinking both are administrative roles, but Project Assurance is a governance function focused on independent oversight, while Project Support is purely administrative.
How to eliminate wrong answers
Option B is wrong because Project Support provides administrative and clerical services to the project team, not independent oversight or assurance. Option C is wrong because the Team Manager is responsible for delivering the work packages within their team, not for independent assurance across the entire project. Option D is wrong because the Project Manager manages the project on a day-to-day basis and cannot provide independent assurance due to their direct involvement and potential bias.
Which THREE of the following are reasons why PRINCE2 recommends separating the Project Manager from Project Assurance?
Independence is key for unbiased assurance.
Why this answer
PRINCE2 mandates that Project Assurance be independent from the Project Manager to ensure objective and unbiased monitoring of the project's performance against plans, risks, and quality criteria. This separation prevents the Project Manager from self-assessing their own work, which could lead to skewed reporting or overlooked issues. The independence is a core principle of the PRINCE2 governance model, ensuring that assurance activities are not influenced by the day-to-day pressures of delivery.
Exam trap
PRINCE2 often tests the misconception that separating roles reduces costs or speeds up decisions, but PRINCE2 emphasizes that the primary purpose is to ensure objective oversight and avoid conflicts of interest, not to improve efficiency or reduce expenses.
Which TWO of the following are roles that are part of the Project Board?
The Senior User is a mandatory Project Board role.
Why this answer
The Project Board is the PRINCE2 management layer responsible for overall project direction and key decision-making. The Senior User is a mandatory Project Board role representing the interests of those who will use the project's products, ensuring the project delivers the required benefits. The Executive is also a mandatory Project Board role, acting as the project's ultimate decision-maker and owner of the business case.
Exam trap
PeopleCert often tests the distinction between roles that are part of the Project Board (Executive, Senior User, Senior Supplier) and roles that support or execute within the Project Management Team (Project Manager, Team Manager, Project Assurance, Project Support), tempting candidates to select Project Assurance or Project Support as Board members.
A large IT project is implementing a new customer relationship management (CRM) system for a multinational corporation. The project is organized with a Project Board comprising the Executive (VP of Sales), Senior User (Regional Sales Director), and Senior Supplier (IT Director). The Project Manager is an experienced PMP-certified professional. The team includes several business analysts and developers from an external supplier. The project has just completed the Initiating a Project process and received authorization to proceed to the next stage. However, during the first week of the Delivery Stage, the Project Manager notices that the business analysts are not collaborating effectively with the developers, leading to misunderstandings about requirements. The Project Manager holds a meeting and discovers that the business analysts feel excluded from decision-making and the developers complain about unclear specifications. The Project Manager wants to resolve this using PRINCE2 principles and practices. Which of the following is the BEST course of action?
Correct: The Project Manager should use the Communication Management Strategy to facilitate collaboration and ensure roles are clear.
Why this answer
PRINCE2's Communication Management Strategy is the formal mechanism for defining roles, responsibilities, and information flows. By revisiting it, the Project Manager can clarify the business analysts' and developers' roles in decision-making and requirements specification, directly addressing the root cause of misunderstandings. This aligns with the 'Manage by Stages' and 'Defined Roles and Responsibilities' principles, ensuring the team collaborates effectively without unnecessary escalation or personnel changes.
Exam trap
The trap here is that candidates may assume any team conflict requires escalation to the Project Board (Option D), but PRINCE2 reserves escalation only for issues exceeding stage tolerances or requiring business-level decisions, not for internal team coordination problems.
How to eliminate wrong answers
Option A is wrong because ignoring the issue violates PRINCE2's 'Manage by Exception' principle; unresolved team dynamics can escalate into requirements errors and rework, jeopardizing stage tolerances. Option B is wrong because replacing team members without first addressing the communication breakdown ignores the PRINCE2 focus on process improvement and the 'Learn from Experience' principle; the problem is likely procedural, not individual competence. Option D is wrong because the issue is within the Project Manager's authority to resolve via the Communication Management Strategy; escalating to the Project Board for a team restructuring decision bypasses the PM's responsibility and violates the 'Manage by Stages' principle where the PM manages day-to-day issues.
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 to the Project Manager.
Why does PRINCE2 separate the Project Manager from Project Assurance?
Correct.
Why this answer
The separation ensures independent oversight. The Project Manager is responsible for day-to-day management, while Project Assurance provides an impartial view to the Project Board to avoid conflicts of interest.
What is the difference between a Request for Change (RFC) and an Off-specification?
Correct: RFCs are for desired modifications; Off-specifications are for deviations from the original specification.
Why this answer
An RFC is a proposal for a modification (change) to the project's products, while an Off-specification is a situation where a product does not meet its specification (a deviation).
In PRINCE2, a Team Manager reports to the Project Manager. What is the primary responsibility of a Team Manager?
Correct. The Team Manager manages work package delivery.
Why this answer
The Team Manager is responsible for delivering one or more Work Packages as defined in the Stage Plan. This role focuses on the technical delivery of products within the constraints agreed with the Project Manager, ensuring quality, time, and cost targets are met for those specific work packages.
Exam trap
The trap here is confusing the Team Manager's scope with the Project Manager's broader responsibilities, leading candidates to select Option D, which describes the Project Manager's role, not the Team Manager's.
How to eliminate wrong answers
Option A is wrong because providing independent assurance to the Project Board is the responsibility of the Project Assurance role, not the Team Manager. Option C is wrong because updating the Business Case is the responsibility of the Senior User or Executive, not the Team Manager. Option D is wrong because managing day-to-day project activities across all stages is the responsibility of the Project Manager, while the Team Manager only manages activities within their assigned Work Packages.
What is the key difference between Project Assurance and Project Support?
This is the correct distinction as defined in PRINCE2.
Why this answer
Project Assurance is an independent oversight function, performed on behalf of the Project Board, to ensure that the project is being conducted correctly and remains viable. Project Support, in contrast, is a set of administrative and advisory services provided to the Project Manager to help them manage the project effectively. This distinction is fundamental to PRINCE2's separation of 'doing' from 'checking'.
Exam trap
The trap here is confusing the independent oversight of Project Assurance with the administrative assistance of Project Support, leading candidates to incorrectly assign Assurance to the Project Manager or to think Support is optional.
How to eliminate wrong answers
Option A is wrong because Project Assurance is not performed by the Project Manager; it is an independent role, often fulfilled by someone outside the project management team, while Project Support is provided to the Project Manager, not by the team. Option C is wrong because both Project Assurance and Project Support can address quality and risk; the key difference is not the focus area but the independence and accountability (Assurance reports to the Board, Support assists the Manager). Option D is wrong because both Project Assurance and Project Support are mandatory roles in PRINCE2; neither is optional.
Which THREE of the following statements about the Project Board are correct?
Yes, the Board authorizes stage transitions.
Why this answer
The Project Board is responsible for authorizing the movement from one stage to the next, which includes approving the Stage Plan for the next stage and reviewing the current stage's completion. This is a key control point in PRINCE2's stage-gate management approach, ensuring that the project only proceeds when the Board is satisfied with progress and the business case remains viable.
Exam trap
The trap here is that candidates often confuse the Project Board's composition with the project team, mistakenly including the Project Manager, or assume a fixed meeting schedule similar to a steering committee in other methodologies, whereas PRINCE2 mandates event-driven rather than time-driven Board meetings.
What is the key difference between Project Assurance and a quality review?
Correct. Project Assurance is a continuous role; quality review is a technique used to assess product quality.
Why this answer
Project Assurance is a role within the PRINCE2 management structure, responsible for ensuring that the project remains viable and compliant with the business case, while a quality review is a technique used to assess the quality of a product. Option D correctly distinguishes between these two concepts: Project Assurance is a role, and quality review is a technique. This aligns with PRINCE2's separation of management responsibilities from quality control activities.
Exam trap
The trap here is that candidates confuse the hierarchical nature of PRINCE2 roles and techniques, often misidentifying Project Assurance as a process or quality review as a role, due to the similar-sounding names and overlapping involvement in quality activities.
How to eliminate wrong answers
Option A is wrong because Project Assurance is not performed by the Project Manager; it is an independent role performed by the Project Board or its delegates, while quality review involves the team, but the key difference is not about who performs them. Option B is wrong because it reverses the definitions: quality review is a technique, not a role, and Project Assurance is a role, not a process. Option C is wrong because they are fundamentally different concepts: Project Assurance is a governance role ensuring ongoing compliance, while quality review is a specific technique for product quality assessment.
Which THREE of the following are responsibilities of the Project Manager?
Producing Highlight Reports is a direct responsibility of the Project Manager under PRINCE2’s management-by-exception principle, as the PM must provide the Project Board with regular, exception-based progress updates. This satisfies the constraint that the PM owns all day-to-day reporting activities, ensuring the Board receives timely summaries of stage status, risks, and deviations without being involved in operational details.
Why this answer
The Project Manager manages day-to-day activities, produces Highlight Reports for the board, and updates the Business Case as needed. The PM does not chair the board or perform assurance.
Which role is responsible for the day-to-day management of a Work Package?
The Team Manager manages the delivery of Work Packages.
Why this answer
The Team Manager is responsible for delivering Work Packages and managing the team's day-to-day work, reporting to the Project Manager.
Which TWO of the following are roles defined in PRINCE2?
Team Manager is a PRINCE2 role responsible for managing work packages.
Why this answer
Team Manager and Project Assurance are PRINCE2 roles. The others are not.
In PRINCE2, what is the difference between accountability and responsibility?
Accountability cannot be delegated, while responsibility can be shared or delegated.
Why this answer
In PRINCE2, accountability refers to the ultimate answerability for the successful completion of a deliverable or objective, and it is always held by a single person (e.g., the project manager is accountable for the project). Responsibility, in contrast, can be shared among multiple team members or delegated to others who perform the work. Option B correctly captures this distinction, which is fundamental to the PRINCE2 management product structure and role definitions.
Exam trap
The trap here is that candidates often confuse accountability with responsibility, assuming they are interchangeable or that accountability can be delegated like responsibility, leading them to pick Option A or D.
How to eliminate wrong answers
Option A is wrong because PRINCE2 explicitly distinguishes between accountability (ultimate ownership, held by one person) and responsibility (task execution, can be shared or delegated); they are not synonyms. Option C is wrong because while accountability is assigned to individuals, responsibility is not necessarily shared among teams—it can be assigned to a single individual as well, and the key difference is that accountability cannot be shared or delegated. Option D is wrong because it reverses the PRINCE2 principle: accountability cannot be delegated (it remains with the person who holds it), whereas responsibility can be delegated to others to perform the work.
Who is responsible for maintaining the Business Case throughout the project?
The SRO owns the Business Case and is accountable for it throughout the project.
Why this answer
The Senior Responsible Owner (SRO/Executive) is the single person ultimately accountable for the project's business justification. They own the Business Case and are responsible for ensuring it remains viable, aligned with corporate strategy, and is formally reviewed at key decision points (e.g., stage boundaries). The PRINCE2 principle of continued business justification places this accountability squarely on the Executive, not on the Project Manager or support roles.
Exam trap
PeopleCert often tests the distinction between accountability (Executive) and responsibility (Project Manager) for the Business Case, trapping candidates who confuse day-to-day maintenance with ultimate ownership.
How to eliminate wrong answers
Option A is wrong because the Senior Supplier represents the interests of those providing the project's specialist products and resources; they do not own the Business Case, though they contribute to its feasibility. Option C is wrong because Project Support provides administrative and advisory services (e.g., maintaining registers, configuration management) but has no authority to own or approve the Business Case. Option D is wrong because the Project Manager is responsible for developing, reviewing, and maintaining the Business Case on a day-to-day basis, but the ultimate accountability and ownership rests with the Executive (SRO).
The Project Board is considering a Request for Change. Which role is authorized to approve changes within delegated limits?
The Change Authority has delegated authority to approve changes.
Why this answer
The Change Authority role is specifically authorized to approve Requests for Change within delegated limits set by the Project Board. This delegation allows the Change Authority to make decisions on low-impact changes without requiring full Board approval, streamlining the change control process.
Exam trap
The trap here is that candidates often assume the Project Manager has approval authority for changes, but PRINCE2 explicitly separates the management of change control from the authority to approve changes, which is delegated to the Change Authority.
How to eliminate wrong answers
Option A is wrong because the Project Manager manages the change control process but does not have the authority to approve changes unless explicitly delegated as the Change Authority. Option B is wrong because the Senior Supplier represents the supplier's interests on the Project Board and is not automatically authorized to approve changes within delegated limits. Option C is wrong because the Senior User represents the users' interests on the Project Board and is not automatically authorized to approve changes within delegated limits.
Which role is optional in the PRINCE2 project management team?
Project Support is optional and can be provided by the Project Manager if needed.
Why this answer
In PRINCE2, the Project Manager, Project Board, and Team Manager are all mandatory roles within the project management team. Project Support is the only optional role, as its responsibilities can be absorbed by the Project Manager or other team members, or provided by a separate office like a PMO. The PRINCE2 manual explicitly states that Project Support is not a required role, making D the correct answer.
Exam trap
The trap here is that candidates often assume all roles listed in the PRINCE2 management team are mandatory, but PRINCE2 explicitly designates Project Support as optional, testing whether you know the distinction between 'required' and 'optional' roles.
How to eliminate wrong answers
Option A is wrong because the Project Manager is a mandatory role responsible for day-to-day management and is required in every PRINCE2 project. Option B is wrong because the Project Board is a mandatory role providing overall direction and decision-making authority; without it, the project cannot be governed. Option C is wrong because the Team Manager is a mandatory role when the project is large or complex enough to require delegation of technical delivery; PRINCE2 mandates this role if the Project Manager cannot directly manage the team.
Which TWO statements about the Project Board are true?
The Project Board directs the PM and makes key decisions.
Why this answer
The Project Board is accountable for the project's success, meets exception-driven, and comprises SRO, Senior User, and Senior Supplier. It does not meet regularly; it meets when exceptions occur or at stage boundaries.
Which role is accountable for the project's Business Case throughout the project?
The SRO is the single point of accountability for the project, including the Business Case.
Why this answer
The Senior Responsible Owner (Executive) is accountable for the Business Case throughout the project in PRINCE2. This role owns the Business Case, ensures it remains viable, and is responsible for the project's justification and continued alignment with organizational objectives. The Executive is the ultimate decision-maker and must approve any changes to the Business Case.
Exam trap
PRINCE2 often tests the distinction between accountability and responsibility, where candidates mistakenly assign accountability for the Business Case to the Project Manager (who is responsible for managing it) rather than the Executive (who is accountable for it).
How to eliminate wrong answers
Option A is wrong because the Senior User represents the interests of those who will use the project's outputs, but they are not accountable for the Business Case; they contribute to it by specifying requirements and benefits. Option B is wrong because the Project Manager is responsible for managing the project on a day-to-day basis and for creating and maintaining the Business Case document, but accountability for its content and viability rests with the Executive. Option C is wrong because Project Assurance provides independent oversight and checks that the project is being managed correctly, but it does not hold accountability for the Business Case; its role is to advise and verify, not to own.
Which role is responsible for ensuring the project provides value for money and is aligned with business strategy?
The SRO owns the Business Case and ensures value for money.
Why this answer
The Senior Responsible Owner (Executive) is the single point of accountability for ensuring the project delivers value for money and remains aligned with the organization's business strategy. This role owns the business case, approves key stage boundaries, and has ultimate authority over project funding and continuation, directly linking project outputs to strategic objectives.
Exam trap
PeopleCert often tests the misconception that the Project Manager owns the business case or that the Senior User ensures strategic alignment, but PRINCE2 explicitly assigns business case ownership and strategic accountability to the Executive alone.
How to eliminate wrong answers
Option B (Senior Supplier) is wrong because the Senior Supplier represents the interests of those providing the project's products or services, focusing on technical feasibility and resource availability, not on business strategy or value-for-money justification. Option C (Project Manager) is wrong because the Project Manager is responsible for day-to-day management, planning, and delivery within constraints, but does not own the business case or have authority to align the project with corporate strategy. Option D (Senior User) is wrong because the Senior User represents the end-users' needs and ensures the final product meets operational requirements, but does not have accountability for strategic alignment or financial value assessment.
Which document is the key output of the Initiating a Project process?
Correct: The PID is the key output of Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the definitive output of the Initiating a Project process, as it consolidates all key planning information—such as the Business Case, project scope, and risk assessment—into a single baseline that authorizes the project to proceed. PRINCE2 mandates that the PID is created during this process to provide a firm foundation for the project and is used throughout the remaining stages.
Exam trap
PeopleCert often tests the distinction between the Project Brief (an input) and the Project Initiation Documentation (the key output), so candidates mistakenly choose the Project Brief because it is created earlier and seems foundational, but the PID is the formal authorization document produced during Initiating a Project.
How to eliminate wrong answers
Option A is wrong because a Stage Plan is produced during the Managing a Stage Boundary process, not during Initiating a Project, and it details the work for a specific management stage rather than the overall project. Option B is wrong because the Benefits Management Approach is developed as part of the Initiating a Project process but is a separate management product, not the key output; the PID is the comprehensive document that includes or references it. Option D is wrong because the Project Brief is created during the Starting Up a Project process as an input to Initiating a Project, not as an output of that process.
Ready to test yourself?
Try a timed practice session using only People: organizations, teams, and leadership questions.