CCNA People: organizations, teams, and leadership Questions

The Executive is the single individual on the Project Board who has ultimate accountability for the project's business justification. They own the Business Case and must ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Project Manager manages the day-to-day work but does not own the Business Case; the Executive alone is responsible for its ongoing viability.

Separation ensures independence of assurance, preventing the Project Manager from making biased assessments of their own work.

During the Managing a Stage Boundary process, the Project Manager must update the Project Plan with actuals and forecasts to reflect the current stage's performance and provide a basis for planning the next stage. This ensures the Project Board has accurate information to authorize the next stage or take corrective action.

The purpose is to enable the Project Board to review the current stage's performance, approve the next stage plan, and ensure the Business Case remains viable.

The Senior Responsible Owner (Executive) is the ultimate owner of the Business Case and is responsible for its development and maintenance throughout the project. PRINCE2 mandates that the Executive ensures the Business Case remains viable, justified, and aligned with corporate strategy at every stage, approving any changes to it.

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 board's responsibilities from project initiation through to closure, including authorizing the initiation, stage plans, and project closure, as well as providing ad hoc direction. This process does not involve detailed planning or day-to-day management, which are handled by other processes.

The Executive (Senior Responsible Owner) chairs the Project Board meetings.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case, ensuring the project remains viable and aligned with organizational objectives. This includes approving the Business Case at initiation and any subsequent changes, as well as securing the necessary funding. The SRO also chairs the Project Board, providing overall leadership and direction, and is ultimately responsible for the project's success.

A Request for Change is a proposal for a change to a product that has been baselined; an Off-specification is a product that does not meet its specification.

Project Assurance is an independent role that checks the project is on track and cannot be delegated to the Project Manager. It supports the Board.

Project Assurance is an ongoing independent oversight of the project's management, while a quality review is a specific technique to assess the quality of a product at a given point in time.

The Project Board provides direction and control. Options A and B are correct. Option C is the PM's responsibility, D is the Senior User's, E is the SRO's.

The Project Board is accountable for the project and must ensure that independent assurance is in place. The Executive (SRO) often appoints assurance roles, but ultimate responsibility lies with the Project Board.

Escalation via Exception Report is required when a tolerance is forecast to be exceeded.

Option A is correct because the PRINCE2 principle of 'continued business justification' and 'manage by stages' require the project board to make decisions by consensus, not majority vote. Using majority vote undermines the principle of unified direction, as the project board must act as a single, cohesive unit representing business, user, and supplier interests. The exhibit likely shows a board where voting could lead to a split decision, violating the PRINCE2 requirement for joint decision-making.

The Senior Responsible Owner (Executive) chairs the Project Board. Option A is correct.

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, monitoring, and controlling project activities, escalating issues or deviations that exceed tolerances. The Project Board sets the overall direction and tolerances but does not manage daily tasks.

The Senior Responsible Owner (Executive) is accountable for the Business Case, ensuring the project remains viable and aligned with organizational objectives.

The Lessons Log is used to capture lessons throughout the project, including during a stage.

A is correct because the Project Manager is responsible for preparing Stage Plans, which detail how the work for a management stage will be executed, including schedules, resources, and controls. This is a core PRINCE2 responsibility as the Project Manager translates the Project Plan into actionable Stage Plans for the Project Board's approval.

Project Support provides administrative services. Options B, C, and E are typical. Option A is Project Assurance's responsibility, D is the PM's.

The Senior Supplier is responsible for providing the project's products and ensuring they meet the specified quality criteria. This role represents the suppliers who design, develop, and deliver the products, and thus bears the accountability for product quality against the defined acceptance criteria.

The Change Authority is an optional role that can be delegated by the Project Board to make decisions on change requests within defined limits. It is not the same as Project Support.

Project Assurance is an independent oversight role that monitors the project's adherence to standards and controls, while a quality review is a specific technique used to check that a product meets its quality criteria.

In PRINCE2, the Project Board is the decision-making body that provides overall direction and control. The board meets at each stage boundary to review progress, approve the next stage plan, and assess continued business justification. It also meets when an Exception Report is raised, which signals that a stage is forecast to exceed its tolerances, requiring the board to decide on corrective action.

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, delegating, monitoring, and controlling all project activities, and reporting progress to the Project Board. The Project Manager operates within the delegated authority of the tolerances (e.g., cost, time, scope) and must escalate any forecast deviation beyond those tolerances.

In PRINCE2, when a project manager forecasts that a stage will exceed its stage tolerance, they must escalate the issue to the Project Board by raising an Exception Report. This is because the Project Manager has authority only within the agreed stage tolerance; exceeding it requires the Project Board to decide on corrective action, such as approving a revised plan or closing the project.

An RFC is a proposal for a change that is not currently in the project's scope or specifications. An Off-Spec is something that should be provided but is not, or is provided incorrectly. Both are types of issue.

A Request for Change is a proposed change to a product specification or baseline, while an Off-specification is something that should be provided but is not (e.g., a product fails to meet its specification).

