When the project board reviews whether the investment remains justified as the project progresses,

this application of the 'manage by stages' principle is evident. This principle ensures that at the end

of each stage, the project board reassesses the business case and the viability of the project before

deciding to continue with the next stage.

Reference: PRINCE2® 7 Foundation resources on the 'manage by stages' principle.

Risk appetite is defined as the amount and type of risk that an organization is willing to take in

pursuit of its objectives. This concept helps organizations balance the potential benefits of risk-taking

with their capability to manage the impact of unfavorable outcomes. Reference: PRINCE2® training

manual and risk management framework.

In PRINCE2®, the role responsible for appointing the Senior User, as well as other key project roles

such as the Executive and the Senior Supplier, is typically taken by someone from corporate or

program management, or the customer. This aligns with the principle of clearly defined roles and

responsibilities, ensuring that the project has clear governance and accountability. The Senior User is

appointed to represent the interests of all those who will use the project’s products, who will benefit

from the outcomes, and those whose work might be impacted by the change.

Reference: PRINCE2® Foundation Manual

In PRINCE2®, the management of ongoing changes to the project ecosystem involves adapting the

project's approach and scope based on real-time information and challenges that arise during the

lifecycle of the project. This step is critical when new tasks or changes in tasks are identified, as

outlined by the project manager. This ensures that the project remains aligned with its intended

outcomes and can adapt to internal and external influences effectively.

Reference: = PRINCE2® 7 Foundation Training Manual and official PRINCE2® website documentation

According to the 'exception management' technique, the team manager should raise an issue when

they predict that a product will cause a work package to exceed its time tolerance. This proactive

approach allows for timely decision-making and corrective action by the Project Board, ensuring that

project delivery is kept on track and within the agreed tolerances. Reference: PRINCE2® methodology

and exception management guidance.

A minimum requirement for applying the quality theme in PRINCE2® is to define quality criteria

within product descriptions. This includes specifying what the product must do, the standards it must

meet, and how quality will be evaluated, ensuring that all project products deliver against the

agreed-upon requirements and standards.

Reference: = PRINCE2® 7 Foundation handbook and online resources

A time-driven control is defined as a monitoring system that is based on a fixed time interval, such as

weekly or monthly progress reports. The expected frequency of progress reports specified in a work

package represents a time-driven control, where updates are required at predefined intervals

irrespective of the state of the project at those times.

Reference: = PRINCE2® 7 Foundation handbook and online resources

An objective of the 'Controlling a Stage' process in PRINCE2® is to replan the current stage when

directed. This process handles day-to-day management of the project, and includes responding to

issues that might impact the stage plan, requiring replanning to ensure project objectives can still be

met.

Reference: PRINCE2® Foundation Manual

In PRINCE2® terminology, a dis-benefit is defined as a measurable decline resulting from a negative

outcome. Dis-benefits are considered alongside benefits to assess the overall value and impact of the

project. They represent outcomes that are perceived as negative by one or more stakeholders.

Reference: PRINCE2® Foundation Manual

The term 'off-specification' is defined as a product that will not meet its quality specifications. This

indicates a variance from what was agreed upon in the product description, requiring attention and

potentially corrective action to ensure the project's outputs meet the required standards. Reference:

PRINCE2® Foundation glossary and project documentation guidelines.