CCNA PRINCE2 Processes Questions

The correct matches are: Product-Based Planning (identification of products and their relationships), Quality Review (reviewing product quality and identifying defects), Change Control (managing change requests), and Configuration Management (controlling and tracking product versions). Common confusions arise from mixing the definitions of Quality Review and Change Control.

Checkpoint Reports are produced by the Team Manager in MP to inform the Project Manager of progress on Work Package activities.

Managing a Stage Boundary is used to produce an Exception Plan and request authorization from the Project Board.

Checkpoint Reports provide the PM with progress information on work packages, including actuals, forecasts, and issues, to support day-to-day management.

SB includes reporting on current stage performance, planning the next stage, and updating the project plan. Authorizing Work Packages is done in CS; directing the project is done in DP.

The Checkpoint Report is the progress report produced by the Team Manager and sent to the Project Manager during the Managing Product Delivery process.

Directing a Project (DP) is the process by which the Project Board authorizes initiation, stage plans, and project closure. Starting Up a Project (SU) prepares for initiation but does not authorize it.

The Starting Up a Project process is designed to ensure that the prerequisites for initiating a project are in place before any significant work begins. It focuses on verifying that the project has a viable business justification, a clear project mandate, and that necessary resources and personnel are available, thereby preventing wasted effort on projects that lack a solid foundation.

The Team Manager should raise the issue to the Project Manager, who will handle it in CS. The Team Manager cannot escalate directly to the Board.

In PRINCE2, the Project Board is responsible for authorizing the initiation of a project. This is because the Project Board represents the business, user, and supplier interests and has the authority to commit resources and approve the project's initiation stage. The Project Manager prepares the initiation documentation, but only the Project Board can give the formal authorization to proceed.

SB is performed near the end of each stage (except the final) to produce an End Stage Report, plan the next stage, and update the Project Plan. It also captures lessons and can produce an Exception Plan if needed.

The Directing a Project process is where the Project Board authorizes the work for each stage, including the initiation stage and subsequent stages.

The Benefits Management Approach is created during the Initiating a Project process to define how and when the expected benefits from the project will be measured, realized, and reviewed. It ensures that the project's outputs translate into measurable outcomes aligned with the business case, and it is a key component of the PRINCE2 principle of continued business justification.

The Directing a Project process is designed for the Project Board to make key decisions and exercise overall control. Its primary purpose is to authorize the initiation of the project, approve stage plans, and authorize project closure, ensuring the project remains viable and aligned with business objectives.

The End Stage Report provides the current stage's performance, which feeds into the Business Case update. The Benefits Management Approach and other documents are also considered, but the End Stage Report is key for performance data.

The Project Board uses the Directing a Project process to authorise closure, based on the recommendation from CP.

In PRINCE2, the Checkpoint Report is a progress report prepared by the Team Manager on behalf of the team. It provides the Project Manager with a snapshot of the work completed, planned, and any issues or risks within a work package. The Project Manager uses this report during the Controlling a Stage process to monitor progress and make informed decisions.

The Project Manager produces the End Stage Report during the Managing a Stage Boundary process.

The Initiating a Project process is where the project's foundations are solidified, and its key output is the Project Initiation Documentation (PID). The PID consolidates all the planning and analysis from the initiation stage into a single, comprehensive document that defines the project's scope, objectives, business justification, risks, and management controls, serving as the baseline for the project board's authorization to proceed.

The End Stage Report is sent to the Project Board, who then decides whether to authorize the next stage (or, if the project is in the final stage, to close the project).

In SB, the PM produces the End Stage Report, updates the Project Plan, and produces a Stage Plan for the next stage. Authorizing work packages is done in CS. Producing Highlight Reports is done in CS.

The Project Board is the decision-making body that reviews Exception Plans when a stage is forecast to exceed its tolerances. This review is performed as part of the 'Directing a Project' process, which covers board-level decisions such as approving exception plans, mid-stage corrections, and project closure. The board does not execute the plan; it authorizes or rejects it.

Directing a Project includes authorizing initiation, authorizing stages, giving ad-hoc direction, and authorizing closure. Producing Highlight Reports is for the PM during Controlling a Stage. Appointing the Project Manager is during Starting Up a Project.

The Lessons Report is produced during the Closing a Project process to capture lessons learned for future projects.

The Project Board uses the Directing a Project process throughout the project, including authorising closure. Closing a Project is the process that produces the recommendation, but the decision to close is taken by the Project Board via Directing a Project.

