5.5 Issues, Risks, Assumptions, and Constraints
Key Takeaways
- An issue is a current problem that is actively affecting the project, while a risk is an uncertain future event that may or may not occur
- Assumptions are factors considered true, real, or certain without proof — they must be documented, validated, and monitored
- Constraints are limiting factors that restrict the project team s options, such as budget limits, regulatory requirements, or fixed deadlines
- The issue log tracks identified issues, their priority, assigned owners, and resolution status throughout the project
- The assumption log documents project assumptions and constraints so they can be validated and monitored as the project progresses
Issues, Risks, Assumptions, and Constraints
One of the most frequently tested CAPM concepts is the distinction between issues, risks, assumptions, and constraints. Understanding these four concepts and how they relate to each other is critical.
Key Definitions
| Concept | Definition | Timing | Example |
|---|---|---|---|
| Issue | A current problem affecting the project | Happening NOW | "The lead developer resigned yesterday" |
| Risk | An uncertain future event with positive or negative impact | May happen LATER | "The lead developer might resign" |
| Assumption | A factor believed to be true without verification | Believed true NOW | "The lead developer will stay for the project duration" |
| Constraint | A limiting factor that restricts options | Fixed limitation | "The project must be completed by December 31" |
Issues vs. Risks
The most important distinction is between issues and risks:
| Aspect | Issue | Risk |
|---|---|---|
| Timing | Has already occurred | May occur in the future |
| Certainty | Certain — it is happening | Uncertain — it may or may not happen |
| Response | Requires immediate action | Requires a planned response strategy |
| Documentation | Issue log | Risk register |
| Management | Issue resolution process | Risk management process |
| Example | "Budget overrun of 15% discovered" | "Budget may overrun by 15%" |
Exam Tip: A risk becomes an issue when it actually occurs. For example, "the vendor may deliver late" (risk) becomes "the vendor delivered late" (issue). The planned risk response should be activated, or a workaround must be implemented.
Assumptions
Assumptions are factors that are considered true, real, or certain without proof or demonstration. They are inherently risky because if an assumption proves false, it can significantly impact the project.
Managing Assumptions
- Identify assumptions during planning
- Document them in the assumption log
- Validate assumptions as soon as possible
- Monitor throughout the project for changes
- Respond when assumptions prove invalid
Common Project Assumptions
- Key resources will be available when needed
- Technology platforms will be compatible
- Stakeholders will be available for reviews
- Regulatory requirements will not change
- Vendor will deliver on schedule
- Team has the required skills
Assumptions and Risks
Unvalidated assumptions are a major source of project risk:
- Assumption: "The API from the vendor will be compatible with our system"
- Risk if false: Integration will require significant rework, delaying the project
- Action: Validate early through a proof of concept
Constraints
Constraints are limiting factors that restrict the project team's options and affect how the project is planned and executed.
Types of Constraints
| Type | Examples |
|---|---|
| Time | Fixed deadline, regulatory milestones |
| Cost | Budget ceiling, funding limitations |
| Scope | Mandatory features, regulatory requirements |
| Quality | Industry standards, customer specifications |
| Resource | Limited staff, specific skill requirements |
| Technology | Must use specific platforms or tools |
| Regulatory | Legal compliance, permits, licenses |
| Organizational | Policies, procedures, governance |
Managing Constraints
Unlike risks and issues (which you try to resolve), constraints are typically accepted and managed within:
- Identify all constraints during planning
- Document in the assumption log alongside assumptions
- Plan around constraints — they define your boundaries
- Communicate constraints to stakeholders
- Monitor for changes — a constraint may be lifted or new ones may appear
The Assumption Log
The assumption log is the document that records both assumptions and constraints. It typically includes:
| Field | Description |
|---|---|
| ID | Unique identifier |
| Type | Assumption or constraint |
| Description | Detailed statement |
| Owner | Person responsible for monitoring |
| Date Identified | When it was documented |
| Status | Open, validated, invalidated, closed |
| Impact if Invalid | What happens if the assumption is wrong |
| Action Required | Steps to validate or manage |
The Issue Log
The issue log tracks current problems and their resolution:
| Field | Description |
|---|---|
| Issue ID | Unique identifier |
| Description | What the issue is |
| Impact | How it affects the project |
| Priority | Urgency and importance |
| Owner | Person responsible for resolution |
| Date Raised | When it was identified |
| Status | Open, in progress, resolved, closed |
| Resolution | How the issue was resolved |
What is the PRIMARY difference between an issue and a risk?
An assumption that proves false during project execution is BEST described as:
Which document records both assumptions and constraints?