A record that keeps track of the assumptions made during a job is called an assumption log. Assumptions are things that are thought to be true but haven’t been checked. They can have a big effect on how a job turns out. The goal of an assumption log is to keep track of these assumptions, make sure they are still true as the project goes on, and find any risks that might be related to them. Here are some of the most important parts of a log of assumptions:
1. Give a clear account of the idea and why you think it is true.
2. Assumption owner: Give the job of making sure the assumption is true to a specific person or team.
3. Assumption validity: Show the current state of the assumption and say whether or not it has been proven or disproven.
4. Do an effect study to see what might happen to the project if the theory turns out to be wrong.
5. Plan B: Come up with a plan B to deal with the possible risks that come with the idea.
6. Review and update: Make sure that the assumption log is regularly reviewed and updated so that all assumptions can be tracked and checked throughout the project.
By keeping an assumption log, project teams can find and deal with possible risks ahead of time, avoid making mistakes that cost a lot of money, and make sure that the project results are in line with business goals.
