CC Learning - PRINCE2®, MSP™, ITIL®, MoR®, ISEB and PMI® training courses :: CS - Controlling a Stage - Quiz

Controlling a Stage drives Managing Product Delivery

All of Controlling a Stage is used in a time-driven manner

→

Controlling a Stage is the process that describes the day-to-day work of the Project Manager in handling the project stage. All of Controlling a Stage may be used in an event-driven manner. To read more on the context in which Controlling a Stage is used, see page 96 of the PRINCE2 Manual.

In Controlling a Stage, the Stage Plan is updated with actuals and progress is checked against the plan

The Project Manager uses the process Controlling a Stage to manage any deviations from Stage or Project Plans.

Identifying the key products that the project will deliver

→

Identification of the products to be delivered by the project is a key activity of the process Initiating a Project. The objectives of the process Controlling a Stage are found on page 97 of the PRINCE2 Manual.

Manage any deviations from Stage or Project Plans

Manage on-time delivery of products within agreed tolerances

Ensure that quality is achieved as planned.

Monitoring the work that is being carried out

Monitoring the status of resources

Updating Business Case

→

The Business Case is revised or updated for each End Stage Report with information from the stage that is closing and the next stage's plan, using the process Updating a Business Case (SB3). The key activities of Assessing Progress (CS2) can be found on page 103 of the PRINCE2 Manual.

Updating the Stage Plans with actuals.

The sub-process Assessing Progress (CS2) requires the Project Manager to submit Checkpoint Reports to the Executive at pre-determined intervals

The sub-process Assessing Progress (CS2) requires the Project Manager to assess Project Issues for impact and to suggest alternative actions

In the sub-process Assessing Progress (CS2), the Project Manager provides the Product Status Account to the Configuration Librarian

In the sub-process Assessing Progress (CS2), the Project Manager monitors work progress and the status of resources.

→

Maintaining an accurate and current picture of work progress and status of resources are the main objectives of Assessing Progress (CS2). The answer to this question is found on page 103 of the PRINCE2 Manual.

To capture, log and categorise all Project Issues

→

Capturing Project Issues (CS3) provides the entry point for all external stimuli, such as changes of scope, notification of problems or advice of new risks. All Project Issues should be entered into the Issue Log as soon as they are identified. The answer to this question is found on page 106 of the PRINCE2 Manual.

To produce the Highlight Report required by the Project Board

To ensure that the stage stays within tolerance

To collate all progress information for reporting to programme management.

Call for a meeting with the Project Board

Escalate Project Issues and wait for ad hoc direction from the Project Board

Assess each Project Issue for impact and consider alternative actions

→

Assessing a Project Issue before making a decision on a course of action is a fundamental principle of the sub-process Examining Project Issues (CS4). The answer to this question is found on page 107 of the PRINCE2 Manual.

Draft an Exception Plan.

1, 2 and 3 only

1, 2 and 4 only

→

The answer to this question is found on page 124 of the PRINCE2 Manual.

2, 3 and 4 only

All of the above.

A Highlight Report is an event-driven report on the status of a stage's progress

Highlight Reports are submitted to the Project Manager by the Team Manager

The Project Manager uses Highlight Reports to keep control of project stages

A Highlight Report should contain information about achievements in the current period and those expected in the next period.

→

Recent Checkpoint Reports will act as inputs to the next Highlight Report, which is produced by the Project Manager for submission to the Project Board. The Highlight Report is time-driven and sent to the Project Board at a frequency dictated by the Project Board. The answer to this question is found on page 240 of the PRINCE2 Manual.

To allow the Project Manager to take stock of the overall project status

To provide the Project Board with a project status summary to monitor stage and project progress

→

The Highlight Report is a report that provides the Project Board with a summary of the stage status. The Project Board should define the content and frequency of the Highlight Report. The answer to this question is found on page 115 of the PRINCE2 Manual. You can also read more about Highlight Report on page 241 of the PRINCE2 Manual.

To update a Team Manager and the team on the project's status

To enable the Project Board to match project actuals against the Project Plan.

The Highlight Report is submitted to the Project Manager by the Team Manager at pre-determined intervals

The Highlight Report details the products completed during the report period

→

The Highlight Report provides the Project Board with summary information about the status of the stage and project, and is produced at the frequency requested by the Project Board. The composition of the Highlight Report is found on page 358 of the PRINCE2 Manual. You can also read more about the sub-process Reporting Highlights (CS6) on page 114 of the PRINCE2 Manual.

Information for the Highlight Report is mainly derived from the Lessons Learned Log

The Project Board may request a Highlight Report upon submission of an Exception Report by the Project Manager.

Examining Project Issues (CS4)

Analysing Risks (PL6)

Escalating Project Issues (CS8)

→

The answer to this question is found on page 119 of the PRINCE2 Manual.

Giving Ad Hoc Direction (DP4).

Receiving a Completed Work Package?

→

The answer to this question is found on page 124 of the PRINCE2 Manual.

Taking Corrective Action?

Completing a Plan?

Designing a Project Management Team?

Is controlled completely by the Project Board?

Provides information for the Project Board to assess the continued viability of the Project?

Handles day-to-day management of the project?

→

In addition to handling day-to-day management of the project Controlling a Stage drives Managing Product Delivery. The answer to this question is found on page 96 of the PRINCE2 Manual.

The Team Manager is responsible for?

CS5 decides whether further Work Packages should be proposed

CS5 decides whether any plan modifications are required

CS5 ensures the project is properly initiated by approving a plan to develop the Project Initiation Document

→

Ensuring that the project is properly initiated by approving a plan to develop the Project Initiation Document is an objective of the Authorising Initiation (DP1) not Controlling a Stage. The objectives of the sub-process Authorising Initiation (DP1) can be found on page 74 of the PRINCE2 Manual.

CS5 decides whether a Project Issue needs to be escalated.