CCNA Prince2 Processes Questions

The Starting Up a Project process ensures that the prerequisites for initiating a project are in place by answering whether the project is viable and worthwhile, and whether the necessary people are available to proceed.

The Highlight Report is a periodic report from the Project Manager to the Project Board summarising progress within a stage.

Starting Up a Project (SU) is the pre-project process that produces the Project Brief and initiation Stage Plan, enabling the Project Board to decide whether to proceed with initiation.

Managing Product Delivery focuses on the team delivering products according to the Work Package requirements. It ensures that work is accepted, executed, and delivered to the required quality.

Managing a Stage Boundary provides the Project Board with information needed to review the current stage and decide whether to authorise the next stage.

The PID and the Benefits Management Approach are key outputs of IP. The Project Brief is from SU, and the Work Package is from CS or MP.

DP enables the Project Board to make key decisions and provide overall direction throughout the project.

The Project Brief is created in SU and provides the basis for the initiation stage.

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

The Executive (Senior Responsible Owner) owns the Business Case and ensures its ongoing viability.

Option A is correct because the Project Manager is responsible for reporting Highlights to the Project Board during the Controlling a Stage process. This is a mandatory management product defined in PRINCE2, providing a summary of progress, achievements, and exceptions at intervals specified in the Stage Plan.

The PID includes the Project Plan, Business Case, and Risk Management Approach. The Daily Log is a project log used throughout, not part of PID. The Checkpoint Report is a product of Managing Product Delivery.

The Highlight Report is the correct choice because it is the PRINCE2 management product used to provide the Project Board with a summary of progress at regular intervals during a stage. Since the stage is on track and no issues or deviations require escalation, the Project Manager should send a Highlight Report to keep the Board informed, not an Exception or End Stage Report.

Closing a Project includes producing the End Project Report, Lessons Report, and confirming benefits review arrangements.

SU is a pre-project process to determine if the project is viable before committing resources to full initiation; IP formally establishes the project's foundations and produces the PID.

Authorizing Work Packages, reviewing progress, and managing risks and issues are key activities of Controlling a Stage. Producing the End Stage Report is done in Managing a Stage Boundary, and producing the Project Plan is done in Initiating a Project.

Option C is correct because, according to PRINCE2, when a Team Manager reports a work package as complete, the Project Manager must first accept the completed work package and then update the stage plan to reflect the actual progress. This ensures the stage plan remains accurate and provides a basis for assessing the impact on the project plan and any necessary corrective actions.

The Project Manager should contact the Team Manager to understand the situation and take corrective action. This is part of the 'Review Work Package Status' activity in Controlling a Stage.

The Benefits Management Approach is produced during the Initiating a Project process because it defines how the project's benefits will be measured, managed, and realized. This document is created as part of the detailed planning and governance setup that occurs in this process, ensuring alignment with the business case.

In PRINCE2, the Highlight Report is a management product that is prepared by the Project Manager and sent to the Project Board. The purpose of the Highlight Report is to provide the Project Board with a summary of the project's progress at intervals defined in the Communication Management Strategy. Therefore, the statement that the Project Manager receives a Highlight Report from the Project Board is incorrect; the flow is from the Project Manager to the Project Board.

The Starting Up a Project (SU) process is designed to ensure that the project has a viable business justification and is worthwhile before committing significant resources. It answers the question 'Do we have a viable and worthwhile project?' by creating the Project Brief and selecting the Project Manager, not by producing detailed plans or the PID.

The PID is the key output of Initiating a Project, which establishes solid foundations for the project.

Option A is correct because preparing the Project Plan is a key activity in the Initiating a Project process, where the detailed plan for the project is developed based on the Project Brief and the chosen strategy. This plan covers time, cost, quality, and scope, and is a core component of the Project Initiation Documentation (PID).

Risks are managed by the Project Manager. The risk should be added to the Risk Register and monitored. The Highlight Report is for reporting current stage progress; the risk can be mentioned but the immediate action is to record it.

The Managing a Stage Boundary process is where the Project Manager reviews the current stage, produces an End Stage Report, and creates the next Stage Plan (or Exception Plan) for the Project Board's approval.

In PRINCE2, the first formal recording of lessons occurs during the 'Starting Up a Project' process. This process includes the activity 'Capture Previous Lessons' (from the 'Learn from Experience' principle), where the project manager reviews lessons from similar previous projects and records them in the Lessons Log before the project is even initiated. This ensures that the project starts with the benefit of past experience.

According to PRINCE2, the Executive appoints the project manager during SU. The Executive is the key decision-maker for this appointment.

The PID and Benefits Management Approach are both produced in IP. The Project Brief is from SU, and the End Stage Report is from SB.

The Starting Up a Project process is the first process in PRINCE2, executed before project initiation. Its key output is the Project Brief, which provides a high-level overview of the project's justification, scope, and approach, enabling the project board to decide whether to proceed to the Initiation Stage. The Project Brief is derived from the project mandate and is used to create the Project Initiation Documentation later.

The Project Brief and the Initiation Stage Plan are outputs of SU. The PID is output of IP. The End Stage Report is output of SB.

The Team Manager should raise an issue (or off-specification) to the Project Manager via the MP process. The Project Manager will then decide on corrective action or escalation.

SU produces the Project Brief and the Initiation Stage Plan. The PID and End Project Report are produced later.

The Initiating a Project process is where the project's baselines are established, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—such as the Business Case, project plan, risk register, and project controls—into a single, approved document that defines what the project will deliver and how it will be managed. This document is the foundation for decision-making and is used throughout the project.

The Project Manager produces Highlight Reports and sends them to the Project Board during Controlling a Stage.

