In the context of PRINCE2 7, the Issue Register is a vital management product within the Issues practice, serving as the central repository for capturing and maintaining information on all formal issues. An issue is defined as any relevant event that has happened, was not planned, and requires mana…In the context of PRINCE2 7, the Issue Register is a vital management product within the Issues practice, serving as the central repository for capturing and maintaining information on all formal issues. An issue is defined as any relevant event that has happened, was not planned, and requires management action. The Issue Register is distinct from the Daily Log, which handles informal management notes; only issues requiring formal handling—specifically Requests for Change (RFCs), Off-specifications, and Problems/Concerns—are recorded here.
From a Practitioner perspective, the register is used to monitor and control the project's direction. It is created during the 'Initiating a Project' process and updated continually throughout the lifecycle, particularly during 'Controlling a Stage'. Each entry typically includes a unique Issue ID, the type of issue, the date raised, the originator, a description, and the current status (e.g., live, closed, or unresolved). Crucially, it documents the impact analysis, detailing how the issue affects project performance targets (time, cost, quality, scope, benefits, and risk).
The Issue Register ensures that every change request or deviation is visible, assessed, and tracked until resolution. It supports the Project Manager in reporting to the Project Board via Highlight Reports and End Stage Reports, ensuring that stakeholders are aware of current challenges. Effective maintenance of the Issue Register provides an audit trail of all decisions made regarding changes and problem resolution, preventing scope creep and ensuring that the project remains aligned with its Business Case.
PRINCE2 Practitioner v7 Guide: The Issue Register
What is the Issue Register? In PRINCE2 v7, the Issue Register is a management product used to capture and maintain information on all the issues that are being managed formally. It serves as the project's central log for any event that has happened, was not planned, and requires management action. It is essentially the 'ledger' for the project's Change Control.
Why is it Important? Projects rarely go exactly to plan. The Issue Register is vital because: 1. Control: It prevents uncontrolled change (scope creep) by ensuring every request is logged and analyzed. 2. Visibility: It provides a snapshot of the current status of all outstanding problems and change requests. 3. Audit Trail: It records the history of what issues were raised, how they were prioritized, and the decisions made.
Key Components While the format can vary, a robust Issue Register typically contains: - Issue Identifier: A unique reference number. - Issue Type: Classifying the issue as a Request for Change, Off-specification, or Problem/Concern. - Date Raised & Author: Who raised it and when. - Priority & Severity: Ratings to determine urgency and impact. - Status: E.g., Active, Closed, Deferred.
How it Works The register is created during the Initiating a Project process. Throughout the project life cycle (specifically during the Controlling a Stage process), whenever a formal issue arises: 1. The Project Manager (or Project Support) enters the issue into the register. 2. An Issue Report may be created to detail the impact analysis. 3. Once a decision is made, the status in the Issue Register is updated. 4. It remains live until the project closes.
Exam Tips: Answering Questions on Issue Register For the PRINCE2 Practitioner exam, questions often present a scenario and ask whether the Issue Register is the correct place for specific data or how it should be updated. Follow these rules:
1. Differentiate from the Daily Log If the scenario describes a 'diary' entry, a minor informal problem, or a note about a potential future risk that hasn't happened yet, it belongs in the Daily Log. If the scenario involves a formal request for change, a missing product feature (Off-spec), or a significant problem requiring a decision, it goes in the Issue Register.
2. Identify the Issue Type You may be asked to categorize an entry in the register. Remember: - Request for Change: A proposal to change a baseline (e.g., adding a new feature). - Off-specification: Something is missing or incorrect compared to the original agreement (e.g., a product fails a quality test and cannot be fixed easily). - Problem/Concern: General issues that are not changes or off-specs (e.g., a supplier goes bankrupt).
3. Tracking vs. Detail If a question asks where to find the detailed analysis and recommendation for a specific issue, the answer is the Issue Report. If the question asks where to see the list or current status of all issues, the answer is the Issue Register.
4. Maintenance The Project Manager is responsible for the register, but Project Support often performs the administrative task of updating it. Ensure the scenario justifies who is doing the typing versus who owns the responsibility.