CCNA PRINCE2 Processes Questions

SU is a pre-project process to determine if there is a viable project, while IP formally establishes the project foundation with detailed planning and management strategies.

Reviewing progress against the stage plan is a key activity within Controlling a Stage, where the PM monitors and controls work.

SU outputs include the Project Brief, initiation Stage Plan, Daily Log, and appointment of the Executive and PM. The PID and Risk Register are outputs from IP.

According to PRINCE2, when a Stage Plan exceeds the agreed cost tolerance, the project board cannot approve it. Instead, the project manager must produce an Exception Plan that describes the options to bring the stage back within tolerance or to request a revised tolerance. This is a formal exception management process defined in the PRINCE2 manual.

When a stage tolerance is forecast to be exceeded, the Project Manager raises an Exception Report and then, if directed by the Project Board, produces an Exception Plan during Managing a Stage Boundary.

The Benefits Management Approach is created during the Initiating a Project process as part of the PID.

According to PRINCE2, when a team manager raises a technical difficulty that could result in a change, the project manager must first log it as an issue in the Issue Register. Only after logging and assessing the impact can the project manager decide on the appropriate response. Since the change does not affect the stage plan or business case, the project manager can handle it within the stage without escalating to the project board.

The Project Board authorizes the project, initiation, stage plans, and closure. Authorization is a key output of DP.

The End Project Report is produced during Closing a Project (CP) to summarize project performance and confirm closure.

Directing a Project (DP) is the process that covers the Project Board's activities from start to finish, including authorizing stages and closure.

Managing a Stage Boundary (SB) is the process where the PM plans the next stage and produces an End Stage Report.

Project Assurance provides independent oversight and is accountable to the Project Board. Project Support provides administrative services to the Project Manager.

The Starting Up a Project (SU) process occurs before the project is formally initiated, focusing on verifying the project's viability and creating the Project Brief. The Initiating a Project (IP) process then establishes the project's foundations by creating the Project Initiation Documentation (PID), which includes detailed plans and controls. Thus, the key difference is that SU is a pre-initiation process, while IP formally establishes the project's management foundation.

The Project Manager should assess the impact of the delay on the stage plan. If the deviation can be managed within stage tolerances, the PM will take corrective action. If tolerances are forecast to be exceeded, escalation is needed.

Option A is correct. Directing a Project is the process by which the Project Board provides ongoing direction and authorizes key decisions.

The End Stage Report is produced in the Managing a Stage Boundary process, which reviews the current stage and plans the next. The report is sent to the Project Board for a decision.

IP produces the PID, which includes the Risk Management Approach and Communication Management Approach. The Project Brief is from SU, and the End Stage Report is from SB.

SU produces the Project Brief and the Stage Plan for the initiation stage. The Daily Log is also created but not a formal output. The PID is from IP.

Starting Up a Project produces the Project Brief, initiation Stage Plan, and Daily Log. The Project Brief is a key output.

Closing a Project provides a controlled closure, ensuring that all products are handed over, the project is formally completed, and lessons are captured.

The Project Board uses Directing a Project to give ad-hoc direction, including responding to exception reports.

The Managing a Stage Boundary process is triggered at the end of each stage (except the final stage) to plan the next stage and produce an End Stage Report.

Option A is correct because the defect in version 2.1 of the User Authentication Module is a new issue that must be formally logged and managed within the current stage. PRINCE2 requires that all issues (including defects) be captured in the Issue Register and handled through the Controlling a Stage process, which includes assessing the impact, deciding on corrective action, and updating the Configuration Item Record (CIR) accordingly. The baseline remains 2.0 because version 2.1 is still under development and has not been baselined, so the defect does not trigger a baseline change request.

The End Project Report is produced during Closing a Project. It reviews the project's overall performance and confirms the project has met its objectives.

The End Stage Report provides the Project Board with information on the performance of the current stage so they can decide whether to authorize the next stage.

SU produces the Project Brief, Stage Plan for initiation, and Daily Log. The PID is produced in IP, and the End Project Report is produced in CP.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, consolidating all the management approaches and plans.

The Project Manager is responsible for producing the Highlight Report in PRINCE2. This report provides the Project Board with a summary of progress against the stage plan, including achievements, next steps, and any issues or risks. It is a key management product defined in the PRINCE2 manual, and its production is a specific responsibility of the Project Manager, not delegated to the Team Manager or others.

The End Stage Report provides a summary of the current stage's performance and the next stage plan for the Board to decide on continuation.

The End Stage Report is a management product that provides a summary of the stage's performance against the plan. When an Exception Plan has been used, the End Stage Report must include a summary of the issue that triggered the exception and the impact of the Exception Plan on the stage's objectives, budget, and schedule. This ensures that the Project Board has a complete picture of the stage's actual performance, including any deviations from the original Stage Plan.

Directing a Project includes authorising initiation, authorising the project, authorising stage/exception plans, giving ad-hoc direction, and authorising closure. Authorising a Work Package is done by the Project Manager in Controlling a Stage. Highlight Reports are produced by the Project Manager in Controlling a Stage.

The PID contains the Project Plan, which is a high-level plan for the entire project. Stage Plans are created in SB, not IP (except the first stage plan).

