1. 8
57086
Contract and Project Management
David Sowden, The University of Hull

2. 8
57086
Contract and Project Management
Introduction to Processes -
Closing a Project
David Sowden, The University of Hull

3. Overview
• Closing a Project
– Fundamental principles
– Contexts
– Process description
– Decommissioning a Project
– Identifying Follow-on Actions
– Evaluating a Project
3

4. Closing a Project THE B
AS ICS
Check that all products have
been delivered and approved by
the customers
Document and later actions that
should be taken by the
management and support
groups
Plan when and how to assess
achievement of the expected
benefits
Report on the project’s
performance
4

5. Relationships
of Processes
Initiating a
Project
Managing
a Stage
Boundary
Directing a
Project End
Starting
a Project
Controlling
Closing a a Stage
Project
Managing
‘Product’
Delivery
5

6. Icons
Guidelines - Rules, Policies,
instructions that should be
followed
Resources - tools, systems
or materials required to
complete a task
6

7. Closing a Project (1a)
Directing a
Project Premature close Prepare premature close
Create additional work estimates
Update Issue Register
Update Project Plan
PID
Project Plan
7

8. Closing a Project (1b)
Controlling Project end
approaching
Prepare planned closure
a Stage
Update Project Plan
‘Product Status Account
PID
Project Plan
8

9. Closing a Project (2)
Closure prepared Hand over ‘products’
Obtain acceptance record
Update Benefits Review Plan
Update Configuration Item Records
Create follow-on action recommendations
PID
Issues register
Configuration Management Strategy
Risk Register
9

10. Closing a Project (3)
‘Products’ handed over Evaluate the project
Create Lessons Report
End Project Report
Follow-on actions recommendations
Issues register
Lessons Log
Quality Register
10

11. Closing a Project (4)
Project evaluated Recommend project closure
Close Daily Log
Prepare draft project closure notification
Close Issue Register
Close Lessons Log
Close Quality Register
PID
Communication Management Strategy
11

12. Closing a Project (5)
Closure recommended Directing a Project
section 4
12

13. TASK
Review your project closure
procedures

14. Closing a Project CHEC
Have all products been completed and approved? K
Has a Product Status Account been created to verify the status of all the products?
Have all outstanding issues been documented as follow-on recommendations ready for distribution subject to Project Board
approval?
For premature closure, has the means for recovering products that have been completed or are in progress been approved by
the Project Board? If requested, was an Exception Plan created and approved?
Is there an acceptance record for the handover of the project product?
Does the acceptance record include operational and maintenance acceptance (if applicable)
Has the lessons Log been reviewed and a Lessons Report created ready for distribution subject to Project Board approval?
Has the Project Plan been updated with actuals?
Has the Business Case been updated with actuals?
Has the Benefits Review Plan been updated with actuals
Has the End Project Report been produced showing actuals against planned performance and summarising lessons and follow-
on action recommendations?
Has the End Project Report been issued to the Project Board in accordance with project controls?
Has a draft project closure notification been created for the Project Board approval and onward distribution?
Has all registers and logs been closed?
Has all project documentation been archived?