The Controlling a Stage (CS) process covers the day-to-day management activities of the Project Manager within a stage.

The Project Initiation Documentation (PID) is the key output of Initiating a Project. It brings together all the information needed to justify the project and define its scope.

The Project Board reviews stage-end reports and decides whether to authorize the next stage. This is part of Directing a Project (DP). The PM produces the End Stage Report and next Stage Plan during Managing a Stage Boundary (SB).

The Project Manager authorizes work by issuing a Work Package to the Team Manager.

In PRINCE2, the Project Board is collectively responsible for authorizing the initiation of a project. This decision is made during the 'Starting Up a Project' process, where the Project Board reviews the Project Brief and decides whether to proceed to the Initiation Stage. The Project Board's authority is derived from the corporate or programme management, but the actual authorization to initiate is a board-level responsibility.

The PM authorizes Work Packages, monitors progress, and manages issues and risks. Producing the next stage plan is done in SB, and producing the Project Plan is done in IP.

DP is performed by the Project Board and runs throughout the project. The Project Board gives direction and authorizes key decisions but does not manage day-to-day. The PM manages day-to-day in CS.

SU produces the Project Brief, the initiation stage plan, and the Daily Log. The PID is an output of IP, and the Benefits Management Approach is an output of IP.

The Project Board is responsible for overall project governance, including authorizing the Project Plan (which defines the project's scope, cost, and schedule) and authorizing the start of each management stage. These decisions ensure the project remains aligned with business objectives and that stage boundaries are properly controlled.

According to PRINCE2, if a product fails its quality inspection, the Team Manager should raise an Issue Report (specifically, an Off-specification) to the Project Manager. The PM then decides how to handle it. Option D is correct; Option B is wrong because the Team Manager should not bypass the PM.

SU produces the Project Brief, Daily Log, and Initiation Stage Plan. PID is from IP.

Option B is correct. Benefits Management Approach is created during Initiating a Project as part of the PID.

Directing a Project (DP) is the process used by the Project Board to authorize initiation, stage plans, exception plans, and closure.

The Project Manager uses the Controlling a Stage process to monitor progress, review Highlight Reports, and report to the Project Board via Highlight Reports.

The Lessons Report is produced during CP to document what went well and what could be improved, for the benefit of future projects.

The Project Board (in the Directing a Project process) is responsible for authorising project initiation, as well as authorising the project itself.

The Team Manager produces Checkpoint Reports at intervals defined in the Work Package. These reports inform the Project Manager of progress against the Work Package.

Checkpoint Reports are produced within Managing Product Delivery (MP) by the Team Manager.

The Lessons Report is used to inform future projects and improve organizational project management. It should be shared with the relevant stakeholders and added to the organizational lessons database. It is not just filed or destroyed.

SU is a pre-project process to determine if the project is viable and worth initiating, while IP formally establishes the project foundation with detailed plans.

Controlling a Stage is the process for managing day-to-day work within a stage, including the first stage.

Managing Product Delivery is the process where Team Managers accept Work Packages, execute them, and deliver products. Checkpoint Reports are produced by Team Managers for the Project Manager. Highlight Reports are produced by the PM, and End Stage Reports are produced in Managing a Stage Boundary.

The Initiating a Project process produces the Project Initiation Documentation (PID), which is the definitive document that defines the project's scope, objectives, and approach. It also produces the Stage Plan for the next stage, which details the work, resources, and controls for the first management stage. These are mandatory outputs that enable the Project Board to authorize the project to proceed.

Checkpoint Reports are produced by the Team Manager (or the team) to inform the Project Manager of progress on Work Packages. The Project Manager receives them, not the Project Board. Option B is correct.

The Project Board, through the Directing a Project process, approves the End Project Report and authorizes project closure.

The Project Initiation Documentation (PID) is the key output of Initiating a Project. It provides the foundation for project management and includes the Project Plan, Business Case, and management approaches.

The Exception Plan is prepared by the Project Manager in the Managing a Stage Boundary process when a stage is forecast to exceed its tolerances. This process allows the Project Manager to present options to the Project Board, including an Exception Plan to replace the current stage plan, ensuring continued control within agreed tolerances.

Option A is correct because the Project Board must authorize initiation to allow the project to proceed from the Starting Up a Project process into the Initiation Stage. This formal approval ensures that sufficient resources are committed and that the project aligns with corporate or programme strategy before detailed planning begins.

Option A is correct because the Managing Product Delivery process is where the Project Manager assigns work packages to Team Managers. This process focuses on the acceptance, execution, and delivery of work packages, ensuring that the team manager receives clear requirements and acceptance criteria. It bridges the gap between the Project Manager's planning and the team's execution.

Option C is correct because evaluating the project and documenting lessons learned is a key activity in the Closing a Project process, as it captures knowledge for future projects. Option D is correct because preparing the End Project Report is also a mandatory activity in this process, providing a final assessment of project performance against the business case and plans.

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager to report progress on Work Packages.

The Directing a Project process is the Project Board’s process, which includes authorising initiation, the project itself, stage plans, and closure.

Starting Up a Project is a pre-project process to ensure that the project has a viable Business Case and that the necessary resources and people are in place before initiation. It does not approve, close, or monitor the project.

Checkpoint Reports provide progress information on Work Packages. The Project Manager uses them to review progress, update the stage status, and produce the Highlight Report for the Project Board. Option C is correct.

Checkpoint Reports are produced by the Team Manager (or the person managing the Work Package) and are sent to the Project Manager. They provide progress on the Work Package.

The Project Initiation Documentation (PID) is the key output of IP, providing the foundation for the project.