I have run into some PM's that rarely if ever use one. Of course many use a risk log, even issue long, but what about an assumption log? Saving Changes...
I use assumptions in Risk Management that mostly required follow-up correction action and validation in order to determine whether or not they will impact the project. Many assumptions may actually be project risks, or may become risks during the life of the project. Saving Changes...
I populate an assumption log for every project. Unless you have a very good memory, the assumptions log helps you remember why certain decisions were made. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I include the assumptions log along with the estimate for the project as an attachement.
...
2 replies by Ayat Rezaeifar and Beverly Keebler
Apr 18, 2018 2:46 PM
Ayat Rezaeifar
...
Very good point Rami. I also expect to see an assumptions/clarifications log from estimating team when handing over a new project.
Nov 10, 2020 9:51 PM
Beverly Keebler
...
When you say "estimate for the project", do you mean a quote? A rate card? As a project manager, how much of the pre-kickoff/pre-sales process are you generally a part of?
I am trying to find the right balance and have found it difficult to follow all the PMI-recommended project initiation/planning processes unless I am involved quite early on in the process - but my organization believes that a PM should only come into the picture once a PO is received and a kickoff call needs to be scheduled...
I include the assumptions log along with the estimate for the project as an attachement.
Very good point Rami. I also expect to see an assumptions/clarifications log from estimating team when handing over a new project. Saving Changes...
Ryan ClarkeProject Manager / Business Analyst| LivingWorksCalgary, Alberta, Canada
I've never actually used one for a design/construction project. I guess I never really assume anything that isn't already stated somewhere else, like the program or statement of requirements. Reports may have assumptions stated but not usually in the form of a log. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
Normally I use assumption log in every project and it will be reviewed regularly to either verify the assumption, so it can be closed or provide a mitigation if the assumption turns out to be incorrect. These assumptions will also be reflected in the risk log and reviewed at regular risk meetings. Saving Changes...
those who do not are likely not experiencing very effective risk management...
Kiron
...
1 reply by Ryan Clarke
Apr 18, 2018 4:31 PM
Ryan Clarke
...
How so? Just because you don't put assumptions in a log, doesn't limit your effectiveness to manage risk. Tools are meant to help PM's, not do their jobs for them.
Saving Changes...
Ryan ClarkeProject Manager / Business Analyst| LivingWorksCalgary, Alberta, Canada
Apr 18, 2018 4:11 PM
Replying to Kiron Bondale
...
Sante -
those who do not are likely not experiencing very effective risk management...
Kiron
How so? Just because you don't put assumptions in a log, doesn't limit your effectiveness to manage risk. Tools are meant to help PM's, not do their jobs for them.
...
1 reply by Kiron Bondale
Apr 18, 2018 5:37 PM
Kiron Bondale
...
(Unvalidated) Assumptions are a common source of risks - if we don't surface assumptions and capture them somewhere, they will get forgotten and we won't remember to validate them in a timely fashion to avoid the issues that will occur when they get invalidated...
How so? Just because you don't put assumptions in a log, doesn't limit your effectiveness to manage risk. Tools are meant to help PM's, not do their jobs for them.
(Unvalidated) Assumptions are a common source of risks - if we don't surface assumptions and capture them somewhere, they will get forgotten and we won't remember to validate them in a timely fashion to avoid the issues that will occur when they get invalidated...
Kiron
...
2 replies by Rami Kaibni and Ryan Clarke
Apr 18, 2018 6:08 PM
Rami Kaibni
...
I agree with Kiron.
High Levels Assumptions contained into the Project Charter / Business Case along with other assumptions done during the Estimation should be documented, taken into considration during initial risk assessment and revisited frequently for validation purposes.
This is very important no matter how big, complex, or small the project is.
Apr 19, 2018 11:07 AM
Ryan Clarke
...
What I am saying is that assumptions shouldn't need to be put in a formal log as they are either captured in the project statement of requirements or other documents, or the actual item being assumed shouldn't be assumed, especially if that assumption is not validated. Assuming something that has not been validated is a risk in itself.
Community Champion
