The role of the change authority in PRINCE2® is to authorize changes within the project that do not exceed a predefined budget. This role is designated to ensure that any change proposals are evaluated and approved without exceeding the allocated budget for changes, thereby maintaining control over project costs and scope.

PRINCE2® Foundation Manual

Among the six aspects of project performance that need to be managed according to PRINCE2®, 'Progress' is a key component. The other aspects include costs, timescales, quality, scope, risk, and benefits. Managing progress involves monitoring and controlling how far along the project is in achieving its objectives and delivering its products. References: PRINCE2® Foundation official documentation and study materials.

The 'Directing a Project' process in PRINCE2 starts when the request to authorize a project is received. This request usually comes after the initial project setup has been reviewed and there is a need to formally authorize the project to begin detailed planning and execution. This is a crucial step in establishing the governance framework that will guide the project's overall direction.

(PRINCE2® 7 Foundation Handbook, AXELOS)

The Project Manager should review the Highlight Report to report to the Project Board on the status of the project's issues. The Highlight Report provides a regular summary of the stage status, including progress against the plan and details about any issues or risks, making it the appropriate management product for communicating current issues to the Project Board.

(PRINCE2® 7 Foundation Handbook, AXELOS)

The project manager should record the impact assessment for a specific business opportunity in an 'Issue Report'. This management product is used to detail particular issues that might affect the project, including opportunities (which are treated like positive risks), and provides a basis for decision-making regarding these issues.

PRINCE2® 7 Foundation materials on issue management and related documentation.

A leadership activity within a PRINCE2 project involves several responsibilities, one of which is agreeing on work packages with team managers. This agreement includes specifying the tools and techniques to be used for product delivery. This activity is crucial for ensuring clarity and mutual understanding of how work is to be conducted, facilitating effective delegation and accountability within the project team.

(PRINCE2® 7 Foundation Study Guide, AXELOS)

hen the project board reviews the Project Initiation Documentation (PID), it is essential to ensure that the PID is aligned with the business objectives. The PID should encapsulate the project's definition, including the reasons for undertaking the project, the benefits expected, and how it aligns with the broader business goals. Ensuring this alignment helps validate that the project remains viable and worthwhile as it progresses.

(PRINCE2® 7 Foundation Handbook, AXELOS)

During the 'Initiating a Project' process, the project manager develops key information, including the detailed Project Initiation Documentation (PID), which enables the project board to decide whether to proceed with the project. This information outlines the approach, plans, and controls that will govern the project, providing a foundation for detailed planning and informed decision-making by the project board.

PRINCE2® 7 Foundation materials on the 'Initiating a Project' process.

To understand how user assurance will support the senior user on the project, the senior user should review the 'Role Descriptions' management product. This document outlines the responsibilities and interfaces for all project roles, including how user assurance supports the senior user by ensuring that the project's products meet the needs and requirements of the users.

PRINCE2® 7 Foundation documentation on management products, particularly Role Descriptions.