In PRINCE2 7, an issue is formally defined as a relevant event that has happened, was not planned, and requires management action. Issues are distinct from risks in that risks are uncertain future events, while issues are events that have already occurred or are currently happening and need to be a…In PRINCE2 7, an issue is formally defined as a relevant event that has happened, was not planned, and requires management action. Issues are distinct from risks in that risks are uncertain future events, while issues are events that have already occurred or are currently happening and need to be addressed.
The Issues Practice in PRINCE2 7 provides a structured approach to capturing, assessing, and resolving these unplanned events throughout the project lifecycle. Issues can arise from various sources including team members, stakeholders, customers, or external parties, and they must be properly documented and managed to ensure project success.
There are three types of issues recognised in PRINCE2:
1. Request for Change - A proposal to modify a baseline product, such as adding new features or altering specifications that were previously agreed upon.
2. Off-specification - A situation where a product does not meet its agreed specification, or where there is a forecast that it will not meet the specification. This represents a deviation from what was promised.
3. Problem or Concern - Any other type of issue that the Project Manager needs to resolve or escalate, which does not fall into the above categories.
Each issue must be captured in an Issue Register, which serves as a central repository for tracking all issues throughout the project. The Issue Register records details such as the issue type, description, priority, severity, status, and the individual responsible for resolution.
The Project Manager is responsible for assessing each issue, determining its impact on project objectives, and deciding on appropriate action. Depending on the severity and authority levels, issues may be resolved at the project level or escalated to the Project Board for decision-making. Proper issue management ensures that unplanned events are handled efficiently, minimising negative impacts on time, cost, quality, and scope.
Definition of an Issue in PRINCE2 v7
Why is Understanding the Definition of an Issue Important?
Understanding what constitutes an issue in PRINCE2 is fundamental to the Foundation exam. Issues are one of the three types of events that can affect a project (alongside risks and changes), and the exam frequently tests whether candidates can distinguish between these concepts. Misidentifying an issue can lead to incorrect responses in scenario-based questions.
What is an Issue?
In PRINCE2 v7, an issue is defined as a relevant event that has happened, was not planned, and requires management action. Issues are events that are currently happening or have already occurred, distinguishing them from risks which are uncertain future events.
The key characteristics of an issue are: - It is something that has happened (not something that might happen) - It was not planned for in the project - It requires management action to be addressed
Three Types of Issues
PRINCE2 categorizes issues into three types:
1. Request for change - A proposal to change a baseline (e.g., modifying a product specification)
2. Off-specification - Something that should be provided by the project but currently is not, or is forecast not to be provided (a deviation from specification)
3. Problem or concern - Any other issue that the Project Manager needs to resolve or escalate (general issues that do not fit the other categories)
How the Issues Practice Works
The Issues practice in PRINCE2 establishes a systematic approach to: - Capture - Identifying and recording issues as they arise - Assess - Analyzing the impact and implications of each issue - Propose - Developing response options - Decide - Selecting the appropriate response - Implement - Taking action to address the issue
Issues are recorded in the Issue Register, which serves as a repository for all formal issues requiring attention.
Exam Tips: Answering Questions on Definition of an Issue
Tip 1: Focus on timing Remember that issues have already happened. If a question describes something that might occur in the future, it is a risk, not an issue.
Tip 2: Look for the unplanned element Issues are events that were not anticipated or planned for. Routine activities are not issues even if they require action.
Tip 3: Identify the issue type When a question asks about categorizing an issue, determine if it involves changing a baseline (request for change), missing or incorrect deliverables (off-specification), or something else (problem or concern).
Tip 4: Remember management action is required Not every unexpected event is an issue. PRINCE2 defines issues as events requiring management action to resolve.
Tip 5: Distinguish from risks A common exam trap is confusing issues with risks. Ask yourself: Has this happened yet? If yes, it is an issue. If it is uncertain whether it will happen, it is a risk.
Tip 6: Watch for scenario clues In scenario questions, look for phrases like 'has occurred', 'was discovered', 'has been found', or 'is currently' which indicate an issue rather than a risk.
Common Exam Question Formats
- Identifying whether a scenario describes an issue or a risk - Categorizing an issue as a request for change, off-specification, or problem/concern - Selecting the correct definition of an issue from multiple options - Determining appropriate responses to different issue types