A document or tool called a “assumption log” is used in project management to keep track of and manage the assumptions that are made during a project. Assumptions are statements that are taken to be true even though there is no proof to back them up. People make assumptions when they don’t have enough information or data or when they need to make quick decisions.
An assumption log usually has a list of all the assumptions that have been made during the project, along with the date, the name of the person who made the assumption, and the reason for the assumption. The assumption log might also have a description of how each assumption might affect the project and a plan for how to validate or test each one.
The goal of an assumption log is to help project teams find and keep track of assumptions throughout the project’s lifecycle, and to make sure that these assumptions are validated or tested as soon as possible. By keeping track of assumptions in a structured way, project teams can reduce the chance of making wrong assumptions and make better decisions based on accurate and reliable information.
The assumption log is usually looked at and updated at regular intervals during project meetings. It is used to help make decisions and manage risks. The log can also be used to make it easier for project team members, stakeholders, and other people involved in the project to talk to each other and work together.
Usage
It is used inproject planning / risk management
