CCNA Prince2 People Questions

An RFC proposes a modification to an agreed baseline, while an Off-spec is a product not meeting its specification (a deviation).

The risk owner is responsible for managing the risk overall, while the risk actionee is assigned to carry out specific actions to respond to the risk.

Option B is correct because one of the key purposes of the Directing a Project process is to confirm project closure, ensuring that all objectives have been met and that the project is formally closed. This includes authorizing the final stage and confirming that the project has delivered its products as defined in the Project Initiation Documentation.

In PRINCE2, the Team Manager is the role responsible for delivering the Work Package authorized by the Project Manager during the Controlling a Stage process. The Team Manager coordinates the team's work, ensures the products meet the agreed quality criteria, and reports progress back to the Project Manager.

The correct answer is C, 'Manage by stages,' because the PRINCE2 principle of managing by stages requires that each stage be planned, monitored, and controlled with defined escalation paths for issues. When team members bypass these paths and go directly to senior stakeholders, they undermine the stage-by-stage control and governance, violating the principle that decisions and escalations should follow the established stage boundaries and management levels.

Option C is correct because a Request for Change (RFC) is a formal proposal to modify a product, baseline, or process that has been approved, while an Off-Specification (Off-spec) is a formal notification that a product does not meet its agreed specification. In PRINCE2, an RFC seeks to change what is required, whereas an Off-spec reports a failure to deliver what was required. This distinction is fundamental to the issue and change control procedure.

Project Support in PRINCE2 is a role that provides administrative and clerical services to the project management team, such as maintaining files, organizing meetings, and managing project documentation. It does not have decision-making authority over stage plans, assurance, or budget management, which are the responsibilities of other roles like the Project Manager, Project Assurance, and the Executive.

The Project Initiation Documentation (PID) is the key output of Initiating a Project. It brings together all the information needed to start the project and is used by the Project Board to decide whether to proceed.

The Senior User represents those who will use the project's products, specifies the benefits, and ensures the project delivers them. They are also accountable for the Business Case's benefits realization.

Project Assurance is a PRINCE2 role that provides independent oversight of the project's ongoing viability, compliance, and quality from three distinct perspectives: business, user, and supplier. Option A is correct because the PRINCE2 framework explicitly requires Project Assurance to cover all three stakeholder viewpoints to ensure balanced governance and that the project remains aligned with business objectives, user needs, and supplier capabilities.

The Highlight Report is a progress report that summarizes the status of a management stage for the Project Board. According to PRINCE2, the Project Manager is responsible for producing the Highlight Report at intervals defined in the Communication Management Strategy, typically to keep the Project Board informed of progress, exceptions, and forecasts.

When a stage is forecast to exceed tolerance, the Project Manager must produce an Exception Report and submit it to the Project Board for decision. This is part of management by exception.

The Project Board is responsible for strategic decisions: approving plans, defining tolerances, and authorizing stage boundaries. Day-to-day management is the PM's role.

Option B is correct because Project Support is an optional role in PRINCE2, providing administrative and advisory services to the project manager and team, but it is not mandatory for the project management team structure. Option E is correct because the Change Authority role is also optional, delegated by the Project Board to manage change requests and off-specifications, and is only established if needed for change control.

Option C is correct because PRINCE2 dictates that when a project manager forecasts a deviation beyond the stage's cost tolerance, they must raise an Exception Report to the Project Board. The Project Board then decides on corrective action, such as approving a revised plan or closing the project. This ensures governance and control over the project's financial limits.

The Executive (Senior Responsible Owner) chairs the Project Board meetings in PRINCE2 because they are ultimately accountable for the project's success and have the authority to make key decisions. This role ensures the project remains aligned with business objectives and provides strategic direction during board meetings.

The Project Manager is responsible for day-to-day management of the project within tolerances set by the Project Board.

The PRINCE2 project management team includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optionally Project Assurance and Project Support. User group and Steering Committee are not PRINCE2 terms.

PRINCE2 separates the role of Project Manager from Project Assurance to ensure that assurance activities are performed independently of day-to-day management. This allows the Project Manager to focus on delivering the project's products and managing the team, while Project Assurance provides an objective check that the project remains viable, compliant with standards, and aligned with business expectations. The independence prevents conflicts of interest and ensures that assurance is not compromised by the pressures of daily project work.

Project Assurance is a continuous, independent oversight role for the Project Board, while a quality review is a specific technique to assess product quality at a point in time.

PRINCE2 recommends that Project Boards meet at the end of each management stage (Stage Boundary) and when an Exception Report is raised. They should not meet on a fixed monthly basis; meetings are exception-driven.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is the principle of management by exception.

The Project Board is responsible for providing overall direction and control to the Project Manager, but it does not handle day-to-day management. It meets on an exception-driven basis to review and decide on exception reports when a project deviates significantly from its tolerances, ensuring management by exception is applied. This is a core PRINCE2 principle that allows the board to focus on strategic decisions rather than routine operations.

The Change Authority is an optional role delegated by the Project Board to make decisions on change requests within defined limits. They can approve RFCs up to a certain cost or impact. They are not responsible for configuration management or raising RFCs.

In PRINCE2, the recommended leadership style for a Project Manager when the team has high competence but low commitment is Supporting (S3). This is because the team already possesses the necessary skills and knowledge (high competence) but lacks motivation or confidence (low commitment), so the PM should focus on encouraging, praising, and involving them in decision-making rather than providing technical direction or close supervision.

Project Support provides administrative and support services, such as maintaining files, providing planning support, and managing project administration.

An RFC proposes a change or enhancement; an Off-specification is a product that fails to meet its specification. Both are issues but differ in cause.

An RFC is a proposal for a change that adds value or modifies requirements; an Off-spec is something that should be provided but is not (e.g., a defect or omission).

Option A is correct because a Request for Change (RFC) is a formal proposal to modify an agreed product, baseline, or configuration item, while an Off-specification (Off-spec) is a notification that a product does not meet its agreed specification. In PRINCE2, these are distinct issue types: RFCs seek authorization for a change, whereas Off-specs report a deviation from the specification that must be resolved.

The Senior User is responsible for specifying the required quality criteria for the project's products and ensuring that the delivered products meet those criteria. This role represents the interests of those who will use the project's outputs and is accountable for defining acceptance standards and verifying that products satisfy the defined quality expectations.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and ensuring it remains viable. The Project Manager maintains it day-to-day, but the SRO owns it. This is a key PRINCE2 principle.

The Senior Responsible Owner (SRO/Executive) is accountable for the business case and its ongoing viability throughout the project.

Option B is correct because PRINCE2 defines the Senior Responsible Owner (SRO) as the single person accountable for the business case and overall project success, and it is a formal role within the PRINCE2 Project Board. 'Project Sponsor' is a generic term used in many organizations but is not a defined role in the PRINCE2 methodology. Therefore, the key difference is that the SRO is a specific PRINCE2 role, while 'Project Sponsor' is not part of the PRINCE2 terminology.

Project Assurance is a role within the PRINCE2 management structure, responsible for monitoring all aspects of the project's performance and products independently of the Project Manager. A quality review, on the other hand, is a specific technique used to assess the quality of a product against its defined quality criteria. Therefore, the key difference is that one is a role and the other is a technique.

The purpose is to provide the Project Board with information to review the current stage, approve the next stage plan, and update the project plan and Business Case. Option C is correct.