Scenario: The Ministry of Food Hygiene (MFH) has a quality management system which contains a document control process to manage all documentation…

The question asks to identify an additional risk placed on the project due to using the corporate configuration management procedure. Options B and C are not risks: B describes an issue (a certain event), and C describes a constraint (a statement of fact). Option D describes a risk but for a different project ('Outsourcing project').

By elimination, A is the correct answer. According to PRINCE2, projects should align with and leverage existing corporate or programme management standards. Using a mature, established corporate document control process is considered good practice that reduces uncertainty and risk, rather than adding to it. Therefore, this arrangement introduces no additional risk.

B. This statement describes a specific delay, which is an issue or a forecast, not a risk. A risk is an uncertain event that may or may not happen.

C. This is a statement of fact about the project's financial status. It is a project constraint, not an uncertain future event (a risk).

D. This describes a valid risk, but it is explicitly for the 'Outsourcing project', not the 'Restructuring project' that is the subject of the scenario.

1. AXELOS

"Managing Successful Projects with PRINCE2

7th Edition" (2023).

Section 11.1

What is risk?: Defines a risk as "an uncertain event or set of events that

should it occur

will have an effect on the achievement of objectives." This definition confirms that options B (an issue) and C (a constraint) are not risks.

Section 4.2.2

Corporate or programme standards: States

"The project management team should adopt the organization’s standards... Using the organization’s standards will reduce the work for the project and will mean that the project’s outputs are more easily integrated into the organization’s business as usual." This supports the rationale that using the corporate system is a risk-reducing measure

thus adding no additional risk.

Appendix A

Section A.5

Configuration management procedure: Notes that the project's procedure should detail how it aligns with any "corporate or programme management quality or configuration management systems." This reinforces that compliance is expected and not inherently a risk.