Project Board meetings are exception-driven; they are not on a fixed schedule except for stage boundaries.

Option A is correct because the Project Manager is responsible for preparing Stage Plans, which detail how a management stage will be executed, and submitting them to the Project Board for approval. This aligns with PRINCE2's principle of management by stages, where the Project Manager provides the detailed plan for the next stage.

The Project Board authorizes the next stage during the Managing a Stage Boundary process. This process prepares the Stage Plan for the next stage and presents it to the Project Board for approval, ensuring that the project remains viable and aligned with the business case before proceeding.

The Senior User is primarily responsible for defining the benefits and ensuring the project delivers a product that meets user needs. When an Exception Report recommends a scope change, the Senior User must assess whether the change is justified from a user-benefit perspective, as they represent the interests of those who will use the project's output. In PRINCE2, the Senior User's role includes approving changes that affect the project's scope, ensuring they align with the business case and user requirements.

PRINCE2 separates the Project Manager from Project Assurance to ensure independent oversight of the project's direction, progress, and compliance with standards. This separation prevents conflicts of interest that would arise if the same person were responsible for both managing the project and objectively assessing its health. Project Assurance provides an impartial check on the Project Manager's decisions, ensuring that the project remains viable and aligned with business, user, and supplier interests.

Option C is correct because PRINCE2 emphasizes that the project board must provide unified direction and timely decisions. When conflicting priorities arise, a facilitated session is a recognized technique to align the board's priorities, ensuring effective governance without bypassing the board's authority. This approach directly addresses the root cause—misalignment—rather than delaying, escalating prematurely, or reducing board involvement.

An RFC proposes a change to baselined products, while an Off-spec identifies that a product does not meet its specification (a defect or non-conformance).

In PRINCE2, the Senior Responsible Owner (SRO) is the single point of accountability for the project's success, as they own the Business Case and are ultimately responsible for ensuring the project delivers the expected benefits. The Project Manager is responsible for managing the project on a day-to-day basis but is not accountable for overall success. Option C correctly identifies the SRO's accountability, and option E correctly states that responsibility (for tasks) can be delegated, while accountability cannot.

The Project Board defines project-level tolerances; the Project Manager sets stage-level tolerances within them.

The Project Manager prepares the Highlight Report and sends it to the Project Board at regular intervals (e.g., weekly or monthly) to provide a summary of stage status.

Project Support and Change Authority are optional roles in PRINCE2. The other roles are mandatory.

In PRINCE2, when a project is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board via an Exception Report. This is because the Project Manager does not have authority to exceed tolerances; the Project Board must decide whether to approve a revised Business Case, adjust tolerances, or terminate the project. Option C correctly follows the PRINCE2 principle of management by exception.

In PRINCE2, when a Work Package is forecast to exceed its tolerance, the Project Manager must first discuss with the Team Manager to understand the situation and explore options. This aligns with the 'manage by exception' principle, where the PM is responsible for managing within stage tolerances and only escalates to the Project Board if the stage tolerance itself is threatened. The PM must gather detailed information before deciding on corrective actions or escalation.

Project Assurance is an independent, ongoing role providing objective oversight to the Project Board. Quality review is a specific technique for reviewing product quality at defined points.

The Project Initiation Documentation (PID) is the primary output of the Initiating a Project process. It provides the basis for the Project Board to decide whether to proceed.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It defines the project and forms the basis for its management. The Project Plan is part of the PID.

The Project Initiation Documentation (PID) is the key document created during the Initiating a Project process that defines how the project will be controlled. It consolidates the project's scope, objectives, and controls, including the management stages, tolerances, and reporting arrangements, providing a baseline for decision-making and governance throughout the project.

The Project Board meets at key decision points, which are exception-driven (when tolerances are forecast to be exceeded) and at stage boundaries. Option D is correct.

PRINCE2 defines distinct roles for management and delivery. The Project Board and Project Manager are key roles.

In PRINCE2, the Senior Responsible Owner (SRO) is the single individual accountable for the project's success, ensuring it delivers the required outcomes and realizes the expected benefits. This role is defined in the PRINCE2 framework as the ultimate decision-maker and owner of the business case, distinct from the Project Board's collective responsibility or the Project Manager's day-to-day management.

Option A is correct because in PRINCE2, the Senior Responsible Owner (SRO) is the single person accountable for the Business Case and ensuring the project delivers the expected benefits. The term 'Project Sponsor' is not a defined role in PRINCE2; it is a common industry term that may be used interchangeably with the SRO or other roles, but PRINCE2's official role structure uses the SRO as the key business representative on the Project Board.

If a Team Manager forecasts that work will exceed Work Package tolerances, they must escalate to the Project Manager via an Exception Report. The Project Manager then decides on corrective action or escalation to the Project Board.

Option A is correct because the Project Manager is responsible for producing the Project Plan, which includes the detailed schedule, resource allocation, and cost estimates. This is a core PRINCE2 responsibility, as the Project Manager owns the planning process and ensures the plan aligns with the project's business case and stage tolerances.

