Chap 4.7 Project or Phase Close

Trainer: Anand BobadePMBOK 6th Edition, 2019, All rights reserved.
Close Project or
phase
Chapter 5 –
Project Integration Management
PMP SIXTH EDITION

PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com)
4.7 Close Project or Phase
What is Phase or project closure?
Close Project or Phase process definition
Close Project or Phase - ITTO
Difference between Close Project & close Phase
What are accepted deliverables?
Contract closure Vs. Project closure.
Review

Integration Management processes
Develop Project
Charter
Develop Project
Management plan
Direct and Manage
Project work
Manage Knowledge
Monitor & Control
Project Work
Perform Integrated
change Control
Close Project or
phase
I P EE
MC CMC

Close Project or Phase -> Overview
Hospital Opening Ceremony
Hospital construction work is completed
Medical equipment installation is completed
Staff has been Training to use medical equipment
Operational Team has been Trained to use/ operate facilities
Project is ready to be Closed.

The process of finalizing all activities across all of the PMP Groups to
formally complete the project or phase.
project or phase information is archived, the planned work is
completed, and organizational resources are released.
Close Project or Phase -> Definition
Finalizing
all
activities

Project Managers focuses on:
Reviewing all prior information from the previous phase
closures.
Reviews scope baseline to ensure completion before
considering the project closed.
Ensure all project work is completed & project has met its
objectives.
Establishes the procedures to investigate & document reasons
for actions taken if a project is terminated before completion.
For successful closure, PM has to engage all concern
stakeholders.
Close Project or Phase -> Administrative closure

Process includes all planned activities necessary for administrative
closure of the project or phase.
Actions and activities includes:
Satisfying completion or exit criteria.
Transfer project’s products or services to operations.
Collect project or phase records
Audit project success or failure
Gather lessons learned
Archive project information
Close Project or Phase -> Administrative closure

Close Project or Phase->ITTO
Expert Judgment
Data analysis
Meetings
Project Charter
Project Management
plan
Project documents
Accepted deliverables
Business documents
Agreements
Organizational process
assets
Procurement
Documents
Project document
updates
Final product, service
or result transition
Final Report
OPA updates
Inputs Tools & Techniques Outputs

Close Project or Phase -> Input
Accepted deliverables Project Charter Business documents Agreements
Project Management
plan
Procurement
Documents
Project documents
Organizational
process assets

Accepted
deliverables
Any product, deliverable or purchased equipment which is approved by business.
Partial deliverables may also be included for phased or cancelled projects.
Example:
Software build after
UAT
Approved product
specifications (Building
drawing and plan)
Delivery receipts of
equipment
Close Project or Phase -> Input -> Accepted deliverables

Project Charter
• Objective : Verify project/phase has met its objective.
Business documents:
• Business case; Benefit management plans
• Ensure project has delivered benefits or ready for it.
Agreements:
• Contracts may be used as input to verify all contractually
agreed deliverables & milestones are delivered.
Project Management plan
• Plans & baselines; closure process
Close Project or Phase -> Input
Business Case
Benefit Management
plan

Procurement
Documents
To close the contract all procurement documentation is collected, indexed and filed.
Close Project or Phase -> Input -> Procurement Documents
Procurement documents may includes:
“As-built” plans
/ drawings
“as developed”
documents
Manuals Troubleshooting
Other technical
documentation

Project documents
Below project documents may act as input for closure activities:
Close Project or Phase -> Input -> Project documents
Assumption log Issue log Change log
Lessons learned
register
Risk Register Risk Report Milestone list Basis of estimates
Quality control
measurements
Quality reports
Requirements
documentation
Project
communications

Close Project or Phase -> Tools & Techniques
Expert Judgment Data analysis Meetings

Expert
Judgment
Experts ensures Project or phase closures is performed to appropriate standards.
Close Project or Phase -> Tools & Techniques -> Expert Judgment
Expertise can be used for
Management
control
Audit
Legal and
procurement
Legislation and
regulations

Meetings
Close Project or Phase -> Tools & Techniques -> Meetings
To confirm the
deliverables have
been accepted
To validate that
the exit criteria
have been met
To formalize the
completion of
the contracts
To evaluate the
satisfaction of
the stakeholders
To gather lessons
learned
To transfer the
knowledge and
information
To celebrate
success
Following meeting may be used:

Data analysis
Following data analysis techniques are used:
Close Project or Phase -> Tools & Techniques -> Data analysis
Document analysis
•Finalize project or phase records. Ensure all records are approved.
Regression analysis
•Involves examining one variable and see effect on dependant
variable. E.g., How Open defects are going to impact operational
cost.
Trend analysis
•The process of identifying trends is called Trend Analysis. E.g., PM
may analyse delay trend to establish fact that Vendor has used
less resources on project than contractually agreed.
Variance analysis
•It is an investigation of two comparable data points. There are
three major types of variance reviews: Estimated versus planned,
planned versus actual & Estimated versus actual.

Close Project or Phase -> Output
Final product,
service or result
transition
Final Report
Project document
updates
OPA updates

Final product, service
or result transition
Refers to Transition of Final product, service to Operational team.
In case of a phase closure, it refers to intermediate product, service of that phase.
Close Project or Phase -> Output -> Final product, service or result transition

Final Report
It’s phase or project closure reports which start with summary level description.
Scope objectives, criteria to evaluate scope, and the completion evidences.
Quality objectives, criteria to evaluate the project and product quality, and variance information.
Schedule objectives, planned and actual dates, and reasons for variance.
Cost objectives including acceptable cost range, actual costs, and the reasons for variance
Summary of
How benefits
were achieved
How project
achieved the
business needs
identified in the
business plan
How Risk, Issues
were addressed
Close Project or Phase -> Output -> Final Report

Project document
updates
Project documents:
Operational and support
documents
Project or phase closure
documents
Lessons learned
repository
Close Project or Phase -> Output -> Project document updates

OPA updates
• PMP; scope, cost, schedule, and project
calendars, risk & other registers;
• CM documentation, planned risk
responses, and risk impact.
Project
files:
• formal documentation that indicates
completion of the project or phase
• Transfer of the completed project or
phase deliverables.
Project or
phase
closure
documents:
• Lessons learned that can be
recommended for use, by future
projects.
Historical
information
Close Project or Phase -> Output -> OPA updates

Close Project or Phase -> Quick Review
What is project or phase closure?
process definition
ITTO
What is successful project closure?
What is Transition of product to operations.
Final Report

Chap 4.7 Project or Phase Close

Chap 4.7 Project or Phase Close

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Chap 4.7 Project or Phase Close

Similar to Chap 4.7 Project or Phase Close (20)

More from Anand Bobade

More from Anand Bobade (17)

Recently uploaded

Recently uploaded (9)

Chap 4.7 Project or Phase Close