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...
Earl LewisSenior Project Manager| University of UtahSalt Lake City, Ut, United States
Assumptions need to be documented somewhere. Depending on the type of project you're running, assumptions could be in the requirements. Others might not seem like a requirement, but still needs to be documented somewhere, so a log of some sort is as good a place to do that as any. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Apr 18, 2018 5:37 PM
Replying to 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...
Kiron
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. Saving Changes...
The Assumption log is related to risks because it also lists constraints, and nearly all risks (if not all) are associated with scope, time, cost and quality.
...
1 reply by Rami Kaibni
Apr 18, 2018 6:53 PM
Rami Kaibni
...
True and not only for Risk, but also for Scheduleing as some assumptions might restrict certain sequencing of activities and impose risk at the same time.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Apr 18, 2018 6:50 PM
Replying to Sante Delle-Vergini, PhD
...
The Assumption log is related to risks because it also lists constraints, and nearly all risks (if not all) are associated with scope, time, cost and quality.
True and not only for Risk, but also for Scheduleing as some assumptions might restrict certain sequencing of activities and impose risk at the same time. Saving Changes...
Utkarsh Ajay ShahAssistant Manager| L&T Hydrocarbon Engineering Ltd.Mumbai, Maharahstra, India
Coming from EPC industry, assumptions log serves as a guiding bible for the considerations we take into account while bidding for the project. these considerations are of nature that impact the project deliverable either by directly increasing the cost or in terms of equipment criteria which may lead to increase in cost of delivery schedule. So yes, we use assumption logs all the time in the organisation i work . Assumptions log becomes a document that states clearly what has been taken or not taken into consideration.And this helps the PM when the team members who worked during bidding are not with the project or organisation when the project has been awarded and is under execution. Saving Changes...
Kathy CastleAuthor at https://www.projectcubicle.com/| FreelanceTx, United States
I have been using for many years. Because assumption analysis is a part of risk management process. If it is not made properly analyze, it may affect the projects health.The project management plans need to changed if assumptions are verified wrong. Saving Changes...
Shelby MengProject Manager| Electrolux China Home Appliances Company LimitedNanjing, China, Mainland
I use assumptions in Project Charter at project beginning , and as condition for project Gantt chart update. Saving Changes...
Ryan ClarkeProject Manager / Business Analyst| LivingWorksCalgary, Alberta, Canada
Apr 18, 2018 5:37 PM
Replying to 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...
Kiron
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.
An assumptions log is completely superfluous. Saving Changes...
Assumptions may appear in "other documents" but if someone wants to view all assumptions recorded in a central place, particularly as they get added/edited/deleted, then they would need an Assumption Log. Saving Changes...
Beverly KeeblerIT Project Manager| Anexinet CorporationBuford, Ga, United States
Apr 18, 2018 2:35 PM
Replying to Rami Kaibni
...
I include the assumptions log along with the estimate for the project as an attachement.
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... Saving Changes...
Community Champion
