Do I need to provide the project progress plan at the project meeting?

At today's project meeting, I presided over the meeting as a project manager. At the meeting, I was asked when to complete the Code, when to complete the test, and when to release it, the product manager and several colleagues from several non-technical departments asked this question. I can understand it, but my supervisor actually wants to confirm these time points before the project meeting. Although it is rough, this allows you to know the duration of the entire project, but I think this approach is inappropriate or even incorrect.

 

First of all, I think this is only a project meeting to show that this project has been started. Generally, I only announce the time and progress of writing UC and system design at the project meeting, because of this good estimation, the progress plan of the entire project is generally estimated after the UC and system design review. The UC and system design are not completed, and the subsequent progress plan will be difficult to estimate, how can I estimate the workload even if the technical solution is not determined?

 

This will only waste more work time in the early stage. If you rashly announce the project progress plan, it will mislead other members of the project team, they will think that this is the project schedule. In this case, I would rather tell them the project schedule later, which will be more accurate and avoid further explanation.

 

Of course, it should be noted that the project I refer to here is only for internal projects of our company. If it is an externally-targeted project, in order to estimate the project cost, in the early stage of project initiation, We need to estimate the workload.

 

I don't know what you think. Welcome to discuss it!