Managing Product Delivery is the PRINCE2 process that focuses on the work required to create the project's products and ensures they are delivered according to the agreed quality criteria. It is the process where the team manager accepts work packages, executes the work, and delivers completed products that meet the defined quality standards.

In Controlling a Stage, the PM authorises Work Packages to Team Managers for execution.

The Executive and Project Manager are appointed during SU, along with the Project Board members. The Team Manager is appointed later.

Option D is correct because PRINCE2 mandates that when a project manager forecasts a deviation beyond the stage tolerance, they must escalate the issue to the Project Board via an Exception Report. The Project Board then decides whether to approve an exception plan, adjust tolerance, or close the project. This ensures governance and control over the project's budget and scope.

The Starting Up a Project (SU) process is the pre-project process where the Executive and Project Manager are appointed. This ensures the necessary roles are in place before the project is formally initiated.

The Executive (Senior Responsible Owner) is responsible for the Business Case. The Project Manager maintains it day-to-day, but the Executive owns it.

The Executive (Senior Responsible Owner) is responsible for the Business Case. The Project Manager develops and maintains it, but ultimately the Executive owns it.

The Project Brief is the key output of SU. The PID is produced during IP.

Managing Product Delivery ensures that products are delivered according to the Work Package, meeting quality criteria.

The End Project Report includes confirmation of product acceptance and handover.

The Starting Up a Project (SU) process produces the Project Brief to provide a basis for deciding whether to proceed with the project.

Closing a Project (CP) is the process for controlled closure, handing over products and releasing resources.

The PID and the Benefits Management Approach are key outputs of IP. The Daily Log is created in SU. The End Project Report is from CP.

Managing Product Delivery (MP) is the process that covers the team manager's acceptance, execution, and delivery of work packages.

CS includes authorizing Work Packages, reviewing progress, and escalating issues. Planning the next stage is done in Managing a Stage Boundary. Authorizing the project is done in Directing a Project.

Since the risk is within stage tolerance, the Project Manager should manage it within the stage (e.g., by updating the risk register and taking corrective action) without escalating to the Project Board.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information—via the End Stage Report and the next Stage Plan—to review the current stage's performance, assess the continued viability of the project, and make an informed decision on whether to authorize the next stage. This process ensures that the project remains aligned with the business case and tolerances before proceeding.

Closing a Project ensures a controlled closure, including handing over products, evaluating the project, and recommending closure.

Highlight Reports are from PM to Project Board at a frequency defined in the Communication Management Approach; Checkpoint Reports are from Team Manager to PM at a frequency defined in the Work Package. Both can be written or verbal.

DP is the Project Board's process for making key decisions and giving direction. It runs throughout the project.

Directing a Project includes authorising stage plans (including exception plans) and project closure.

CS is the PM's process for managing the stage; MP is the Team Manager's process for delivering Work Packages. The PM authorizes Work Packages in CS, and the Team Manager delivers them in MP.

The Team Manager should inform the Project Manager via the Checkpoint Report or, if urgent, via an issue. The team manager does not directly escalate to the Board.

Starting Up a Project (SU) is the pre-project process that produces the Project Brief, which provides the outline business case and project approach needed to decide whether to proceed. Initiating a Project (IP) is the next process that produces the detailed Project Initiation Documentation (PID), including the full business case, project plan, and risk register, to establish a solid foundation for the project. The key difference is that SU creates the high-level justification and approach, while IP creates the comprehensive management documentation required for execution.

In PRINCE2, the Managing Product Delivery process focuses on the work required to create project products. The Team Manager's primary responsibility is to accept Work Packages from the Project Manager and then deliver them by coordinating the team's work, ensuring the products meet the required quality criteria. This directly aligns with option A, as accepting and delivering Work Packages is the core function of the Team Manager within this process.

SU produces the Project Brief, initiation Stage Plan, and Daily Log. The PID is produced in IP, and the Benefits Management Approach is also part of IP.

The Closing a Project process provides a controlled closure, including handing over products, evaluating the project, and recommending project closure.

Directing a Project (DP) is the process by which the Project Board authorizes initiation, authorizes the project, authorizes stage plans, and authorizes closure.

The Project Board authorizes initiation, gives ad-hoc direction, and authorizes closure. Managing day-to-day is the PM's role; producing Highlight Reports is the PM's role.

MP is the process where Team Managers accept, execute, and deliver Work Packages, ensuring products meet quality criteria and that work is controlled.

The Directing a Project process is responsible for authorizing the start of each stage because it provides the high-level governance and decision-making authority from the Project Board. This process ensures that the Project Manager receives explicit permission to proceed with the next stage, based on the Stage Plan and updated Business Case. Without this authorization, the project cannot move forward to the next stage.

Starting Up a Project produces the Project Brief and the Initiation Stage Plan. The PID is produced in Initiating a Project, and the End Project Report is produced in Closing a Project.

The PID is the key output that defines the project and forms the basis for management decisions.

Directing a Project enables the Project Board to make key decisions and provide overall direction without managing day-to-day activities.

Checkpoint Reports are prepared by the Team Manager and sent to the Project Manager.

When a stage tolerance is forecast to be exceeded, the PM must escalate to the Project Board via an Exception Report, following management by exception.