CCNA Overview of PRINCE2 and the project environment Questions

Delegating authority within agreed tolerances is precisely what 'manage by exception' enables: the Project Board sets tolerances for time, cost, scope, quality, risk and benefit, then only intervenes when the Project Manager forecasts a breach. This satisfies the stem's focus on the principle's primary purpose — escalation by exception rather than routine reporting.

This correctly describes the hierarchy: a project can sit within a programme, and programmes and standalone projects sit within a portfolio that aligns change initiatives with strategic objectives. Understanding this helps the project manager see how the project's Business Case and governance connect to programme benefits and portfolio investment decisions.

Project Assurance provides an independent, objective check on the project's viability and compliance on behalf of the Project Board, while Project Support delivers administrative services such as configuration management and tooling. This satisfies the stem by contrasting independent scrutiny against administrative assistance.

Tailoring involves adapting PRINCE2 to the project's size, complexity, and risk. Reducing stages and simplifying documentation is a valid way to apply the principle while retaining essential controls. This keeps the method proportionate and still complies with PRINCE2 principles, making it the best example of tailoring.

PRINCE2 recognises that projects may be part of a programme, which is a group of related projects and activities managed together to achieve benefits that would not be possible if they were managed separately. The mobile banking app project can be one project within that programme, and its business case should align with the programme's benefits. This option correctly describes the relationship and is the right answer.

Project Assurance operates independently of the Project Manager, reporting directly to the Project Board on the project's viability against business, user and supplier interests. This independence satisfies the stem's requirement for objective oversight, since assurance must not be compromised by the Project Manager's delivery pressures.

Any new requirement is an issue under PRINCE2, so the Project Manager must first capture it in the Issue Register and assess its impact before deciding whether it needs a formal change. Only after impact analysis can the appropriate authority decide.

This action demonstrates Learn from Experience by seeking lessons from similar past projects during initiation and maintaining a lessons log. The log is updated as new lessons emerge, and lessons are applied to improve the current project and inform future projects.

PRINCE2's integrated elements comprise seven principles, seven practices, seven processes, and tailoring to the project environment. This option correctly names all four, satisfying the stem's requirement for the complete integrated framework rather than partial lists or unrelated components such as themes or roles.

Poor planning is a recognised cause of project failure that PRINCE2 addresses through its Plans theme and product-based planning technique. This satisfies the stem by naming one of the three failure reasons the method is designed to counter.

Defined roles and responsibilities is a PRINCE2 principle that requires the project to have a clear organizational structure with defined roles. The project board must include the Executive, Senior User, and Senior Supplier to represent business, user, and supplier interests. This directly supports the project manager's need to ensure all three interests are represented in the team structure.

The Project Brief is a key output of the Starting up a Project process. It provides a foundation for the project, outlining the project definition, outline business case, and project approach. In this scenario, the project manager creates the Project Brief to present to the Project Board for authorization to initiate the project.

Practices form one of the three integrated elements of PRINCE2, alongside principles and processes. They describe the aspects of project management that must be applied consistently, such as business case and risk, satisfying the stem's requirement for a genuine integrated element.

The Senior User is responsible for specifying the needs of those who will use the project's products and for ensuring that the solution will deliver the expected benefits. This role provides the user perspective and confirms that the benefits defined in the Business Case are realized through the project's outputs.

Continued business justification demands that a project's business case is reviewed and revalidated at every stage and end stage assessment, so funding stops once benefits no longer outweigh costs. This directly maintains viability, the constraint the stem specifies.

The SB process produces the End Stage Report and Next Stage Plan, which the Project Board reviews to confirm the current stage delivered as agreed and to authorise the following stage, maintaining control at each boundary.

Tailoring scales PRINCE2 to the project's context, which includes simplifying or combining processes, roles and management products where full rigour adds no value. This satisfies the stem by confirming tailoring can reduce, not only add to, the method's standard documentation and process set.

This principle ensures that a project has a justified Business Case that is aligned with strategic objectives and remains valid throughout. By linking the project's Business Case to the programme's benefits, the project manager applies this principle, ensuring the project contributes to the programme's goals and remains viable.

PRINCE2 requires a clear Business Case.

Tailoring involves adapting PRINCE2 to the size, complexity, and risk of the project. Combining processes and reducing stage boundaries for a small, low-risk project is a direct application of this principle. PRINCE2 is designed to be tailored, and this scenario describes exactly that. The principle ensures that the method is not applied rigidly but is scaled appropriately.

Defined roles and responsibilities ensures that the project has a clear organisational structure with defined roles, including the three primary stakeholder interests: business, user, and supplier. This principle requires that these interests are represented in the Project Board and that roles are clearly defined. The scenario directly describes the need for clear accountability for these interests, which is the essence of this principle.

