Constraints Analysis in Project Risk Management

PMBOK v8 Definition

Assumption and constraint analysis is a tool and technique that explores the validity of assumptions and constraints to determine which pose a risk to the project. Threats may be identified from the inaccuracy, instability, inconsistency, or incompleteness of assumptions. Constraints may give rise to opportunities through removing or relaxing a limiting factor that affects the execution of a project or process.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions related to Risk Management and Identify Risks process. Questions test your ability to distinguish between assumptions (considered true for planning) and constraints (limiting factors), and to recognize that both can generate threats and opportunities. Expect scenario-based questions where you must identify which technique helps uncover risks from these sources.

Key Points to Remember (for the exam)

Main Input: Assumption log (project document containing all assumptions and constraints)
Main Output: Updates to risk register and risk report (when threats or opportunities are identified)
Key Tool: Assumption and constraint analysis (performed during Identify Risks process)
Common Confusion: Assumptions are not inherently risks—they become risk sources when they are inaccurate, unstable, inconsistent, or incomplete
Dual Nature: Constraints can create threats (limitations) OR opportunities (when removed or relaxed)
Process Location: Part of Identify Risks process in Project Risk Management Knowledge Area
Exam Tip: Always check the assumption log first when a question involves risk identification from planning uncertainties

Typical PMI Exam Example

A project manager reviews the assumption log and discovers that the assumption "key vendor will deliver materials by March 1" is based on outdated market data. Using assumption and constraint analysis, the PM identifies this inaccuracy as a potential threat to the schedule and adds it to the risk register. This scenario tests your understanding of how assumption analysis feeds risk identification.

PMI Exam Traps

Trap: Treating all assumptions as risks from the start Reality: Only inaccurate, unstable, inconsistent, or incomplete assumptions become risk sources
Trap: Confusing constraints with assumptions Reality: Constraints are fixed limitations (budget, schedule, scope); assumptions are beliefs accepted as true for planning
Trap: Thinking constraints only produce threats Reality: Constraints can also create opportunities when limiting factors are removed or relaxed
Trap: Assuming assumption analysis is a one-time activity Reality: The assumption log is continuously updated throughout the project and reviewed during Monitor and Control Project Performance

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Risk Register	Output of Identify Risks	Assumption analysis directly updates the risk register with new threats/opportunities
Assumption Log	Input to Identify Risks	Primary document where assumptions and constraints are recorded and analyzed
Theory of Constraints (TOC)	Complementary concept	TOC focuses on improving system performance by identifying and managing the single constraint limiting throughput
Monitor and Control Project Performance	Ongoing process	Assumption log is reviewed during this process to validate assumptions and identify new risks

Quick Review Questions

During which process is assumption and constraint analysis performed?
What are the four characteristics of assumptions that can generate threats?
How can constraints potentially create opportunities for a project?
Which project document serves as the primary input for assumption and constraint analysis?
What is the difference between an assumption and a constraint in project management?

PMBOK v8 Reference

Section 5 – Tools and Techniques (pages 147-148) - Assumption and Constraint Analysis within Identify Risks process, Project Risk Management Knowledge Area