Curriculum
PMP® Exam Prep Mastery — Fall 2026
Founders Cohort Orientation
0/1
WEEK 1 – PMP FOUNDATION & PMI MINDSET
0/4 
WEEK 2 – People Domain (Leadership & Team Performance)
0/4 WEEK 3 – Process Domain (Planning & Scope Control)
0/4 WEEK 4 – Process Domain (Execution & Monitoring)
0/4 WEEK 5- Agile, Hybrid & Execution Approaches (Ways of Working)
0/4 WEEK 6 – Integration, Execution Flow & Decision-Making
0/5 WEEK 7 – Exam Strategy & Application Readiness
0/3 WEEK 8 – Final Calibration & Exam Readiness
0/2 Extras
0/3 Session 13 – Closing the Project: Transition, Knowledge Transfer & Benefits Realization
Closing the Project
Live session via Zoom · Meeting ID: 875 6602 9896 · Passcode: 958630
Questions between sessions: support@pmptrainingacademy.com
Session Overview
This is the last content lesson of the course. We cover everything PMI expects you to know about closing a project or phase: the closure types, the 8-step closure checklist, benefits realization and the benefits owner, and knowledge transfer including lessons learned. We also apply each concept to the Shawpe Lifestyle Centre (SLC) project and work three exam-style practice questions.
| Hour | Topic | ECO Ref |
|---|---|---|
| Hour 1 | 6A: Project/Phase Closure — types, checklist, transition, SLC scenario | ECO 1.8 · 2.17 |
| — | 6B: Benefits Realization — timing, benefits owner, measurement | ECO 3.2 |
| Break | 10-minute break | — |
| Hour 2 | 6C: Knowledge Transfer — tacit vs. explicit, lessons learned register vs. repository | ECO 2.16 |
| — | Practice Questions (3) with full debrief | All |
6A · Project/Phase Closure
The Three Closure Types
PMI recognizes three scenarios in which a project or phase is formally closed. All three require the same closure activities — the circumstances differ, not the process.
| Type | What It Means | Key Point for the Exam |
|---|---|---|
| Successful Completion | Project delivers all objectives; customer accepts deliverables | Formal acceptance is required even when success is obvious |
| Phase Gate Closure | End of a phase before the next phase is authorized to begin | If closure is skipped, the next phase cannot be authorized |
| Early Termination | Project is stopped before objectives are met (budget, strategy shift, risk) | Must document why terminated and how unfinished deliverables are transferred |
The 8-Activity Closure Checklist
Regardless of closure type, PMI expects these activities to be completed:
- Obtain final acceptance of deliverables or product from the customer
- Release resources — human, financial, and physical assets
- Archive project information and request updates to OPAs (Organizational Process Assets)
- Close out contracts — verify work was done to specification, arrange final payments, update contract artifacts
- Conduct final lessons learned meeting or retrospective
- Finalize and transfer the lessons learned register to the repository
- Complete the final project report
- Validate transition readiness (operations team or next phase)
Transition Planning
Before a project can be closed, the receiving party must confirm they are ready to accept the deliverable. Transition requirements are documented in the transition plan, part of the project management plan, and should be identified as formal project activities and scheduled accordingly.
Answer: Ang Fen should not force closure. The transition plan requires that the receiving party validates readiness before the project closes. He should update the schedule to accommodate the UAT window, document the delay, and re-confirm the revised go-live date with Eugene Lowe and the governance board. Closing over the operations team’s objection creates post-closure support risk and conflicts with PMI’s emphasis on transition readiness.
6B · Benefits Realization
When Are Benefits Realized?
| Approach | When Benefits Are Typically Realized |
|---|---|
| Adaptive / Agile | Incrementally throughout — working features delivered each sprint |
| Predictive | Months or years after project closure — after full deployment and organizational adoption |
| Hybrid | Mixed — some incremental delivery during execution, full benefits after final transition |
The Benefits Management Plan
The benefits management plan defines how benefits will be created, tracked, and sustained. It is typically created before the project is approved — alongside the business case. Key contents include:
- The target benefits and how they align to organizational strategy
- The metrics and measurement methods to track benefits realization
- The timeframe for realizing benefits
- Who is accountable for sustaining benefits after the project closes
The Benefits Owner
Once a project transitions to operations, a benefits owner takes accountability for monitoring whether the promised benefits are actually being realized. This role begins as soon as benefits are delivered and continues long after closure — often for years. In predictive projects, the transition and sustainment plan identifies who is responsible. In adaptive/hybrid projects, the product owner facilitates ongoing reporting during execution.
6C · Knowledge Transfer
Tacit vs. Explicit Knowledge
| Type | Definition | Examples |
|---|---|---|
| Explicit | Knowledge that can be documented and transferred directly | Process docs, training manuals, technical specs, project plans |
| Tacit | Knowledge held in people’s experience and judgment — difficult to formalize | Stakeholder communication preferences; vendor relationship nuances; judgment in ambiguous situations |
Lessons Learned Register vs. Repository
This distinction is tested directly. Know it cold.
| Term | Scope | Timing |
|---|---|---|
| Lessons Learned Register | A single project — captures lessons throughout the life cycle | Updated continuously; finalized at closure |
| Lessons Learned Repository | The organization — stores lessons from many projects as historical OPAs | Receives the finalized register at project closure; available for future projects |
Knowledge Transfer Activities at Closure
- Conduct retrospectives or final lessons learned meetings
- Archive all project information per OPA requirements
- Finalize the lessons learned register (compiled throughout the project)
- Transfer the lessons learned register to the organizational repository
- Transition required technical knowledge and skills to the organization
Practice Questions
A. Release all team members immediately and close the project
B. Document the reasons for termination and determine how completed deliverables will be transferred
C. Escalate the decision to the PMO to request reinstatement
D. Archive all project documents and update the OPAs
Answer: B. Early termination still requires formal closure. The first step is to document why the project was terminated and to determine what happens to completed deliverables. Releasing resources (A) and archiving documents (D) are part of closure but come after the termination is documented and deliverables are handled. Escalating (C) is not appropriate — the decision has already been made at the executive level.
A. Proceed with closure since all deliverables have been completed per the plan
B. Escalate to the sponsor to force the operations team to accept
C. Validate the operations team’s readiness concerns and update the schedule accordingly
D. Document the operations team’s objection and close the project anyway
Answer: C. Transition readiness must be validated before closure. The project is not complete until the receiving party confirms they can accept the deliverable. Closing over their objection (A, D) creates post-closure risk. Forcing acceptance via escalation (B) does not resolve the underlying readiness gap.
A. In the project’s final report as a note to the next project manager
B. In the lessons learned repository as part of knowledge transfer, including the tacit insight about vendor preferences
C. In the vendor’s contract file for legal reference
D. In personal notes — this level of detail is too informal for official documentation
Answer: B. Vendor relationship insights, including tacit knowledge like communication preferences, belong in the lessons learned repository where future teams can access them. The final report (A) is project-specific and not searchable by future teams. Contract files (C) are for legal and procurement records. Personal notes (D) are not organizational assets and will be lost when the team disperses.
Before Session 14 — Your Assignments
High Priority
- Know the three closure types and what happens in each — especially early termination
- Be able to distinguish the lessons learned register from the repository by name, scope, and timing
- Complete the Session 13 LMS quiz before Thursday’s session
Medium Priority
- Glossary terms to own: Administrative Closure · Phase Gate · Transition Plan · Benefits Management Plan · Benefits Owner · Lessons Learned Register · Lessons Learned Repository · OPA · Explicit Knowledge · Tacit Knowledge · Final Report
- Review ECO domain weightings (People 42% · Process 50% · Business Environment 8%) and identify your two weakest areas from your LMS quiz scores
Optional
- Write out the closure checklist for the SLC Oracle HCM implementation. What is the status of each activity? Who owns it? What is still outstanding before Ang Fen can formally close the project?
Lesson Materials