PRINCE2 deliberately excludes human resource management; it addresses roles, responsibilities and organisation structure, but line management of people, appraisals and team welfare sit outside its scope. This is the documented exclusion, so it correctly answers what the method does not cover.

Continued business justification is the PRINCE2 principle that requires the project to have a valid Business Case at the start and to remain justified throughout. Reviewing the Business Case at the end of each stage is a direct application of this principle, as it ensures the project is still aligned with business objectives and should continue. This is the correct principle being applied.

When a forecast breach of stage tolerances occurs, the Project Manager must escalate it by producing an Exception Report and referring it to the Project Board. This triggers the 'directing a project' process to decide how to proceed. Escalating promptly maintains the manage by exception principle and allows the Board to take corrective action.

Exceeding cost tolerance breaches the tolerance delegated to the Project Manager, so the matter must escalate to the Project Board via an Exception Report, which presents options and awaits direction. Proceeding without approval would violate the manage by exception principle governing stage-level authority.

Project Assurance is the Project Board's independent check on the project's viability, separate from the Project Manager, whereas Project Support is a non-decision-making administrative role. The option correctly separates independent oversight from administrative help, matching the accountability split PRINCE2 defines.

The Project Plan is the first plan to be created in the initiation stage.

Project Assurance monitors the project independently of the Project Manager, checking that all seven principles, themes and processes are applied correctly. Its independence from the delivery role satisfies the stem's requirement for an impartial view of progress.

PRINCE2 defines a project as a temporary organisation created for the purpose of delivering one or more business products according to an agreed business case. The payroll replacement is a temporary organisation with a defined start and end, created specifically to deliver the new system. This characteristic distinguishes it from business as usual, which is ongoing and permanent. Therefore, this option correctly explains why the work is a project.

Breaching stage cost tolerance exceeds the Project Manager's delegated authority, so the deviation must be escalated. An Exception Report informs the Project Board of the forecast breach, enabling it to decide on corrective action, satisfying the stem's requirement for handling tolerance exceedance.

'Directing a Project' enables the Project Board to be accountable for the project's success by making key decisions and exercising overall control, rather than performing day-to-day management. This satisfies the stem's requirement to identify the process's purpose: providing the decision-making and control layer that sits above the Managing a Stage Boundary and Controlling a Stage processes.

Human resource management covers line-management matters such as recruitment, contracts and appraisals, which PRINCE2 excludes. PRINCE2 addresses the organisation structure and role responsibilities for the project, but not the wider HR discipline, satisfying the stem's NOT requirement.

The Project Plan is produced during Initiating a Project, where the Project Initiation Documentation is assembled and the Project Board authorises the project. This satisfies the stem's question by distinguishing the project-level plan from the Stage Plan created later at Managing a Stage Boundary.

This principle ensures that every project has a clear organizational structure with defined roles, such as the Project Board, Project Manager, and Team Manager. In this scenario, establishing a Project Board with clear roles directly applies this principle, ensuring accountability and direction for the mobile banking app project.

Highlight Reports flow to the Project Board, satisfying the stem's requirement to distinguish the two by audience. Checkpoint Reports travel from Team Manager to Project Manager, covering work package progress at agreed frequencies. This recipient axis — Board versus Project Manager — is the defining difference, not content, timing or authorship.

Manage by Exception defines tolerances for time, cost, scope, quality, risk and benefits, empowering the Project Board to set boundaries and requiring the Project Manager to escalate only when a forecast breach exceeds delegated authority.

Alongside the revised next Stage Plan, the Managing a Stage Boundary process requires an End Stage Report summarising performance against the current Stage Plan, plus an updated Business Case and risk information, so the Project Board can authorise continuation.

This principle requires the PRINCE2 method to be adapted to the project's size, complexity, importance, capability and risk. Because the organisation has a Programme Office setting governance standards, the project's approaches must be tailored to align with those existing controls rather than applied in a generic, unmodified way, ensuring the method fits the wider organisational environment.

PRINCE2 supplies a defined vocabulary and role structure, so all stakeholders share consistent terminology for products, roles and processes. This common language reduces misunderstanding across organisational and disciplinary boundaries, satisfying the benefit of shared communication the question seeks.

A Request for Change proposes altering a product already agreed and baselined, whereas an Off-specification records a product that fails to meet its agreed specification. This distinction satisfies the stem's requirement by separating a proactive change proposal from a reported non-conformance, matching PRINCE2's change and quality terminology precisely.

Continued Business Justification requires the Business Case to be reviewed and confirmed viable, desirable and achievable at every stage, justifying continued investment. This satisfies the stem's emphasis on ongoing desirability, viability and achievability throughout the project's life.

The Business Case is a key input to the 'Managing a Stage Boundary' process and provides the current status of the project's justification. It is reviewed and updated at each stage boundary to ensure the project remains viable. The project board uses it to decide whether to continue, and it directly addresses the question about the status of the business justification.

