
Project Closure in Predictive Approaches
PMBOK v8 Definition
For project closure, the project manager should ensure that all work is completed and that the objectives are met by reviewing the project management plan. Key activities for administrative closure in predictive approaches include satisfying completion or exit criteria by ensuring all documents and deliverables are updated and all issues are resolved.
Why It Matters for the Exam
Project closure appears frequently in PMI exam questions testing your understanding of the final process group and administrative responsibilities. Questions typically present scenario-based situations where you must identify the correct closure activities, distinguish between administrative and contract closure, or recognize when closure is properly completed.
Key Points to Remember (for the exam)
- Primary Purpose: Ensure all work is completed and objectives are met by reviewing the project management plan
- Core Activity: Satisfying completion or exit criteria
- Critical Steps for Exit Criteria:
- Ensure all documents and deliverables are updated
- Ensure all issues are resolved
- Process Group: Closing Process Group
- Common Confusion: Administrative closure is NOT the same as contract closure; administrative closure focuses on internal documentation and deliverable acceptance
- Key Document: Project management plan is the reference document for verifying completion
Typical PMI Exam Example
A construction project has completed all physical work. The project manager reviews the project management plan and discovers three deliverables are not formally signed off. What should the project manager do first? Answer: Ensure all documents and deliverables are updated and all issues are resolved before satisfying exit criteria.
PMI Exam Traps
-
Trap: Thinking project closure only happens at the end of the project
-
Reality: Closure activities occur in the Close Project or Phase process, which can apply to phases as well
-
Trap: Confusing "completion criteria" with "success criteria"
-
Reality: Completion criteria are specific exit criteria for closure; success criteria measure overall project success
-
Trap: Assuming all issues must be resolved before closure
-
Reality: The PMBOK v8 explicitly states "all issues are resolved" as part of satisfying exit criteria
-
Trap: Believing the project manager alone performs closure
-
Reality: The project manager ensures closure activities happen but may coordinate with stakeholders
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Management Plan | Input to closure | Used to verify all work is completed and objectives met |
| Project Performance Domains | Framework context | Closure is part of the delivery domain |
| Deliverables | Output of execution | Must be updated and formally accepted before closure |
| Issues | Constraint to closure | Must be resolved before satisfying exit criteria |
Quick Review Questions
-
What document does the project manager review to ensure all work is completed during project closure?
-
What are the two key steps required when satisfying exit criteria in the Close Project or Phase process?
-
In predictive approaches, what is the primary responsibility of the project manager regarding project closure?
-
How does administrative closure differ from contract closure in predictive approaches?
-
What must be done with issues before project closure can occur according to PMBOK v8?
PMBOK v8 Reference
Section 2.1.6.9.1 - Predictive Approaches (Project Closure)