Skip to content
PMPCAPM

Closing Process Group

The Closing Process Group consists of processes performed to formally complete or close the project, phase, or contract.

Share:

Explanation

The Closing Process Group ensures that all project work is finished, deliverables are accepted, resources are released, and the project is formally closed. In the PMBOK Guide Sixth Edition, this group contains a single process: Close Project or Phase. Despite having only one process, closing involves significant activities including final deliverable handoff, lessons learned documentation, contract closure, resource release, and archiving project records.

Lessons learned are particularly important during closing. PMI emphasizes capturing what went well, what could be improved, and what was learned throughout the project. These lessons become organizational process assets that benefit future projects. Unfortunately, lessons learned are often neglected due to time pressure or the team's eagerness to move on to the next assignment.

Closing also involves administrative activities such as obtaining formal sign-off from the customer or sponsor that the deliverables meet acceptance criteria, ensuring all financial accounts are reconciled, and updating organizational records. Premature closure — ending a project without proper closing activities — can lead to unresolved issues, lost knowledge, and contractual disputes.

Key Points

  • Formally completes the project, phase, or contract
  • Includes deliverable acceptance, lessons learned, and resource release
  • Archives project records as organizational process assets
  • A project can be closed whether completed successfully or terminated early

Exam Tip

Projects that are cancelled or terminated still go through the Closing Process Group. The exam may present a scenario where a project is ended early and ask what should happen next — the answer is to perform closing activities.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Predictive Life Cycle (Waterfall)

A predictive life cycle is a plan-driven approach where the project scope, schedule, and cost are determined early and changes are carefully managed.

Subsidiary Plans

Subsidiary plans are the individual management plans that are components of the overall project management plan, each addressing a specific Knowledge Area or management function.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Part of

PM Fundamentals & Frameworks

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.