CCNA PRINCE2 Processes Questions

The Project Board authorizes initiation, authorizes the project, authorizes stage plans, gives ad-hoc direction, and authorizes closure. They do not manage day-to-day work or produce Checkpoint Reports.

In the Initiating a Project process, the PID is created, which includes the Benefits Management Approach, Project Plan, and other management approaches.

MP's purpose is to control the link between the PM and Team Manager by accepting Work Packages and ensuring delivery. Approving stage plans is done in DP; reporting to the Board is done in CS.

The Project Board authorizes initiation, authorizes stage plans, and gives ad-hoc direction. Producing Highlight Reports is the PM's responsibility, and approving Work Packages is part of Controlling a Stage.

Closing a Project ensures a controlled closure, handover of products, and production of the End Project Report and Lessons Report. It confirms benefits review arrangements.

A Work Package is a set of information about one or more products to be created, including requirements, constraints, and acceptance criteria.

The PID and the Stage Plan for the next stage are outputs of IP. The Project Brief is an output of SU, and the End Stage Report is an output of SB.

The Project Board, through the Directing a Project process, authorizes the initiation of a project after reviewing the outputs from Starting Up a Project.

The Project Board authorizes initiation as part of the Directing a Project process.

The Project Brief is the correct key input because it contains the high-level scope, objectives, and constraints that define the project's boundaries. During the Initiating a Project process, the Project Plan is developed by elaborating on the information in the Project Brief, ensuring the plan aligns with the project's initial justification and requirements.

Starting Up a Project is a pre-project process to check viability before committing resources, while Initiating a Project formally establishes the project with detailed plans and management strategies.

Option A is correct because the Project Board is responsible for authorizing project closure as part of the Directing a Project process. This ensures that the project formally ends only after all objectives have been met, products accepted, and lessons recorded, providing governance and control over the project's lifecycle.

The PM should assess the impact of the issue on the stage plan and decide whether corrective action is needed or if it can be handled within tolerance.

The Initiating a Project process is responsible for establishing a solid foundation for the project, and its key output is the Project Initiation Documentation (PID). The PID consolidates all the planning and analysis work into a single, controlled document that defines the project's scope, business justification, risks, and management controls. This document is used to obtain authorization to proceed with the project's delivery stages.

The Starting Up a Project process produces the Project Brief and the Daily Log as outputs. The Project Brief provides a high-level overview of the project's justification, scope, and approach, while the Daily Log is used to record informal issues, actions, and events during the startup phase. These are distinct from later-stage documents like the Project Initiation Documentation or End Project Report.

The Highlight Report is produced by the Project Manager and sent to the Project Board to provide a summary of progress within a stage.

Option C is correct because in PRINCE2, the Highlight Report is a formal report produced by the Project Manager for the Project Board to provide a summary of progress, while the Checkpoint Report is produced by the Team Manager for the Project Manager to report on progress within a Work Package. This distinction is defined in the PRINCE2 manual's 'Reporting' theme and the 'Controlling a Stage' process.

Managing Product Delivery (MP) is the process by which the Team Manager accepts and executes Work Packages and ensures products meet quality criteria.

The Project Manager should escalate via an Exception Report in Controlling a Stage (CS) or at a stage boundary. However, if within a stage, CS is the appropriate process to raise the exception.

Authorizing Work Packages is an activity within the Controlling a Stage process, where the PM assigns work to teams.

The CP process includes preparing the End Project Report, Lessons Report, and confirming benefits review arrangements. The Project Board authorizes closure in the DP process.

The Controlling a Stage process includes the activity of authorising Work Packages, which are formal agreements to produce products. The Project Manager assigns work packages to the Team Manager.

The Starting Up a Project process outputs the Project Brief, Daily Log, initiation Stage Plan, and appoints the Executive and Project Manager. The Risk Management Approach is developed later in Initiating a Project.

The Team Manager is responsible for accepting and delivering Work Packages, ensuring that products meet quality criteria.

The End Stage Report is produced to report on the current stage's performance.

Managing a Stage Boundary is the process where the PM presents an End Stage Report and next Stage Plan to the Board for approval.

The Board authorizes the project after reviewing the PID, which is produced in IP. This is the 'authorize the project' activity in DP.

In the Managing Product Delivery process, the Team Manager is responsible for producing the Checkpoint Report. This report provides the Project Manager with progress information on the work packages assigned to the team, including any issues such as quality problems. The Checkpoint Report is a key control document that the Team Manager uses to communicate status at regular intervals, typically weekly.

Closure is authorised by the Project Board in the Directing a Project process, based on the End Project Report and closure recommendation from the PM.

The Starting Up a Project process ensures that there is a viable and worthwhile project before the initiation stage begins.

SB produces the End Stage Report, updated Project Plan, next Stage Plan (or Exception Plan), and Lessons Report. The Highlight Report is from CS, and the Project Brief is from SU.

The Executive is the single individual responsible for the Business Case throughout the project in PRINCE2. They own the Business Case and must ensure it remains viable, justified, and aligned with organizational strategy, approving any changes to it. The Project Manager only maintains the Business Case document but does not have authority to update its justification or approve changes.

