Issues Practice

The correct answer is: To capture and maintain information about all issues that arise during the project lifecycle.

This is the accurate definition of the Issue Register's purpose in PRINCE2 7. The Issue Register is a project record that captures and maintains information on all issues (which include requests for change, off-specifications, and problems/concerns) that are raised during the project. It provides a central repository for tracking issues from the point they are raised through to closure.

Why the other answers are incorrect:

The answer about capturing risks, issues, and quality deviations is incorrect because risks are managed separately in the Risk Register, not the Issue Register. While quality deviations may become issues (specifically off-specifications), the Issue Register does not track risks.

The answer about stakeholder concerns requiring management team escalation is too narrow. The Issue Register captures all issues regardless of whether they require escalation or not. Issues can be resolved at various levels depending on tolerances and delegated authority, and not all require formal escalation to the management team.

The answer about problems, root cause analysis, and preventative measures is incorrect because this describes more of a lessons log or quality review approach. While problems/concerns are one type of issue captured in the Issue Register, the register's primary purpose is not focused on root cause analysis and preventative measures implementation - it's focused on capturing and maintaining information about the issues themselves and tracking their resolution.

The correct answer is: To formally document and communicate concerns, problems, or off-specifications that require management attention and decision-making.

In PRINCE2 7, an Issue Report serves a specific purpose within the Change theme. Its primary function is to formally capture and communicate issues that arise during the project. These issues can include:

• Problems or concerns that need to be addressed
• Off-specifications (when a product doesn't meet its specified requirements)
• Requests for change
• Any situation requiring management attention and a decision

The Issue Report provides a structured way to document these matters so they can be assessed, prioritized, and resolved through the project's change control procedures.

Why the other answers are incorrect:

The second answer focuses on operational achievements, completed deliverables, and milestone progressions. These positive outcomes would typically be documented in products like Checkpoint Reports, Highlight Reports, or End Stage Reports, not in an Issue Report. Issue Reports specifically deal with problems and concerns, not achievements.

The third answer describes resource allocation changes, team capacity adjustments, and scheduling modifications. While these might result from addressing an issue, they are not the purpose of an Issue Report itself. Such changes would be reflected in updated project plans, and the Issue Report would only document the problem that necessitated these changes.

The fourth answer relates to stakeholder expectations, user requirements, and acceptance criteria. These elements are captured in products like the Project Product Description, Product Descriptions, and the Project Brief or Project Initiation Documentation, not in Issue Reports. Issue Reports deal with problems that arise during execution, not with defining what needs to be delivered.

The correct answer is: Request for Change, Off-Specification, and Problem or Concern.

In PRINCE2 7, the Issue and Change Control practice defines three formal categories for classifying issues throughout a project:

1. Request for Change: A proposal to modify an approved baseline, such as scope, time, cost, or quality. This could be a request to add, modify, or remove something from the project.

2. Off-Specification: A situation where a product or work output fails to meet its agreed specification or quality criteria. This represents something that was supposed to be delivered to a certain standard but hasn't met that standard.

3. Problem or Concern: Any other issue, question, or concern that needs to be formally captured and managed but doesn't fall into the other two categories. This is a catch-all category for various issues that may arise.

Why the other answers are incorrect:

The option mentioning 'Quality Exception' uses incorrect PRINCE2 terminology. While quality issues are addressed in PRINCE2, they are captured as Off-Specifications, not Quality Exceptions.

The option including 'Risk Event' confuses issue management with risk management. Risks are managed separately through the Risk Management practice in PRINCE2, not as a category of issue.

The option that adds 'requiring escalation to the Project Board' is unnecessarily restrictive. Problems or Concerns don't all require escalation to the Project Board - this is just one possible outcome depending on the severity and nature of the issue. The three categories are simply classification types, not dependent on escalation requirements.