You and several of your key team leaders are really struggling with estimating the overall cost of the project. What is the most probable cause for this?

D. problems with the overall schedule.

Option A:

If the scope is clear and  with well defined with boundaries, cost estimation is easier for all.

My answer is for option (A)

this is confusion due to lack of study and experience , i am inclined to answer A. initial poor scope definition

Thank you for the invitation. My answer is A

Thanks for invitation

Option A  

both (A) and (D) are correct answers and it varies from project to project. Project scope and technical specifications together with bid clarifications does not automatically lead to construction but it has to go through a detailed engineering phase where there are several engineering comments. Initial submittals based on contract documents will normally be rejected and goes through progressive modifications and refinement to meet project objectives. The baseline schedule can always be constructed using similar past projects schedule and expert opinion but needs to be updated for perfection in engineering. Continuous improvements and learnings is the way forward with recovery plans for delays in schedule if any. There is nothing perfect or absolute in this world. Operations normally may not like this as they are defensive about existing conditions and existing models and the top management demands strict adherence of master schedule and budget. Finally, there are different perspectives which needs to be balanced and you need a supportive management who understands the need for change and progression together with responsible and responsive suppliers/ vendors collaborating and holistically aligned and prioritized on all important issues and fast coordination/ problem solving/ negotiation

Option A -  the  poor scope definition causes a real struggling of the estimating of the Overall cost.

Thanks for the invitation , I will go with option A - Initial poor scope definition.

A. initial poor scope definition

D. problems with the overall schedule.

If we look at the out put from define scope and develop schedule processes

For define scope process,  the out puts are project scope statement and project documents updates.

For develop schedule process,  the out put from the process (project schedule, schedule baseline)

But the last process in time management is create WBS which is the out Scope baseline. which is not mentioned in the options.

According to options A and D in A the scope is not yet created so you cant judge it, but in D its created and the schedule is created sequenced and estimated. 

So I go with D (it seems more reasonable among the options)

1) Taking more time for tender analysis

2) No proper schedule 

3) Confusion in drawings and specifications

4) Big project