In PRINCE2, the project board is responsible for making decisions about project viability, including closure. During the Initiating a Project process, if the business case becomes unviable, the project manager must escalate this to the project board, who then decides whether to close the project. Option C correctly reflects this by advising the board and recommending closure, aligning with the 'continued business justification' principle.

Directing a Project is the process used by the Project Board to make key decisions and provide overall direction and control, including authorization of stages and closure.

Closing a Project includes handing over products and producing the Lessons Report. The End Stage Report is from SB, and the Project Brief is from SU.

Closing a Project ensures controlled closure, handover of products, and confirmation that the project is complete. It does not manage benefits realization; that happens post-project.

Managing a Stage Boundary (SB) is the process for reporting on the current stage and planning the next stage, producing both the End Stage Report and the next Stage Plan.

Directing a Project ensures the Project Board provides direction and makes key decisions, including authorising initiation, stage plans, and closure.

In PRINCE2, the Benefits Management Approach is a living document that must be updated with actual results during the Closing a Project process, even if benefits are not yet fully realized. Since the business case has not been fully realized, the project manager should record the actual benefits achieved and recommend a follow-on action plan for the remaining benefits to be managed post-project. This ensures that the expected benefits are not lost and that the organization can continue to pursue them.

The Starting Up a Project process is responsible for appointing the Executive and the Project Manager because it occurs before the project is formally initiated. During this process, the project mandate is reviewed, and key roles are assigned to ensure the project has the necessary leadership to proceed to the initiation stage. This is defined in PRINCE2 as the point where the project board is established and the Project Manager is selected.

Highlight Reports are produced by the Project Manager and sent to the Project Board during the Controlling a Stage process. Checkpoint Reports are produced by Team Managers.

A Highlight Report is periodic and reports progress within tolerances; an Exception Report is triggered when a tolerance is forecast to be exceeded.

Starting Up a Project is a pre-project process to ensure that there is a viable and worthwhile project before committing to significant resources. It creates the Project Brief and Initiation Stage Plan.

CS includes authorizing Work Packages, reviewing progress, and reporting highlights. Producing the End Stage Report is done in SB.

The Team Manager should notify the Project Manager that the product is ready for acceptance. The PM arranges quality review and acceptance.

Checkpoint Reports are produced by the Team Manager (or team members) and sent to the Project Manager to report progress on a Work Package.

If a product does not meet quality criteria, the Project Manager should raise an Issue (specifically an Off-specification) and decide on corrective action.

Option C is correct because the End Stage Report is the formal mechanism to report stage performance, including cost variances, to the Project Board. The project manager must include the actual cost ($520,000) against the planned budget ($500,000) and provide an updated forecast, allowing the board to make an informed decision. This aligns with PRINCE2's management by exception principle, where variances within tolerance are reported in the End Stage Report, not via an exception report.

The Team Manager should escalate to the Project Manager via the Managing Product Delivery process. The Project Manager will decide to revise the Work Package or raise an exception.

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.

When a stage tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is PRINCE2's management by exception principle.

The Project Brief is the key output that provides a definition of the project and justifies its viability.

Directing a Project is the process by which the Project Board authorizes initiation, authorizes the project, authorizes stage plans, and gives ad hoc direction.

The Starting Up a Project process produces the Project Brief, which provides a high-level overview of the project to support the decision to proceed to initiation.

Managing a Stage Boundary (SB) is the process where the PM reports on the current stage (End Stage Report) and plans the next stage (next Stage Plan).

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager as part of the Managing Product Delivery process.

Authorizing Work Packages is an activity in the Controlling a Stage process, where the PM assigns work to Team Managers.

The PID and Benefits Management Approach are created in IP. The Project Brief is from SU, and the End Project Report is from CP.

Highlight Reports are produced by the Project Manager during the Controlling a Stage process and sent to the Project Board to provide a summary of progress.

SB produces the End Stage Report and the next Stage Plan (or Exception Plan).

SU is a pre-project process that ensures the prerequisites for initiating a project are in place, including the appointment of the Executive and Project Manager and the creation of the Project Brief.

The Project Brief is produced during Starting Up a Project and provides the baseline for the Initiation Stage. It contains the project definition, outline business case, and other preliminary information.

The Controlling a Stage process includes the activity of authorizing Work Packages. The Project Manager assigns work to Team Managers via Work Packages in this process.

The Managing Product Delivery process is used to control the link between the project manager and the team managers, authorizing work on the first stage's products. Since the project initiation documentation (PID) is approved, the project board has authorized the project, and the project manager uses Managing Product Delivery to assign work packages to the team for execution.

If a tolerance is forecast to be exceeded during a stage, the PM should have already escalated via an Exception Report in Controlling a Stage. However, if this is identified during Managing a Stage Boundary, the PM should still produce an Exception Plan for the Board's approval.

Checkpoint Reports are produced by Team Managers to inform the PM of progress on Work Packages.

The Managing a Stage Boundary process produces the End Stage Report to summarize the current stage's performance against its Stage Plan, and the Stage Plan for the next stage to define the work for the upcoming stage. These are mandatory outputs because the process prepares the project for the next stage or closure decision by the Project Board.