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...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I fully support this, in theory and in practice: "those who do not are likely not experiencing very effective risk management.." which was written by @Kiron. In some comments in this post I think is a confusion about what assumption log is. Call it as you want but you must have a place where you have all the assumptions listed and you have to validate it as part of your project management activities. And by the way, something obvious, but restrictions and assumptions are not the same. Saving Changes...
Wan-Phek HowCareer and Project Management Coach| Wan How ConsultingBurnaby, British Columbia, Canada
Thank you Sante for introducing the concept of an assumption log. This got me thinking about a hypothesis column within the assumption log to test the assumption (I see that Sergio has already talked about validating the assumption which I suppose is the same thing.)
Then after the hypothesis is proven true or false, there could be follow-up decisions or actions, perhaps to test another version of the hypothesis.
Hoping this makes sense. What do you all think? Saving Changes...
I work in pharma and I've never used an assumption log but a lot of assumptions usually go into the risk register and risk management plan Saving Changes...
