Close project process

Close project or phase is the process of finalising all activities across all project management process groups to formally complete the project or phase (PMBOK, Integration Management, Closing group). It confirms that all work is done, the product is accepted and information is archived.

Activities

1. Confirm completion of all work and deliverables against the project plan and scope baseline.
2. Obtain final acceptance from the customer or sponsor (formal sign-off).
3. Close procurements: settle contracts, make final payments, evaluate vendors.
4. Hand over the product, service or result to operations/support, with documentation, user manuals and training.
5. Administrative closure: collect, finalise and archive project records; update organisational process assets.
6. Release resources: reassign team members, return equipment, release facilities.
7. Financial closure: close accounts, prepare the final cost report, compare actual cost with budget.
8. Collect lessons learned and conduct a post-project (post-implementation) review.
9. Measure customer satisfaction and check benefits against the benefits realisation plan.
10. Celebrate and recognise the team.

Complete work -> Acceptance -> Handover
      -> Close contracts -> Archive -> Lessons learned
      -> Release team

Inputs, tools and outputs

Premature closure

If a project is cancelled early, closure still documents the state of the work completed and the reasons.

Importance

Prevents loose ends, gives the customer assurance, retains knowledge for future projects and frees resources.

Example: After finishing a school management software, the team conducts user acceptance, gives training, hands over the source code, pays the vendor, writes the lessons-learned report and disbands.