CCNA Prince2 Processes Questions

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports on a frequency defined in the Work Package. These reports provide the Project Manager with progress updates on the team's work, including actual vs. planned achievements, quality activities, and any issues or risks. The Team Manager is the role that directly manages the team's day-to-day work and thus is best positioned to compile this detailed progress information.

When the Project Board rejects the Stage Plan during the Managing a Stage Boundary process, the project cannot proceed as intended. PRINCE2 requires the Project Manager to issue an Exception Report to the Project Board, recommending project closure if the plan is not approved, because the project has no authorized plan to continue and the board must decide whether to close or take alternative action.

The Managing a Stage Boundary process produces the End Stage Report, updated Project Plan, and the next Stage Plan (or Exception Plan).

In the Directing a Project process, the Project Board is responsible for reviewing the Stage End Report and deciding whether to authorize the next Stage Plan. This is the formal activity that occurs when a stage is complete, ensuring that the project remains viable and aligned with business justification before proceeding. The correct answer is A because the board must approve the plan for the next stage to continue.

The Managing a Stage Boundary process produces the End Stage Report and the next Stage Plan, which the Project Board uses to decide whether to continue.

PRINCE2 mandates that when a stage's forecast exceeds its tolerance (here, 10% above $200,000 = $220,000, and the new cost is $230,000), the project manager must raise an Exception Report to the project board. The board, comprising the executive, senior user, and senior supplier, then decides on corrective actions—such as approving additional budget, renegotiating scope, or stopping the project. The project manager cannot unilaterally approve the overrun or bypass the board.

The Change Control Approach defines how changes to baselined products are managed, including the change control procedure.

The PM must first record the issue in the Issue Register and then decide on the appropriate response. If the issue could breach tolerances, an Exception Report is needed, but the immediate step is to log it.

DP is the process by which the Project Board authorizes key decisions and provides overall direction, but does not manage day-to-day activities.

Checkpoint Reports are produced by the Team Manager in Managing Product Delivery and reviewed by the Project Manager in Controlling a Stage.

SU is a pre-project process to determine if the project is viable; IP formally establishes the project by creating the PID.

The PID includes the Project Plan, Business Case, and Risk Management Approach. The Daily Log is an ongoing log, and the Lessons Report is produced in Closing a Project.

The Project Manager produces the End Project Report as part of the Closing a Project process.

The Starting Up a Project process produces the Project Brief, which provides a high-level overview of the project's justification, scope, and approach. It also produces the Initiation Stage Plan, which details the activities and resources needed for the initiation stage, and the Daily Log, which records informal issues and actions. These outputs are created before the project board authorizes initiation.

Directing a Project includes the activity 'Authorize Initiation' and later 'Authorize the Project' to formally start the project.

The PID is the single most important output of IP, providing the foundation for the project.

SU is a pre-project process to decide if the project is viable; IP formally establishes the project and produces the PID.

Managing Product Delivery is the process of accepting, executing, and delivering Work Packages. It ensures that products are created to the required quality standards.

Directing a Project includes the activity 'Authorise Initiation' where the Project Board reviews the Project Brief and decides whether to allow initiation. Starting Up a Project prepares the Project Brief but does not authorise initiation.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot ignore the issue or update the plan without authorisation. Closing the project is premature.

The purpose of Closing a Project is to provide a fixed point to verify that the project has achieved its objectives, hand over products, confirm benefits review arrangements, and release resources. Starting Up a Project is to ensure basic conditions exist; Initiating a Project establishes the project; Managing a Stage Boundary plans the next stage.

The Project Manager is responsible for ensuring that the project's products meet their quality criteria before acceptance. They oversee quality control activities and review product verification, while the Senior User is responsible for acceptance of the final products, not for ensuring quality criteria are met beforehand.

The Initiating a Project process is where the Project Initiation Documentation (PID) is produced. The PID consolidates key planning information, including the detailed business case, project plan, and risk register, to form a solid foundation for the project. This process ensures that all stakeholders have a shared understanding of the project's scope, objectives, and approach before proceeding.

CS focuses on day-to-day management, including authorising work packages and taking corrective action. Producing the Project Initiation Documentation is done in IP, and producing the End Project Report is done in CP.

Managing a Stage Boundary includes capturing lessons learned as part of the End Stage Report.