Continued business justification requires the business case to remain valid throughout the project, not merely at initiation. It satisfies the principle that investment is re-evaluated at each stage boundary, and the project stops if justification lapses.

The Project Plan documents the products to be delivered and the resources and activities needed to deliver them, satisfying the Initiating a Project requirement. It provides the baseline against which progress is monitored, distinct from the Business Case, which justifies the investment.

Manage by exception involves setting tolerances and delegating authority to the Project Manager to manage within those tolerances. When the project is forecast to exceed the time tolerance, the Project Manager must escalate to the Project Board, which is exactly what this principle prescribes. This ensures that the Project Board is only involved when necessary.

The Project Brief is the output of Starting Up a Project and contains the outline Business Case, project definition and approach. The Project Board reviews it to decide whether to authorise initiation, which then produces the Project Initiation Documentation.

Reviewing the lessons log from previous projects is a key action for applying the learn from experience principle. It ensures that the project benefits from past successes and failures, avoiding repeated mistakes and leveraging proven practices. This is a direct application of the principle, as it involves seeking out and using lessons from similar projects to inform the current project's approach.

The Executive chairs the Project Board, owning the Business Case and holding ultimate accountability for the project's success. As chair, the Executive drives decision-making and represents the business interest, ensuring the project remains justified and aligned with corporate strategy.

The Project Initiation Documentation is the key output of Initiating a Project, consolidating the Business Case, Project Plan, and approach documents. It satisfies the process's purpose of establishing a firm baseline before the Project Board authorises the project to proceed.

The Project Initiation Documentation is assembled during Initiating a Project, containing the Project Plan, Business Case, risk and quality approaches. It satisfies the requirement to define how the project will be executed, monitored and controlled before the Project Board authorises the project.

The project brief is the pre-project document that gives the project board enough information to authorize the Initiating a Project process. It contains the project definition, outline business case, and project approach, allowing a go/no-go decision on whether to invest in the more detailed initiation work.

Forecast breach of a cost tolerance is an exception, so the Project Manager escalates by issuing an Exception Report to the Project Board, which decides how to respond. This satisfies the stem's first action, since tolerances cannot be exceeded without Board authorisation.

PRINCE2 defines a project as a temporary organisation created to deliver one or more business products according to an agreed Business Case. Uniqueness of the product, service or result is a defining characteristic, distinguishing projects from routine operational work.

Risk is one of the seven PRINCE2 practices, alongside business case, organisation, plans, quality, change and progress. It satisfies the stem's requirement by being a recognised practice, governing how the project team identifies, assesses and controls uncertainty throughout each stage of the project lifecycle.

Starting Up a Project is triggered by the Project Mandate and produces the Project Brief, along with the initiation stage plan. It precedes Initiating a Project, which then develops the Project Initiation Documentation from that brief.

Tailoring allows adaptation of processes, themes, roles, terminology, and management products to suit the project. However, all seven principles must remain applied; tailoring cannot be used to justify removing a principle such as continued business justification or manage by exception. This statement accurately reflects the relationship between tailoring and principles.

The business case theme is concerned with establishing whether the project is desirable, viable and achievable, and with maintaining that justification throughout the project. In this CRM implementation, the project board uses the business case to confirm continued alignment with corporate strategy and to decide whether to continue, change or stop the project. This theme directly addresses ongoing viability and investment justification, making it the correct answer.

This principle requires PRINCE2 to be adapted to the project's size, complexity, and organisational context. Using the Programme Office's templates and assurance reviews is an example of tailoring to the existing environment, ensuring the method fits the organisation's standards and governance without reinventing processes.

Cost tolerance breach means the stage or project plan can no longer be delivered within its agreed limits, so the deviation must be escalated to the Project Board. The Exception Report documents the cause, impact and options, enabling the Board to decide whether to authorise a revised plan.

These are distinct issue types on different axes. A Request for Change asks to alter an already-agreed product's baseline, whereas an Off-specification reports that a product has failed to meet its agreed specification. Both are captured in the Issue Register and assessed for impact.

Dividing a project into management stages directly enacts the Manage by Stages principle, which requires that the project be planned, monitored and controlled stage by stage. The stem's act of splitting work into discrete management stages is precisely this principle in operation.

Tailoring adapts PRINCE2's processes, themes and roles to suit a specific project's scale and complexity, whereas embedding integrates the method into an organisation's culture and working practices. This distinction satisfies the stem by separating project-level adaptation from organisation-wide adoption.

Spending 95% of budget against only 40% of scope breaches the approved +/-10% cost tolerance, so the business case no longer holds. Recommending closure lets the board stop further investment rather than continue a project whose forecast benefits cannot justify remaining spend.

Tailoring the number of stages is valid for small projects, provided that the Project Board retains control and can review progress. A single stage may be sufficient for a low-risk website update, but the Project Board must still authorize the project and review at key points to maintain the manage by exception principle and overall control.