CCNA Prince2 Processes Questions

According to PRINCE2's management by exception, if a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot unilaterally change the plan.

Option A is correct because the Project Board is responsible for approving Stage Plans and any updates to them during the Directing a Project process. This ensures that the project remains aligned with the business case and that management stage boundaries are properly controlled.

The Team Manager should first record the quality problem as an issue and escalate it to the Project Manager, who will decide how to handle it. The Team Manager cannot unilaterally change the product or stop work without authorization.

Controlling a Stage (CS) is where the PM authorizes Work Packages, monitors progress, and takes corrective action.

Closing a Project ensures controlled closure, including handover of products, confirmation of benefits review arrangements, and release of resources.

The Closing a Project process produces the End Project Report, which assesses how the project performed against its plan and justifies closure.

Starting Up a Project produces the Project Brief, Initiation Stage Plan, and Daily Log. PID and Benefits Management Approach are from Initiating a Project. End Stage Report is from Managing a Stage Boundary.

Closing a Project ensures a controlled closure, handover of products, evaluation of the project, and recommendations for future projects.

If a product cannot meet its quality criteria, the Team Manager must escalate the issue to the Project Manager as an issue, following the issue and change control procedure.

The End Project Report and the Lessons Report are both produced in CP. The Project Brief is from SU, the PID from IP, and the Stage Plan from SB.

Directing a Project is the process where the Project Board makes key decisions, including authorizing initiation, stage plans, exception plans, and project closure.

The End Stage Report is produced during Managing a Stage Boundary (SB) to report on the current stage's performance and plan the next.

Directing a Project includes the activity 'Giving ad hoc direction' to allow the Project Board to provide guidance or decisions outside of formal stage boundaries.

In Controlling a Stage, the Project Manager authorizes Work Packages, but the authorization to proceed with the stage comes from the Project Board via Directing a Project.

Directing a Project is the process that covers the Project Board's activities: authorising initiation, project, stages, exception plans, and closure. The Project Board does not manage day-to-day work.

The Starting Up a Project process is designed to evaluate the project mandate and determine whether the project is viable and worthwhile before committing significant resources to full initiation. It ensures that the project has a clear business justification, a defined project manager, and a sufficient understanding of scope and risks to proceed. This process does not produce detailed plans or the Project Initiation Documentation (PID), which are outputs of the Initiating a Project process.

Closing a Project is the process for controlled closure, including handover, benefits review planning, and project closure recommendation.

Configuration management: identify, control changes, record status, verify, and report.

The PM should first assess whether this is an issue that can be resolved within the stage's tolerances. If it cannot, an escalation is needed. But initially, corrective action within CS is appropriate.

The Quality Management Approach is one of the management approaches produced in IP, defining quality procedures and standards.

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

The Project Manager authorizes Work Packages during the Controlling a Stage process.

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

All changes must be logged in the Issue Register before analysis. The Project Manager then assesses the impact and may escalate to the Project Board if it affects tolerances.

The Initiating a Project process produces the Project Plan (Option E) and the Risk Management Approach (Option D). The Project Plan defines the baseline for scope, schedule, and cost, while the Risk Management Approach establishes the procedures for identifying, assessing, and controlling risks throughout the project. Both are formal management products created during initiation to guide project execution.

End Stage Reports are produced during the Managing a Stage Boundary process, which also plans the next stage and updates the project plan.

The Project Board makes decisions on Exception Plans as part of the Directing a Project process, specifically through the activity 'Authorize a Stage or Exception Plan'.

The PID includes the Project Plan, Business Case, and various management approaches. Checkpoint Reports are from MP, End Stage Report from SB, Lessons Report from CP.

If a Checkpoint Report indicates a deviation within stage tolerances, the PM can take corrective action themselves. If it threatens stage tolerance, they must escalate.

The Business Case is initially outlined in Starting Up a Project and fully developed in Initiating a Project, where it becomes part of the PID. It is then reviewed and updated at each stage boundary (Managing a Stage Boundary) and at project closure.

Closing a Project ensures controlled closure, product handover, and lessons learned.

The Directing a Project process is where the Project Board authorizes the initiation of a project, authorizes stage plans, and authorizes the project closure. The Initiating a Project process includes the key authorization of the Project Initiation Documentation (PID) by the Project Board, which formally authorizes the project to proceed. Both processes involve the Project Board making critical go/no-go decisions that control the project's lifecycle.

The 'Directing a Project' process covers the Project Board's decision-making responsibilities, including providing ad-hoc direction to the Project Manager. This process runs from project initiation to closure and is the only process where the Board gives unplanned guidance outside of stage boundaries.

The End Project Report provides a final assessment of project performance against the PID, and is used to evaluate project success and inform future projects.

The Project Board, as part of the Directing a Project process, authorizes the initiation stage. The Executive chairs the Board but authorization is a Board decision.

Closing a Project ensures controlled closure, handover of products, and confirmation of benefits review arrangements.

Options A and D are correct. DP includes authorizing initiation and authorizing the project. Managing product delivery is MP; escalating issues is part of CS (PM role).

The Initiating a Project process produces the Project Initiation Documentation (PID), which includes the Project Plan, Business Case, and various management approaches. The Project Brief is an output of SU, and the End Stage Report is from SB.

Option A is correct. The Project Manager authorizes Work Packages in Controlling a Stage.

The Project Board authorises initiation, gives ad-hoc direction, and authorises closure. Producing Highlight Reports is a Project Manager responsibility, and managing day-to-day work is a Team Manager responsibility.

The project manager should use the Controlling a Stage process because it is specifically designed to monitor the day-to-day work of the stage, manage issues and risks, and take corrective action to keep the stage on track. The symptom of frequent re-prioritization and loss of focus indicates a lack of control within the current stage, which this process directly addresses by providing mechanisms for work package assignment, progress monitoring, and escalation. It ensures the stage remains within tolerance and that the team's efforts are aligned with the stage plan.

CS includes activities like authorizing Work Packages, managing issues, and reviewing progress. Closing the project is CP; creating the Project Plan is IP.

The purpose of Closing a Project is to provide a fixed point to verify that all project products have been accepted, confirm that the project has met its objectives, and recommend project closure.

The Directing a Project process is specifically designed for the Project Board to provide overall direction and control, including making key decisions and issuing ad-hoc instructions outside of the regular stage management cycle. It covers activities like authorizing initiation, stage plans, and project closure, as well as giving ad-hoc direction to the project manager when needed.

Starting Up a Project is a pre-project process to ensure that the project has a viable business justification and that the necessary people and resources are available before committing to the full initiation stage.

SB includes updating the Business Case and planning the next stage. Authorising Work Packages is done in CS, and delivering products is done in MP.

PRINCE2's management by exception requires escalation via an Exception Report when tolerances are forecast to be breached.

The Executive (Senior Responsible Owner) is accountable for the Business Case and ensuring its ongoing viability.