The Starting Up a Project (SU) process produces the Project Brief, which outlines the project's scope, objectives, and feasibility. The Initiating a Project (IP) process then uses that brief to develop the detailed Project Initiation Documentation (PID), which includes the Business Case, plans, and risk assessment. This distinction is fundamental because SU is a pre-project process to ensure there is a viable idea, while IP is the detailed planning phase that creates the management documents needed to proceed.

The Project Initiation Documentation (PID) is the definitive output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single baseline that defines 'what, why, who, when, and how' for the project. The PID is formally approved by the Project Board at the end of initiation, authorizing the project to proceed to the next stage.

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

The End Stage Report is produced during the Managing a Stage Boundary process to summarize the current stage's performance and inform the Project Board's decision to authorize the next stage.

The Initiating a Project process is where the project's scope, objectives, and approach are fully defined and documented. Its key output is the Project Initiation Documentation (PID), which consolidates all the baseline plans and strategies needed to justify and manage the project. The PID replaces the Project Brief, which is created earlier in the Starting Up a Project process.

When the Project Board authorizes a stage plan, the next process to execute is Controlling a Stage, where the Project Manager manages the work of that stage.

The Starting Up a Project (SU) process is designed to evaluate the project's viability by creating the Project Brief and checking if the project is worthwhile, while the Initiating a Project (IP) process focuses on establishing a solid management foundation by creating the Project Initiation Documentation (PID) and detailed plans for how the project will be managed and controlled.

In PRINCE2, the Project Board is responsible for authorising the start of a project. This occurs at the end of the Initiating a Project process, when the Project Board reviews the Project Initiation Documentation and gives approval to proceed with the project. The Project Board provides overall direction and control, ensuring the project aligns with business, user, and supplier interests.

The Team Manager must escalate the issue to the Project Manager promptly, as they cannot exceed Work Package tolerances without authorization. The Project Manager will then handle the escalation.

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 pre-project process, the project mandate is reviewed, and key roles are assigned to ensure the project has the necessary leadership and management before proceeding to the Initiation Stage.

According to PRINCE2, when an Off-specification is identified, the Project Manager must first log it in the Issue Register and assess its impact. This ensures that all issues are formally recorded and evaluated before any corrective action is taken, maintaining control over project baselines.

The Project Board authorises initiation, stage plans, and project closure. They do not create Work Packages (PM does) nor approve Checkpoint Reports (PM receives them).

The Project Manager uses the Controlling a Stage process to monitor progress, review Work Packages, and manage issues. Checkpoint Reports are received from Team Managers during CS.

The Managing Product Delivery process is designed to control the link between the Project Manager and the Team Manager(s) by ensuring that work on products is authorized, executed, and delivered according to the agreed quality criteria and acceptance requirements. Its primary purpose is to create and deliver the project's products to the specified quality standards, as defined in the Product Description and Work Package.

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

SB includes planning the next stage, updating the project plan, reporting on the current stage (End Stage Report), and capturing lessons. Authorizing Work Packages is done in CS, and delivering products is in MP.

During SU, the Executive and the Project Manager are appointed. The Project Board is also appointed, but the question asks for two specific roles. The Senior User and Senior Supplier are part of the Project Board but may be appointed later if not already in place.

Directing a Project is the process that covers the Project Board's decision-making and direction-giving activities throughout the project, including ad-hoc direction.

The first process in PRINCE2 is 'Starting Up a Project' (SU). This process occurs before the project is formally initiated and is designed to ensure that the project has a viable business justification, a clear project mandate, and that the necessary people and resources are available to proceed. It produces the Project Brief and the Initiation Stage Plan, which are essential inputs for the 'Initiating a Project' process.

CP includes handing over products, producing the End Project Report, and recommending closure. Authorizing closure is done by the Board in DP; authorizing Work Packages is done in CS.

The Lessons Report is produced during CP to document lessons for future benefit. The End Project Report also includes lessons, but the specific document for lessons is the Lessons Report.

The PRINCE2 Controlling a Stage process requires the Project Manager to first assess any deviation from the stage plan to see if corrective action can bring performance back within tolerance. The Checkpoint Report is a control mechanism that triggers an exception assessment, not an immediate escalation. Only if the deviation exceeds tolerance should the Project Manager escalate via an Exception Report.

