Assumption
An item the team treats as true or certain during planning to move forward, even though it has not been proven or demonstrated.
Key Points
- Assumptions are accepted as true without evidence at the time of planning.
- They are documented in an assumption log and should have an owner and review date.
- Every assumption introduces uncertainty and potential risk if it proves false.
- Common areas include resource availability, schedules, technology performance, and external dependencies.
Example
The project plan assumes the vendor's API will be available by May 1. If the API is late, the schedule slips; if it arrives on time, the plan remains valid.
PMP Example Question
During planning, the team records statements such as "the test environment will be ready by June 10" to proceed with scheduling. What are these statements called?
- Assumption
- Constraint
- Risk
- Requirement
Correct Answer: A — Assumption
Explanation: It is something the team accepts as true to plan, without proof at the time. Constraints limit choices, risks are uncertain events, and requirements define needs.