Close Project or Phase

Sensei Short Scroll 49 Closing Process Group

Introduction: Why This Matters

Every project or phase must be finalized in a structured way. The Close Project or Phase process ensures that all work is completed, deliverables are accepted, and the project is formally closed. Without formal closure, projects may leave behind unresolved issues, incomplete documentation, or wasted opportunities for learning.

On the PMP exam, this process is often tested through situational questions about formal acceptance, lessons learned, archiving records, and closing contracts. In practice, proper closure provides accountability, releases resources, and strengthens organizational knowledge for future projects (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To finalize all project activities across all process groups and obtain formal closure of the project or a project phase.

Key Objectives:

Obtain stakeholder sign off and formal acceptance of deliverables.
Verify that all requirements and scope are complete.
Close out contracts and confirm vendor obligations are fulfilled.
Archive project documents and data.
Conduct lessons learned sessions.
Release project resources.
Celebrate project completion to acknowledge contributions.

Overview

Close Project or Phase brings together everything that happened on the project and closes it out in a disciplined way. You confirm completion, document results, and transition the work to ongoing operations or the next phase.

Verification: Confirm that scope, quality, and contractual obligations are satisfied.
Formal acceptance: Obtain documented sign off from key stakeholders.
Documentation and archiving: Finalize reports, records, and lessons learned, then store them in organizational repositories.
Resource and stakeholder closure: Release people, close communication channels, and celebrate completion.

Characteristics

Formality: Emphasizes documented acceptance, closure records, and compliance with organizational standards.
Holistic: Touches all knowledge areas, from scope and cost to risk, procurement, and stakeholder engagement.
Knowledge focused: Captures lessons learned and feeds them back into organizational process assets.
Transition oriented: Ensures a smooth handoff of deliverables to operations or the next phase.

Inputs, Tools and Techniques, Outputs (ITTOs)

Inputs

Project management plan (scope, quality, resource, procurement plans).
Project documents (assumption log, issue log, risk register, lessons learned).
Accepted deliverables (from Validate Scope).
Business documents (business case, benefits management plan).
Agreements (contracts, vendor SLAs).
Organizational process assets (closure procedures, templates, repositories).

Tools and Techniques

Data analysis: Document analysis, regression analysis, and trend analysis to evaluate performance.
Meetings: Lessons learned workshops, closure meetings with stakeholders, vendor finalization sessions.
Expert judgment: Input from PMO, legal, procurement, and senior leadership.
Audits: Closure audits to confirm compliance with policies and standards.

Outputs

Final product, service, or result transition to operations.
Final report documenting performance, variances, and outcomes.
Updates to organizational process assets (templates, repositories, knowledge base).
Project or phase closure documentation.
Lessons learned repository updates.
Release of resources.

Close Project vs Close Phase

Close Project: Conducted when the entire project is finished or terminated. Involves final acceptance, resource release, and archiving.
Close Phase: Conducted at the end of a major phase in multi phase projects (for example, design phase). Provides structured sign off before starting the next phase.

Distinguishing between phase closure and project closure is a common PMP exam question.

Practical Example: Airport Terminal Expansion

Context: A city completes an airport terminal expansion project.

Close Project activities:

Acceptance: City council and aviation authority sign off on deliverables.
Contracts: Vendor agreements for construction and technology installations are finalized and closed.
Final report: Documents show the project finished within 2 percent of budget and three weeks ahead of schedule.
Knowledge capture: Lessons learned session identifies success in early contractor engagement and challenges in stakeholder communication.
Transition: Operations team assumes control of the terminal.
Celebration: Ceremony held to recognize the project team and stakeholders.

Outcome: The project concludes formally, with all obligations completed, stakeholders satisfied, and knowledge preserved.

Common Pitfalls

Skipping formal acceptance

Pitfall: Assuming stakeholders accept deliverables.
Prevention: Always require documented sign off.

Incomplete contract closure

Pitfall: Leaving vendor obligations unresolved.
Prevention: Confirm all deliverables and payments are finalized.

Neglecting lessons learned

Pitfall: Failing to capture insights.
Prevention: Conduct lessons learned sessions and update OPAs.

Delayed resource release

Pitfall: Holding staff after project completion.
Prevention: Release resources promptly.

Sensei Tip : On the exam, when you see that all deliverables are completed and accepted, think closure steps: obtain formal sign off, archive records, close contracts, update lessons learned, and release resources. Treat closure as a disciplined checklist, not a single action.

Exam Alert : A common trap is to skip formal acceptance or contract closure when the project is canceled or finished early. Even canceled projects still require closure activities, including documenting lessons learned and updating organizational process assets.

Exam Lens

Patterns on the PMP Exam:

Questions often ask what to do when a project is finished. Correct answers include formal acceptance, archiving records, closing contracts, releasing resources, and updating OPAs.
Lessons learned are collected throughout the project but are finalized and stored during closure.
Closure applies whether a project is completed, canceled, or terminated early.

Sample Question

Question: A project has been completed, and all deliverables are accepted. What should the project manager do next?

Release resources immediately.
Archive project records and close contracts.
Conduct lessons learned and update OPAs.
Perform all of the above as part of closure.

Correct Answer: D. Closure involves releasing resources, archiving records, closing contracts, and updating lessons learned and OPAs as a complete set of activities.

Quick Recap Table

Concept	Description	Exam Watch Point
Close Project or Phase	Finalizes the project or a phase.	Requires formal acceptance and documentation.
Accepted Deliverables	Input to closure, verified in Validate Scope.	Must be signed off before closure.
Final Report	Documents performance, variances, and outcomes.	Frequently tested for purpose and content.
Lessons Learned	Finalized and added to organizational process assets.	Collected throughout but completed in closure.

Key Takeaways

Close Project or Phase provides formal closure, acceptance, and accountability.
Activities include contract closure, lessons learned, archiving, and resource release.
Outputs include final report, final product transition, and updates to organizational process assets.
On the PMP exam, closure always requires acceptance, documentation, and lessons learned.
In practice, closure supports organizational maturity and celebrates achievement.

Next Step

With Close Project or Phase complete, the Closing Process Group is fully covered and you can zoom out to review how all process groups connect across the project life cycle.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Close Project or Phase