In PRINCE2, the Controlling a Stage process is responsible for authorizing Work Packages. This process manages the day-to-day activities within a stage, including assigning work to teams and ensuring it is completed according to the agreed tolerances. The Project Manager uses this process to issue Work Packages to the team manager or team members, formally delegating the work defined in the Stage Plan.

The End Stage Report is produced during the Managing a Stage Boundary process to provide a formal summary of the stage's actual performance against the approved Stage Plan. Its primary purpose is to give the Project Board the information needed to review the completed stage and decide whether to authorize the next stage, including updated Business Case and project plan information. Option D correctly captures this dual purpose of reporting on the completed stage and seeking approval to proceed.

Checkpoint Reports are produced by the Team Manager for the Project Manager during Managing Product Delivery. Highlight Reports are produced by the Project Manager for the Project Board during Controlling a Stage. They serve different audiences and have different frequencies.

The Managing Product Delivery process is designed to control the interface between the Project Manager and the Team Manager. Its purpose is to accept, execute, and deliver work packages, ensuring that the work is done according to the agreed criteria and that the completed products are handed back to the Project Manager. This process focuses on the team's work and the delivery of products, not on the Project Manager's day-to-day activities.

The Daily Log is first created as an output of the Starting Up a Project process. This process establishes the project's initial records, including the Daily Log, to capture informal issues, observations, and lessons from the very beginning of the project lifecycle.

The Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress information on the work package assigned to the team, including achievements, next steps, and any issues or risks. This aligns with PRINCE2's principle of management by exception, where the Team Manager reports at intervals defined in the Work Package.

The Exception Plan is produced during the Managing a Stage Boundary process because this process is triggered when a stage is forecast to exceed its tolerances. The Project Manager creates the Exception Plan to replace the current Stage Plan and submit it to the Project Board for approval, ensuring continued control over the project.

The Project Board is responsible for ensuring that project assurance is independent of the Project Manager. This is because the Project Board provides overall governance and oversight, and project assurance is a key function that must be objective and separate from the day-to-day management activities of the Project Manager. The PRINCE2 principle of 'defined roles and responsibilities' explicitly assigns this accountability to the Project Board to maintain the integrity of the assurance function.

SU is a pre-project process to determine if the project is viable before committing to detailed planning. IP formally establishes the project foundation and produces the PID. Key difference: SU decides whether to proceed; IP creates the detailed plans and strategies.

When a stage tolerance is forecast to be exceeded, the PM produces an Exception Report (part of Controlling a Stage) and then the Board decides, but the escalation itself occurs within CS. However, the process for creating an Exception Plan is SB. The escalation step is part of CS.

A Request for Change (RFC) is a formal proposal to modify a baseline product or process, while an Off-specification (Off-spec) is a product that has been identified as not meeting its agreed specification. In PRINCE2, both are types of issues, but an RFC seeks a change to the specification itself, whereas an Off-spec indicates a deviation from the existing specification that must be resolved.

The End Project Report is the key document in Closing a Project that confirms the project's deliverables and performance against the original PID. It also includes lessons and a summary of benefits reviews.

The Project Board is responsible for authorizing the initiation of the project during the Directing a Project process. This authorization formally allows the Project Manager to proceed with the Initiation Stage, committing resources and funding. It is a key decision point that ensures the project aligns with corporate or programme strategy before detailed planning begins.

IP produces the PID, which includes the Project Plan, Business Case, and various management approaches. The Project Brief and End Stage Report are not outputs of IP.

Managing Product Delivery is the process where Team Managers accept, execute, and deliver Work Packages, reporting progress via Checkpoint Reports.

CS includes authorizing Work Packages, reviewing progress, and reporting. Producing the PID is done in IP.

If project-level tolerance is forecast to be exceeded, an Exception Plan is required instead of a normal Stage Plan. The Exception Plan must be approved by the Project Board.

In the Closing a Project process, the Project Manager is responsible for producing the End Project Report. This report summarizes the project's performance against the original Business Case, including whether the project achieved its objectives and delivered the expected benefits. It also provides information for the post-project Benefits Review Plan.

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 essential information—including the Business Case, project plan, risk register, and controls—into a single, comprehensive document that defines what the project will deliver, why, and how it will be managed. This makes it the definitive reference for project governance and the baseline against which progress is measured.

The Directing a Project (DP) process includes the activity of giving ad-hoc direction to the Project Manager as needed.