In PRINCE2, the Project Manager is responsible for preparing the Project Plan, as defined in the 'Plan' theme. This includes estimating, scheduling, and documenting the plan to achieve the project's objectives within agreed tolerances. The Project Manager owns the planning process and produces the plan for approval by the Project Board.

This process aims to provide the Project Board with information to review the current stage and approve the next stage plan.

Starting Up a Project (SU) is a pre-project process. Its purposes include ensuring that the project has a viable Business Case and that the necessary authorities are in place to proceed to initiation. Option C (authorize the project) is done in Directing a Project; Option D (produce the PID) is done in Initiating a Project; Option E (update the Business Case) is done throughout the project.

Project Assurance provides independent oversight of the entire project on behalf of the Project Board, whereas a quality review is a specific technique to assess the quality of a product.

The Initiating a Project process produces the Project Initiation Documentation (PID) as its key output. The PID consolidates all essential information required to manage the project, including the Business Case, Project Plan, and controls, and serves as the foundation for the next stage. It is the definitive document that authorizes the project to proceed.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case and its continued viability because PRINCE2 defines this role as the single point of accountability for the project's justification. The Executive owns the Business Case throughout the project lifecycle, ensuring it remains aligned with corporate strategy and approving any changes that affect its viability. This accountability cannot be delegated to the Project Manager, who is responsible for day-to-day management but not for the business justification.

The Project Initiation Documentation (PID) is the main output of Initiating a Project.

The Project Manager must first assess the impact of the delay on the Stage Plan and decide on corrective action within the agreed stage tolerances. This aligns with the PRINCE2 principle of management by exception, where the Project Manager handles deviations within tolerances before escalating. Only if the delay exceeds stage tolerances should an Exception Report be raised to the Project Board.

Project Assurance is a PRINCE2 role responsible for providing an independent, objective check to the Project Board that the project remains viable, compliant, and on track. It is not a day-to-day management function but a governance safeguard, ensuring that the project adheres to its business case, quality standards, and tolerances without being influenced by the Project Manager or delivery team.

Option B is correct because a Request for Change (RFC) is a proposal for a future modification to the project's baselined products, while an Off-specification (Off-spec) is a problem that has already occurred, indicating that a product does not meet its specification. In PRINCE2, the key distinction is timing: RFCs are proactive and seek approval for a planned change, whereas Off-specs are reactive and document a deviation that has already happened.

The 'manage by stages' principle requires that the project manager plans only one stage at a time in sufficient detail, while the next stage is planned just before it begins. In a distributed team with time zone delays, the first step is to plan the next management stage with clear communication milestones that explicitly account for time zone differences, ensuring that stage boundaries and decision points are synchronized despite the delays.

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

The project is within the stage tolerance of 10% (currently at 5% over time), and the Project Manager expects the trend to continue but has not yet exceeded the tolerance. According to PRINCE2, the Project Manager should continue managing the work within the agreed tolerance and report the deviation in the next Highlight Report, as this is the standard mechanism for communicating progress and forecast deviations that are still within tolerance. Raising an Exception Report is only required when a deviation is forecast to exceed the stage tolerance, which is not the case here.

Project Assurance is a PRINCE2 role responsible for verifying that the project remains viable and compliant with its business case, plans, and standards, independent of the Project Manager. A quality review is a specific technique used to assess whether a product meets its defined quality criteria and to identify defects. The key difference is that Project Assurance provides ongoing oversight of the project's adherence to plans and governance, while a quality review focuses on the quality of a specific product at a point in time.

The Senior Responsible Owner (SRO/Executive) is accountable for the project's success and owns the Business Case.

In a strong matrix structure, team members report to both functional and project managers, which can create loyalty conflicts. PRINCE2's 'defined roles and responsibilities' practice, documented in the Project Initiation Documentation (PID), clarifies each team member's authority, accountability, and reporting lines. This formal definition reduces ambiguity and reinforces commitment to the project by making project responsibilities explicit.

The purpose of Managing a Stage Boundary is to provide the Project Board with sufficient information to review the current stage, approve the next stage plan, and confirm the continued viability of the Business Case.

Option A is correct because the Senior User is responsible for specifying the user requirements and ensuring that the project delivers the expected benefits. This role represents the interests of the users and is accountable for defining the desired outcomes and confirming that the project's products meet those needs.

PRINCE2 recommends that the Project Board meets at stage boundaries and when an exception is raised (exception-driven).

Starting up a Project ensures that there is a viable and justified project idea before initiating the project.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and must ensure it remains viable throughout the project.

The Executive is the single person accountable for the Business Case and must ensure it remains viable throughout the project. PRINCE2 explicitly assigns ownership of the Business Case to the Executive, who approves any changes to it and decides whether the project should continue based on its ongoing justification.

The Project Manager manages day-to-day operations and prepares Highlight Reports. Creating the PID is done in Initiating a Project, and authorizing Work Packages is the Team Manager's role.