In PRINCE2 7, a Problem or Concern is one of the three types of issues that can be raised during a project, alongside Request for Change and Off-Specification. Understanding this classification is essential for effective issue management within the Issues practice.
A Problem or Concern refers to a…In PRINCE2 7, a Problem or Concern is one of the three types of issues that can be raised during a project, alongside Request for Change and Off-Specification. Understanding this classification is essential for effective issue management within the Issues practice.
A Problem or Concern refers to any matter that the Project Manager needs to address or escalate but does not fall into the categories of requesting a change to the baseline or identifying something that deviates from agreed specifications. These are typically worries, queries, or situations that could potentially impact the project if left unaddressed.
Examples of Problems or Concerns include resource availability questions, potential risks that have not yet materialized, stakeholder relationship difficulties, communication challenges, or uncertainties about how to proceed with certain aspects of the project. They represent situations where clarity, guidance, or action is needed to maintain project momentum and health.
When a Problem or Concern is identified, it should be captured in the Issue Register, which serves as a central repository for all issues requiring attention. The Project Manager must assess each Problem or Concern to determine its severity and the appropriate response. Some may be resolved at the Project Manager level, while others may require escalation to the Project Board for decision-making.
The key difference between a Problem or Concern and other issue types is that it does not necessarily require a formal change to project baselines or products. Instead, it calls for investigation, discussion, and potentially advisory input from relevant stakeholders or authorities.
Effective handling of Problems and Concerns demonstrates good project governance and helps prevent minor issues from escalating into major threats. By maintaining vigilance and addressing these matters promptly through the Issues practice, project teams can sustain stakeholder confidence and keep the project on track toward successful delivery.
Problem or Concern in PRINCE2 Issues Practice
What is a Problem or Concern?
In PRINCE2, a Problem or Concern is one of three types of issues that can be raised during a project. It represents a situation that the Project Manager needs to resolve or escalate, but it is not a request for change and it is not related to a missing product or quality failure.
A Problem or Concern typically involves: • Worries about the project's direction or viability • Resource availability issues • External factors affecting the project • Stakeholder concerns about any aspect of the project • Any situation requiring attention that doesn't fit the other issue categories
Why is Understanding Problem or Concern Important?
Recognizing and correctly categorizing issues is essential because: • Different issue types require different handling approaches • Proper categorization ensures issues are escalated appropriately • It helps maintain accurate project documentation • The Project Board needs clear information to make decisions • It demonstrates proper use of the Issues procedure in PRINCE2
How Problem or Concern Works
When a Problem or Concern is identified:
1. Capture - The issue is recorded in the Issue Register 2. Examine - The Project Manager assesses the impact and options 3. Propose - Possible solutions or responses are identified 4. Decide - A decision is made on how to proceed (may require escalation) 5. Implement - The agreed action is carried out
The Project Manager handles most Problems or Concerns within their tolerance levels. If the issue threatens project tolerances, it must be escalated to the Project Board.
Distinguishing Problem or Concern from Other Issue Types
• Request for Change - A proposal to modify a baseline (scope, cost, time) • Off-Specification - A product that doesn't meet its specification or is forecast to miss specification • Problem or Concern - Everything else that needs attention
Exam Tips: Answering Questions on Problem or Concern
Tip 1: When given a scenario, first eliminate whether it's a Request for Change or Off-Specification. If it's neither, it's likely a Problem or Concern.
Tip 2: Look for keywords in scenarios such as 'worried about', 'concerned that', 'uncertainty regarding', or 'potential difficulty with' - these often indicate a Problem or Concern.
Tip 3: Remember that stakeholder complaints or worries that don't involve changing baselines or quality failures are Problems or Concerns.
Tip 4: Questions may test whether you understand that Problems or Concerns are recorded in the Issue Register, not handled informally.
Tip 5: Be aware that resource issues, external dependencies causing worry, and concerns about risks materializing are typically classified as Problems or Concerns.
Tip 6: In multiple choice questions, the correct answer will often be the most generic issue type when the scenario doesn't specifically mention baseline changes or specification failures.
Common Exam Scenarios
• A team member expresses concern about meeting deadlines = Problem or Concern • A stakeholder is unhappy with communication frequency = Problem or Concern • External supplier may not deliver on time = Problem or Concern • Team morale is declining = Problem or Concern