Register now or log in to join your professional community.
All projects need a close section. Most projects that do not close correctly usually have many scope creeps or undefined requirements that creep in. Ensure you know what you are delivering with tight control at the start and during the project. Close the project by presenting your deliverables VS the requirements and scope and you should be able to close your project.
I found that project closure is rarely included in the project plans.
If you mean that project delays have been creeping during execution, I suggest that is a failure on the project manager's part. He/she should identify any deviations as soon as they start and decide on how to fix the problem and seek management and customer approval if the fix is going to cause any change in the project goals, cost, or time line.
Yes , from your1st day you have to identify yourscope & stake holders ,, give them enough time to study collect all the recommendations and you have to tak approval on your scope and deliverables in certain time and cost within the proper quality required
Improper closing of the project because we don't specify all deliverables from the begining (before execution). Deliverables could be any thing such as hardware, software, licenses, services, etc.
PM is responsible to make a list of all deliverables will be handed over to the customer so he can get the final approval/sign off.
There could be many reasons based on the environment, team involved, type of project etc, however to look at it from project management perspective the key things to make sure projects gets closed are 1. Defining Success criteria of the project2. Having RTM(Requirement tracebaility matrix) and importantly3. Having a lifecycle and defining phases and gates and deliverables expected from each of them. As a PM it's important to verify the scope and agree on every milestone and get the required sign of.