If a Team Manager forecasts that a Work Package tolerance will be exceeded, they must escalate to the Project Manager via an Issue Report. The Project Manager then decides how to proceed.

In PRINCE2, management by exception means the Project Manager must escalate to the Project Board when a stage tolerance is forecast to be exceeded. The correct action is to raise an Exception Report.

The Directing a Project process is designed to enable the Project Board to make key decisions and exercise overall control over the project. It covers the project's lifecycle from initiation through closure, ensuring that the board authorizes each stage, reviews progress, and provides strategic direction without getting involved in day-to-day management.

Issues that threaten tolerances or require changes to baselines should be escalated. The PM manages issues within their authority.

Options A, D, and E are correct. The Project Initiation Documentation (PID) includes the Project Plan, Risk Management Approach, and Business Case. The Highlight Report is a product of the Controlling a Stage process, and the Checkpoint Report is a product of the Managing Product Delivery process.

The Project Manager is responsible for reviewing progress against the stage plan and taking corrective action when deviations occur, as defined in the Controlling a Stage process. This ensures the stage remains within tolerance and aligns with the project plan.

The Checkpoint Report is a progress report on the work completed within a Work Package during a specific period. According to PRINCE2, the Team Manager is responsible for producing the Checkpoint Report to inform the Project Manager of progress against the Work Package plan.

In PRINCE2, the Project Board is responsible for authorizing the initiation of a project. This occurs at the end of the Starting Up a Project process, when the Project Board reviews the Project Brief and decides whether to proceed with the Initiation Stage. The Project Board's authority is defined in the project's governance framework, and it must formally approve the initiation plan before the Project Manager can begin detailed planning.

In the Controlling a Stage process, after a Team Manager reports that a product is complete, the Project Manager must first review the product to confirm it meets the quality criteria defined in the Product Description. This is part of the 'Review Work Package' activity, ensuring that the product is fit for purpose before any further actions, such as reporting or planning, occur. Only after this quality check can the Project Manager proceed to other activities like updating logs or sending reports.

The Project Board must authorize project closure through the Directing a Project process. The PM prepares the recommendation, but only the Board can formally close.

The primary purpose of the End Stage Report in the Managing a Stage Boundary process is to provide the Project Board with a summary of the stage's performance against the plan, including progress, issues, and risks, so they can make an informed decision on whether to authorize the next stage. This aligns with PRINCE2's principle of management by stages, where the board reviews stage-end information to confirm continued business justification.

SU is a pre-project process to check viability; IP is the full initiation to establish the project on a solid foundation, creating the PID.

In PRINCE2, an Exception Plan is triggered when a stage tolerance is forecast to be exceeded. The Project Board authorizes this plan to address the deviation and keep the project on track. This is a key control mechanism within the Directing a Project process.

The Project Board authorizes initiation, authorizes stage plans, and gives ad-hoc direction. Producing Highlight Reports and managing day-to-day issues are PM/CM responsibilities.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress updates on work packages, including actual versus planned progress, quality activities, and any issues or risks. The Team Manager is the role that manages the day-to-day work of the team and reports back to the Project Manager.

The Project Initiation Documentation (PID) is produced during the Initiating a Project process. This process refines the project's business justification, establishes the project management team, and creates the PID as the definitive reference document for how the project will be managed, including plans, controls, and tolerances.

In the Managing a Stage Boundary process, the Project Manager produces an End Stage Report to summarize the current stage's performance. The PRINCE2 method requires that a Stage Plan for the next stage must also be produced during this process, as it provides the detailed plan for the upcoming work and is essential for the Project Board to authorize the next stage. Without the next Stage Plan, the project cannot proceed beyond the current stage boundary.

The Starting Up a Project process ensures that the prerequisites for initiating a project are in place, such as having a Project Brief and approved initiation stage plan. It does not produce the PID or manage delivery.

Directing a Project (DP) is the process by which the Project Board authorises project closure. The Project Manager prepares the closure recommendation in Closing a Project, but the Board gives the final authorisation.

The Starting Up a Project (SU) process appoints the Executive and Project Manager before formal initiation begins.

The primary difference is that Starting Up a Project (SU) is a pre-project process performed before the Project Board authorizes initiation, while Initiating a Project (IP) is the first process after the Project Board gives authorization. SU ensures the project is viable and creates the Project Brief, whereas IP develops the detailed Project Plan and Business Case for the Project Board's approval.