The End Stage Report and next Stage Plan are produced; the Project Board then decides in DP.

The work package is complete but the actual cost exceeds the planned cost by $5,000, which exceeds the tolerance set for the work package. In PRINCE2, any deviation beyond the agreed tolerance must be escalated to the Project Board as an exception, as the Project Manager cannot approve such variances themselves.

The Closing a Project process in PRINCE2 is designed to provide a fixed point to verify that the project has delivered its products according to the agreed scope, confirm that the project's objectives have been met, and then formally close the project in a controlled manner. This includes handing over the products to the operational environment, completing any follow-on actions, and preparing the End Project Report. It does not wait for benefits realization, as benefits are assessed post-project during the Managing Product Delivery stage.

The Starting Up a Project process ensures that the prerequisites for initiating a project are in place, such as having a viable project idea and an appointed Executive and Project Manager. It answers the question 'Do we have a viable and worthwhile project?' before proceeding to initiation.

Directing a Project includes giving ad-hoc direction as one of its key activities.

The PM should assess the impact on the stage and take corrective action within the stage tolerance. If tolerance is threatened, then escalate.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, which establishes the solid foundation for the project.

According to PRINCE2, when a project manager forecasts that stage costs will exceed the agreed stage tolerance, the first action is to raise an Exception Report to the Project Board. This is because the project manager must escalate the deviation immediately, as they do not have authority to exceed tolerance without board approval. The Exception Report informs the board of the situation and options, allowing them to decide on corrective action.

The Directing a Project process is used by the Project Board to make key decisions and exercise overall control, including authorizing the initiation of the project. The Project Board does not manage day-to-day work; that is the responsibility of the Project Manager via the Managing a Stage process.

The Project Board authorizes the next stage as part of Directing a Project, based on the End Stage Report and next Stage Plan from SB.

The Project Manager authorises a Work Package to assign work to the Team Manager.

The Exception Plan is produced by the Project Manager within the Managing a Stage Boundary process. This process is triggered when the Project Board authorizes an Exception Plan to replace the current Stage Plan due to a deviation beyond tolerance. The Project Manager then creates the Exception Plan and submits it for approval.

In PRINCE2, the Closing a Project process requires the End Project Report and the Lessons Report to be produced before the Project Board can authorize project closure. The End Project Report provides a summary of the project's performance against its planned objectives, while the Lessons Report captures lessons learned for future projects. These two reports together form the basis for the Project Board's decision to formally close the project.

Directing a Project is the process by which the Project Board makes key decisions, including authorizing initiation. Starting Up a Project is a pre-project process that does not involve authorization.

The End Stage Report summarizes performance of the current stage and includes a recommendation for the next stage. The Project Board then decides whether to authorize the next stage.

CP produces the End Project Report, Lessons Report, and project closure recommendation. The Project Plan is updated in SB, and the Business Case is updated throughout.

SU ensures that the project has a viable Business Case and that the necessary people are appointed before committing to the full initiation effort.

The Project Manager in Controlling a Stage authorises Work Packages, monitors progress, and reports to the Project Board via Highlight Reports. The Project Board authorises stage plans, and the Team Manager produces Checkpoint Reports.

In PRINCE2, the Managing Product Delivery process is where the Team Manager executes the work defined in a Work Package. The Team Manager accepts the Work Package from the Project Manager (Option B) and then delivers the products, sending Checkpoint Reports to the Project Manager (Option D) to report progress. These two activities are core responsibilities within this process.

SU is a pre-project process that ensures the project is viable before committing to full initiation. IP formally establishes the project and produces the PID.

If the deviation is within stage tolerance, corrective action can be taken by the Project Manager without escalation. The Project Manager should take corrective action to bring the work back on track.

Directing a Project is the process by which the Project Board provides overall direction and control, making key decisions and authorizing initiation, stages, and closure.

The Project Manager is appointed during the Starting Up a Project process, as part of preparing for initiation.

The Project Board decides whether to authorize an Exception Plan during the Directing a Project process. This process covers the Project Board's decision-making responsibilities, including reviewing and approving exception plans when a stage is forecast to exceed its tolerances. The board either approves the exception plan, allowing the project to continue, or requests alternatives.

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.

The Project Manager is responsible for producing the Lessons Report at the end of the project. This is because the Project Manager owns the day-to-day management of the project and is best positioned to capture and document lessons learned from the project's execution, ensuring that knowledge is transferred for future projects.