In PRINCE2 7, the Issues practice deals with handling events that were not planned and require management attention. There are three main types of issues that can occur during a project.
**1. Request for Change (RFC)**
A Request for Change is a proposal to modify a baseline product, such as a deli…In PRINCE2 7, the Issues practice deals with handling events that were not planned and require management attention. There are three main types of issues that can occur during a project.
**1. Request for Change (RFC)**
A Request for Change is a proposal to modify a baseline product, such as a deliverable that has already been approved. This could include changes to scope, requirements, or specifications. RFCs must be formally assessed for their impact on time, cost, quality, benefits, and risk before any decision is made. The change authority evaluates whether the change should be approved, rejected, or deferred.
**2. Off-Specification**
An off-specification occurs when a product does not meet its agreed specification or when it is forecast that it will fail to meet the specification. This represents a deviation from what was promised in the product description. Off-specifications need to be assessed to determine whether the product can be accepted as-is, whether corrective action is needed, or whether a concession should be granted to accept the non-conforming product.
**3. Problem or Concern**
This category covers any other issue that the Project Manager needs to resolve or escalate. Problems and concerns might include resource conflicts, stakeholder disagreements, external factors affecting the project, or any situation requiring management attention that does not fall into the other two categories.
**Managing Issues**
All issues should be captured in the Issue Register, which tracks their status, priority, and resolution. The severity and impact of each issue determines whether it can be handled at the Project Manager level or needs to be escalated to the Project Board. Effective issue management ensures that problems are addressed promptly and decisions are made with full understanding of consequences, keeping the project on track toward successful delivery.
Types of Issues in PRINCE2 Foundation v7
Why is Understanding Types of Issues Important?
Understanding the different types of issues is crucial for effective project management in PRINCE2. Issues can derail a project if not properly identified and managed. By categorizing issues correctly, project managers can apply the appropriate response strategy, escalate to the right authority level, and maintain project control. In the exam, this topic tests your ability to distinguish between different issue categories and understand their handling procedures.
What are Types of Issues?
In PRINCE2 v7, issues are categorized into three distinct types:
1. Request for Change A proposal to modify a baseline product. This could include changes to scope, deliverables, or any product that has been approved. Requests for change typically require formal change control procedures and impact assessment.
2. Off-Specification Something that should be provided by the project but currently is not, or is forecast not to be provided. This represents a deviation from the agreed specification. It could be a missing product, a product not meeting quality criteria, or a product that will not be delivered as planned.
3. Problem or Concern Any other issue that requires the Project Manager to resolve or escalate. This is a catch-all category for matters that are neither a request for change nor an off-specification but still need attention.
How Does Issue Management Work?
The issue management procedure follows these steps:
1. Capture - Record the issue in the Issue Register with all relevant details 2. Examine - Analyze the issue to understand its impact and determine its type 3. Propose - Develop options for resolving the issue 4. Decide - The appropriate authority makes a decision based on tolerance levels 5. Implement - Carry out the agreed course of action
The Project Manager handles issues within their delegated tolerance. Issues exceeding tolerance are escalated to the Project Board through an Exception Report.
Key Differences Between Issue Types
• Request for Change: Stakeholder-driven, seeks to add or modify something • Off-Specification: Performance-driven, something is missing or wrong • Problem/Concern: General matters requiring management attention
Exam Tips: Answering Questions on Types of Issues
1. Read scenarios carefully - The wording will indicate the issue type. Look for keywords like 'customer wants to add' (Request for Change) or 'product does not meet' (Off-Specification).
2. Focus on the source - If someone is asking for something new or different, it is likely a Request for Change. If something is not being delivered as promised, it is an Off-Specification.
3. Remember the catch-all - If an issue does not fit neatly into Request for Change or Off-Specification, it is a Problem or Concern.
4. Understand escalation - Questions may test whether an issue should be handled by the Project Manager or escalated to the Project Board based on tolerance.
5. Know the Issue Register - All issues regardless of type are recorded in the Issue Register. This is the single repository for tracking issues.
6. Link to Change Control - Requests for Change and Off-Specifications often go through change control procedures, especially if they affect baselined products.
7. Practice scenario-based questions - The exam often presents real-world situations where you must identify the correct issue type from the description provided.