Appearance
5.3 Constraints & Assumptions
Every project operates within a set of invisible walls. Identifying these early is critical for managing stakeholder expectations and project risk.
🏗️ Definitions: Know the Difference
On the exam, you must distinguish between what is Fact (Constraint) and what is Belief (Assumption).
Constraints
"The Walls"
Limiting factors that must be obeyed. They are not negotiable.
- Fixed Deadlines
- Approved Budgets
- Safety Regulations
- Physical Limits
Assumptions
"The Foundations"
Factors held to be true for planning purposes without proof.
- Resource Availability
- Tool Reliability
- Market Stability
- Team Skill Levels
🚦 Managing the Log
Both are documented in the Assumption Log, which is created during initiation.
- Assumptions are Risks: If an assumption (e.g., "The server will arrive Tuesday") proves false, it becomes an issue or a risk realized.
- Constraints are Boundaries: They define the "Triple Constraint" (Scope, Schedule, Cost) within which you must innovate.
- Active Monitoring: The PM reviews the Assumption Log during every status meet or sprint planning to verify if beliefs are still valid.
🛠️ 2026 Focus: Virtual Constraints
In 2026, we add Digital Constraints:
- Data Privacy (GDPR/CCPA): Non-negotiable legal walls.
- API Latency: Physical constraints of modern global software.
- Asynchronous Time Gaps: The limitation of working across 12-hour zone differences.
📝 Exam Insight: If a planner makes a decision based on a "belief" that resources will be available, and they aren't, the root cause is a failed assumption. Never treat assumptions as facts without validation.