Process 49 of 49

Close Project or Phase

Finalizes all activities to formally complete the project or phase, producing the final report and transitioning the product to operations. It is the disciplined ending that captures value and learning.

Process Group Closing Knowledge Area Project Integration Management

Close Project or Phase formally concludes the work: confirming deliverables are accepted, settling contracts, releasing resources, archiving documents, capturing lessons learned, and transitioning the final product, service, or result to the customer or operations. The final report summarizes outcomes against objectives.

Close Project or Phase: key inputs and outputs
The key inputs feeding Close Project or Phase and the deliverables it produces — full ITTOs are listed below.

Closure is administrative but important: it confirms the project met its goals, frees up people and budget, and preserves knowledge for future projects. Phase closure applies the same discipline at the end of each phase, not just at project end.

Common pitfalls. Skipping closure when the team rushes to the next project; lessons learned that are never captured or reused; leaving contracts or resources formally open; and no confirmation that the intended benefits were actually realized.

Inputs, Tools & Techniques, and Outputs

Inputs

  • Project charter
  • Project management plan
  • Project documents
  • Accepted deliverables
  • Business documents
  • Agreements
  • Procurement documentation
  • Organizational process assets

Tools & Techniques

  • Expert judgment
  • Data analysis
  • Meetings

Outputs

  • Project documents updates
  • Final product, service, or result transition
  • Final report
  • Organizational process assets updates

← All PMBOK Processes