In the context of PRINCE2 7, the Issues practice is designed to identify, assess, and control any relevant event that has happened, was not planned, and requires management action. These events are categorized into three distinct types of issues to ensure they are handled appropriate by the Project…In the context of PRINCE2 7, the Issues practice is designed to identify, assess, and control any relevant event that has happened, was not planned, and requires management action. These events are categorized into three distinct types of issues to ensure they are handled appropriate by the Project Manager.
1. Request for Change: This is a proposal for a modification to a baseline. In PRINCE2, a baseline is a reference point (such as an approved Plan or Product Description) that has been signed off. Any change to these frozen documents—whether it implies adding a new feature, removing a scope item, or altering a timeline—is classified as a Request for Change. These typically incur costs or time delays and require formal approval from a Change Authority.
2. Off-specification: This issue type arises when a product is missing a feature, fails to meet a specific requirement, or is not available when expected. It represents a failure to meet the agreement outlined in the Product Description. For example, if a software component fails a security test or a physical prototype is smaller than the agreed dimensions, it is recorded as an Off-specification.
3. Problem/Concern: This is a broad category covering any other issue that the Project Manager must resolve or escalate. It often includes general inquiries, disputes, or external events impacting the project (such as a supplier delay). Significantly, a risk that has materialized (occurred) is also treated as a Problem/Concern.
Properly categorizing these issues in the Issue Register allows the project management team to assess their impact on project performance targets—time, cost, quality, scope, benefits, and sustainability—and decide on the correct course of action, whether that be a formal change procedure or corrective action.
Types of Issues in PRINCE2 Practitioner v7
Introduction and Importance In PRINCE2, the purpose of the Issues Practice is to provide a systematic way to identify, assess, and control changes and issues. It is impossible to plan for every eventuality in a project. Therefore, distinguishing between different types of issues is crucial because each type requires a specific management approach, funding source, and decision-making authority. If issues are categorized incorrectly, it can lead to scope creep, budget overruns, or failure to deliver the required quality.
The Three Types of Issues PRINCE2 explicitly distinguishes between three types of issues. Understanding the difference is vital for the Practitioner exam:
1. Request for Change (RFC) This is a proposal for a change to a baseline. A baseline is a product that has been approved and signed off (e.g., a Project Plan, a Product Description, or a finished product). Example: The Senior User requests that a login screen includes 'Face ID' authentication, which was not in the original approved design. Funding: These are typically funded via a Change Budget if one exists, or by the customer/user.
2. Off-specification (Off-spec) This occurs when something should be provided by the project, but currently is not (or is forecast not to be) provided. It is a failure to meet a requirement or an approved specification. Example: The supplier delivers the software, but the 'Forgot Password' feature does not work, despite being in the Product Description. Funding: Correcting an off-spec is usually done using Tolerance (budget/time), as it is fixing a deviation from what was promised.
3. Problem/Concern This is a catch-all category for any other issue that the Project Manager needs to resolve or escalate. It can be positive or negative. It is not a request to change a baseline, nor is it a failure to deliver a spec. Example: A team member raises a concern that the testing environment is too slow, or a stakeholder asks a question about the project's sustainability targets.
How it Works All three types work through the Issue and Change Control Procedure: 1. Capture: The issue is recorded in the Issue Register (and an Issue Report is created if formal handling is needed). 2. Assess: The Project Manager and relevant specialists assess the impact on the project's performance targets (Time, Cost, Quality, Scope, Benefits, Risk, and Sustainability). 3. Decide: A decision is made to approve, reject, or defer the issue. This depends on the authority level (Project Manager vs. Project Board vs. Change Authority). 4. Implement: The corrective action is taken.
Exam Tips: Answering Questions on Types of Issues In the Practitioner exam, you will likely be presented with a scenario and asked to identify the type of issue or the appropriate response. Follow these steps:
1. Baseline Check (The RFC Test): Ask yourself: Is the user asking for something NEW or DIFFERENT from what was originally signed off? If yes, it is a Request for Change. Look for keywords like 'enhance', 'add', or 'modify'.
2. Error Check (The Off-spec Test): Ask yourself: Is something MISSING or BROKEN? If the product fails to meet criteria that were previously agreed upon, it is an Off-specification. Look for keywords like 'failed', 'missing', 'omitted', or 'incorrect'.
3. Distinguish Risk vs. Issue: A common trap is confusing a Risk with a Problem/Concern. Remember: A Risk is uncertain (it might happen). An Issue has happened, is happening, or requires immediate decision. If the scenario says 'There is a worry that X might occur', it is a Risk. If it says 'X has occurred', it is an Issue.
4. Concession: Be aware that the Project Board might decide to accept an Off-specification without fixing it. This is called a Concession. In the exam, if the question asks how to handle a minor error that is too expensive to fix, 'accepting a concession' is often the correct answer.