An Issue Report is a formal document used in PRINCE2 7 to capture and manage any concern, problem, or change that arises during a project. It serves as the primary mechanism for recording issues that require assessment and decision-making by appropriate project management levels.
The Issue Report …An Issue Report is a formal document used in PRINCE2 7 to capture and manage any concern, problem, or change that arises during a project. It serves as the primary mechanism for recording issues that require assessment and decision-making by appropriate project management levels.
The Issue Report contains essential information including a unique identifier, the type of issue (whether it is a request for change, an off-specification, or a problem/concern), a detailed description of the issue, its impact assessment, priority rating, and recommended actions. It also tracks the status of the issue throughout its lifecycle.
There are three categories of issues in PRINCE2. First, a Request for Change represents a proposal to modify a baseline product, such as adding new features or altering existing functionality. Second, an Off-Specification occurs when a product fails to meet its specified requirements or when there is a forecast that it will not meet them. Third, a Problem or Concern covers any other matter that the Project Manager needs to address or escalate.
The Issue Report follows a structured process. When an issue is identified, it is logged and given a unique reference number. The Project Manager then examines the issue, assesses its severity and impact on the project objectives, and determines the appropriate response. Depending on the nature and significance of the issue, it may be handled at the Project Manager level or escalated to the Project Board for decision.
The Issue Report provides an audit trail of all issues and their resolution, ensuring transparency and accountability. It helps maintain control over project changes and problems while ensuring that stakeholders remain informed about matters affecting the project. This document is closely linked to the Issue Register, which provides a summary log of all issues raised during the project.
Issue Report - PRINCE2 Foundation v7 Complete Guide
What is an Issue Report?
An Issue Report is a management product in PRINCE2 that captures and maintains information about formal issues that need to be managed through the project. It provides a structured way to document any relevant event that has happened, was not planned, and requires management action.
Types of Issues Captured
The Issue Report can document three types of issues:
1. Request for Change - A proposal to modify a baseline product (something already approved)
2. Off-Specification - Something that should be provided by the project but currently is not, or is forecast not to be provided
3. Problem/Concern - Any other issue that the Project Manager needs to resolve or escalate
Why is the Issue Report Important?
The Issue Report is crucial because it:
• Provides a formal mechanism for capturing and tracking issues • Ensures issues are assessed for their impact on project objectives • Creates an audit trail of decisions made • Supports the Change Control Approach by documenting issue handling • Enables proper escalation when issues exceed tolerances • Helps maintain project integrity by controlling changes
How Does the Issue Report Work?
The Issue Report follows a lifecycle within PRINCE2:
Step 1: Capture - The issue is logged with details including date raised, author, and description
Step 2: Assess - The Project Manager examines the issue for impact on time, cost, quality, scope, benefits, and risk
Step 3: Propose - Options for resolution are identified and recommendations made
Step 4: Decide - The appropriate authority makes a decision based on the severity and impact
Step 5: Implement - The agreed action is carried out
Key Contents of an Issue Report
• Issue identifier and type • Date raised and author • Issue description • Impact assessment • Severity rating • Priority • Recommended action • Decision and date • Closure date
Who is Responsible?
The Project Manager is responsible for creating and maintaining Issue Reports. However, the decision authority depends on the severity:
• Project Manager can decide on issues within stage tolerance • Project Board decides on issues that exceed tolerance or require escalation • Change Authority (if appointed) can approve certain changes
Exam Tips: Answering Questions on Issue Report
Tip 1: Remember the three issue types - Request for Change, Off-Specification, and Problem/Concern. Questions often test whether you can identify the correct type.
Tip 2: Know that the Issue Report is created from the Issue Register. The Register is the summary log, while the Report contains full details.
Tip 3: Understand escalation paths. If an issue exceeds the Project Manager's authority, it must be escalated to the Project Board.
Tip 4: Connect the Issue Report to the Change Control Approach - this approach defines how issues will be handled.
Tip 5: When asked about timing, remember Issue Reports are created during the Managing a Stage Boundary and Controlling a Stage processes when issues are raised formally.
Tip 6: The severity and priority are different concepts - severity relates to impact on objectives, while priority relates to urgency of resolution.
Tip 7: Look for keywords in questions: 'formal', 'documented', 'tracked', and 'managed' often indicate the Issue Report is the correct answer.
Common Exam Question Patterns:
• Identifying which management product captures issue information • Determining who has authority to make decisions on issues • Distinguishing between Issue Register and Issue Report • Matching issue types to scenarios • Understanding the relationship between issues and exception handling