Assumption – A factor in the planning process that is considered to be true, real, or certain without proof or demonstration for the purposes of planning.
Key Characteristics:
- Unverified factors: Believed to be true but not confirmed
- Planning enablers: Allow project planning to proceed despite uncertainties
- Risk sources: Assumptions that prove false can become risks or issues
- Documentation required: Should be explicitly recorded and tracked
- Validation needed: Should be verified as the project progresses
Common Types of Assumptions:
- Resource availability: Key team members will be available when needed
- Technology: Existing systems will continue to function as expected
- External factors: Regulatory environment will remain stable
- Stakeholder behavior: Customers will provide timely feedback
- Environmental: Weather conditions will be normal for outdoor projects
Examples:
- “The client will provide requirements within 2 weeks”
- “The development team will have access to the production environment”
- “Budget approval will be received by the planned start date”
- “Third-party vendors will deliver on schedule”
- “No major organizational changes will occur during the project”
Best Practices:
- Document clearly: Record all assumptions in the project charter and plans
- Validate regularly: Check assumptions throughout the project lifecycle
- Assign ownership: Someone should be responsible for tracking each assumption
- Risk assessment: Evaluate what happens if assumptions prove false
- Communication: Share assumptions with all relevant stakeholders
Relationship to Risk:
- Assumptions that prove false often become risks or issues
- Should be analyzed for potential impact if they don’t hold true
- May require contingency planning
Documentation Locations:
- Project Charter
- Project Management Plan
- Risk Register
- Assumptions Log
Related Terms:
- Constraint: Limiting factors that are known to be true
- Risk: Uncertain events that may impact project objectives
- Issue: Current problems that need to be addressed
- Dependency: Relationships between project activities
Management Process:
- Identify: Capture assumptions during planning
- Document: Record in appropriate project documents
- Validate: Test assumptions as information becomes available
- Monitor: Track throughout project execution
- Update: Revise plans when assumptions change
