In the context of PRINCE2 7, the Issue Management Approach is a baseline management product created during the 'Initiating a Project' process. It describes precisely how the project will capture, assess, and control issues. Under PRINCE2 definitions, an 'issue' is a relevant event that has happened…In the context of PRINCE2 7, the Issue Management Approach is a baseline management product created during the 'Initiating a Project' process. It describes precisely how the project will capture, assess, and control issues. Under PRINCE2 definitions, an 'issue' is a relevant event that has happened, was not planned, and requires management action; this includes requests for change, off-specifications (where a product fails to meet criteria), and general problems or concerns.
The primary objective of this document is to establish a standard, effective procedure for handling deviations from the project plan, thereby protecting the project's baselines (cost, time, scope, quality) from uncontrolled scope creep. It defines the project's specific 'Issue and Change Control Procedure,' which typically follows the steps: Capture, Assess, Decide, and Implement.
Key components of the Issue Management Approach include:
1. Roles and Responsibilities: It clarifies who can authorize changes (identifying the Change Authority and the budget available to them), the role of Project Support in maintaining the Issue Register, and the Project Manager's decision-making limits.
2. Scales: It establishes consistent metrics for prioritizing issues (e.g., MoSCoW - Must have, Should have, Could have, Won't have for now) and rating severity, ensuring objective assessment across the team.
3. Configuration Management: It details how product versions (Configuration Items) and records will be tracked to ensure that the status of project assets is always known.
4. Timing and Reporting: It outlines when issue reviews occur and how decisions are communicated to stakeholders.
Without a robust Issue Management Approach, a project lacks the governance required to manage uncertainty. By defining these rules upfront, the project team ensures that every change or problem is treated on its merits, balanced against the Business Case, and managed without derailing the project's justification.
What is the Issue Management Approach? In PRINCE2 v7, the Issue Management Approach is a management product usually created during the Initiating a Project process. It defines the specific procedures and techniques the project will use to identify, assess, and control issues (which include Requests for Change, Off-specifications, and Problems/Concerns). It essentially sets the 'rules of the game' for how the project handles change and uncertainty regarding the project's baseline.
Why is it Important? Without a robust Issue Management Approach, projects are vulnerable to Scope Creep. Uncontrolled changes can destroy the Business Case by increasing costs or delaying timelines without proper authority. This document ensures that every issue is captured, assessed for impact on the project performance targets (Time, Cost, Quality, Scope, Risk, Benefits), and decided upon by the appropriate authority level.
How it Works The approach details the Issue and Change Control Procedure, which generally follows five steps: 1. Capture: Recording the issue in the Issue Register. 2. Assess: Analyzing the impact (Business Case and Project Plan) and prioritizing (using scales like MoSCoW or 1-5). 3. Propose: Identifying options for resolution. 4. Decide: The Change Authority or Project Board approves, rejects, or defers the recommendation. 5. Implement: Taking corrective action.
It also defines the Change Budget (money set aside to fund approved changes) and the severity/priority scales to be used.
How to Answer Practitioner Exam Questions In the PRINCE2 Practitioner exam, questions regarding this document often focus on tailoring and application. You will likely face scenarios where you must determine if a specific approach is appropriate for the scenario.
1. Is the procedure efficient? If a project is small and simple, a complex bureaucratic issue procedure is inappropriate. If the project is highly regulated, a very loose procedure is inappropriate.
2. Check the Roles. Look at who is designated as the Change Authority. Is it appropriate for the Senior User to approve technical changes? Or for the Senior Supplier to approve changes that drastically increase the budget? Ensure the people assigned have the knowledge and authority.
3. Check the Scales. The exam may present a 'Priority Scale' or 'Severity Scale'. You must judge if the definitions provided (e.g., 'Critical', 'Major', 'Minor') are clear and useful for the project team in that specific scenario.
Exam Tips: Answering Questions on Issue Management Approach Tip 1: Distinguish between the 'Approach' and the 'Register'. The Approach is the 'How-to' guide (the rules). The Register is the log of actual events. If the question asks about how to categorize an issue, look for the Approach. If it asks about the status of a specific defect, look for the Register.
Tip 2: The Change Budget. Remember that the Issue Management Approach defines how the Change Budget is managed. In the exam, ensure the Change Budget is not being used to fund things that should be in the initial project plan. It is strictly for authorized changes.
Tip 3: Integration with Configuration Management. In v7, issue management is closely linked with maintaining the integrity of products. The approach should explain how issues link to the creation of new versions of products (Configuration Item Records).