There are several pieces of information that are not clear or are not necessary to be available with clarity while we go through the project. We assume and progress.
In most cases, it is done at the beginning of the project where we outline the basic assumptions and as we dive into the project we keep updating the assumptions in Assumption Log.
These details will then be included in the project charter and presented at a high level. During the course of the project, lower-level activity and task assumptions are formed, such as those concerning the following areas.
- Technical Requirements
- Estimations,
- Schedule
- Risks / Hazards.
During the whole life cycle of the project, the assumption log is where all of the project’s assumptions and limitations are recorded.
Key Points
– The Assumption Log acts as a journal for all of the “what-ifs” in a project.
– It’s a place where you put down everything you think is true but aren’t sure about.
– Consider it a record of estimations or estimates on which the project is based.
– It records the concepts or conditions on which the project is based but which may change in the future.
– It’s similar to making weather predictions—predictions that might effect your plans but may not always come true.
