Project Value Delivery: Close Project or Phase Process

Project Value Delivery: Close Project or Phase Process

PMBOK v8 Definition

The Close Project or Phase process involves finalizing all activities related to both successful and unsuccessful projects, phases, releases, iterations, or contracts. The primary benefits include archiving project or phase information, completing planned work, and releasing organizational resources for new projects. This process also includes confirming the extent to which value or the capability to deliver value has been achieved.

Process Group: Closing Process Group
Knowledge Area: Project Integration Management

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about project closure activities, value confirmation, and organizational resource management. Questions typically test your understanding of what happens during closure (beyond just delivering the product), the distinction between successful and unsuccessful project closure, and the critical step of confirming value delivery before finalizing the project.

Key Points to Remember (for the exam)

  • Primary Benefits: Three specific benefits—archiving project/phase information, completing planned work, and releasing organizational resources for new projects
  • Value Confirmation: The process explicitly includes confirming the extent to which value or the capability to deliver value has been achieved (not just deliverables)
  • Applicability: Applies to both successful AND unsuccessful projects, phases, releases, iterations, or contracts
  • Main Input: Project management plan, project documents, accepted deliverables, business documents, agreements, procurement documentation, and organizational process assets
  • Main Output: Project documents updates, final product/service/result transition, final report, and organizational process assets updates
  • Key Tool: Expert judgment, data analysis (regression analysis, trend analysis, variance analysis), and meetings
  • Common Confusion: Confusing Close Project or Phase with the process of simply delivering the final product—closure includes archiving knowledge, releasing resources, and confirming value

Typical PMI Exam Example

A project manager is closing a software development project that was completed on time and within budget. During the Close Project or Phase process, the project manager must confirm that the project achieved the expected business value. What is the PRIMARY benefit of this confirmation step?

Answer: It ensures the project delivered value or the capability to deliver value, which is a mandatory part of the closure process per PMBOK v8.

PMI Exam Traps

  • Trap: Thinking Close Project or Phase only applies to successful projects

  • Reality: It applies to BOTH successful and unsuccessful projects, phases, releases, iterations, or contracts

  • Trap: Assuming closure is complete once deliverables are accepted

  • Reality: Closure requires archiving information, completing planned work, releasing resources, AND confirming value achievement

  • Trap: Confusing Close Project or Phase with the Control Procurements process

  • Reality: Close Project or Phase is about overall project closure; procurement closure is a separate process within the Closing Process Group

  • Trap: Believing value confirmation happens only at the end of the project

  • Reality: Value can be realized throughout the project, at the end, or following completion—but closure confirms the extent achieved

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Initiate Project or PhaseOpposite processInitiation authorizes resources; closure releases them back to the organization
Project CharterInput/OutputProject charter authorizes the project; closure confirms value against business case
Organizational Process AssetsOutput of closureLessons learned, project archives, and historical information are updated during closure
Value DeliveryCore principleClosure confirms value achievement—this is a key PMBOK v8 emphasis on value over just outputs
Release ResourcesBenefit of closureResources are formally released for new projects or operations—tested as a primary benefit

Quick Review Questions

  1. What are the three primary benefits of the Close Project or Phase process?

  2. Does the Close Project or Phase process apply to unsuccessful projects? Why or why not?

  3. What must be confirmed during the Close Project or Phase process beyond completing planned work?

  4. How does the Close Project or Phase process relate to releasing organizational resources?

  5. What is the difference between closing a phase and closing the entire project?

PMBOK v8 Reference

Section 2.1.6.9 – Close Project or Phase
Figure 2-12 – Close Project or Phase Inputs, Tools and Techniques, and Outputs
Section 2 – Project Management Performance Domains