Issue Resolution is a fundamental component of the Issues Practice in PRINCE2 7, providing a structured approach to handling problems that arise during project execution. An issue is defined as any relevant event that has happened, was not planned, and requires management action. Issues can include…Issue Resolution is a fundamental component of the Issues Practice in PRINCE2 7, providing a structured approach to handling problems that arise during project execution. An issue is defined as any relevant event that has happened, was not planned, and requires management action. Issues can include problems, concerns, changes to requirements, or any other matter that needs addressing.
The Issue Resolution process begins with capturing and logging issues in an Issue Register, which serves as a central repository for tracking all identified issues throughout the project lifecycle. Each issue is assigned a unique identifier, categorized by type, and assessed for its potential impact on project objectives including time, cost, quality, scope, benefits, and risk.
Once an issue is logged, it undergoes analysis to determine the appropriate response. The Project Manager evaluates the severity and urgency of each issue, considering various resolution options. These options might include taking corrective action within existing tolerances, escalating to the Project Board when tolerances are threatened, or implementing approved changes through formal change control procedures.
The resolution approach depends on the issue type and its potential consequences. Some issues can be resolved at the Project Manager level, while others require escalation through Exception Reports when they exceed delegated authority. The Project Board then decides on the appropriate course of action, which may involve approving additional resources, accepting modified outcomes, or implementing alternative solutions.
Effective issue resolution requires clear escalation paths, defined roles and responsibilities, and regular communication with stakeholders. The process ensures that problems are addressed promptly and systematically, preventing minor concerns from escalating into major project threats. Throughout the resolution process, all actions and decisions are documented, maintaining an audit trail that supports project governance and enables lessons to be learned for future projects.
Issue Resolution in PRINCE2 Foundation v7
Why Issue Resolution is Important
Issue resolution is a critical component of the Issues practice in PRINCE2 because projects rarely go exactly as planned. Issues can arise from various sources including team members, stakeholders, or external factors. Having a structured approach to resolving issues ensures that problems are addressed systematically, decisions are made at the appropriate level, and the project remains on track to deliver its objectives.
What is Issue Resolution?
Issue resolution refers to the systematic process of analyzing, evaluating, and determining the appropriate response to issues that arise during a project. In PRINCE2, issues fall into three categories:
• Request for change - a proposal to modify a baseline • Off-specification - something that should be provided but currently is not, or is forecast not to be • Problem or concern - any other issue that needs to be resolved
The resolution process ensures that each issue receives appropriate attention and is escalated to the correct management level when necessary.
How Issue Resolution Works
The issue resolution process follows these key steps:
1. Capture - Record the issue in the Issue Register with relevant details
2. Examine - Analyze the issue to understand its impact on time, cost, quality, scope, benefits, and risk
3. Propose - Develop options for resolving the issue, including doing nothing
4. Decide - Determine which option to implement based on authority levels: • Project Manager can resolve within stage tolerances • Project Board involvement required for issues exceeding tolerances • Change Authority may handle certain types of changes if established
5. Implement - Execute the chosen resolution
Key Documents
• Issue Register - tracks all formal issues and their status • Issue Report - provides detailed analysis of significant issues requiring Project Board decision
Exam Tips: Answering Questions on Issue Resolution
1. Know the three issue types - Be clear on the distinction between requests for change, off-specifications, and problems or concerns. Exam questions often test whether you can identify the correct category.
2. Understand escalation triggers - Remember that issues are escalated to the Project Board when they exceed the Project Manager's tolerances or authority. The Project Manager handles issues within their delegated limits.
3. Remember the Change Authority role - A Change Authority may be established to make decisions on certain changes, reducing the burden on the Project Board.
4. Focus on impact analysis - Questions may ask about what factors should be considered when examining an issue. Think about the six performance targets: time, cost, quality, scope, benefits, and risk.
5. Link to other practices - Issue resolution connects to Risk (issues may create new risks), Change Control (for baseline changes), and Progress (reporting issue status).
6. Watch for scenario-based questions - Read carefully to determine whether the scenario describes something within tolerance or requiring escalation.
7. Remember documentation requirements - All formal issues go in the Issue Register; significant issues requiring board decisions need an Issue Report.