57086 08 closing_a_project

David Sowden, The University of Hull

857086 Contract and Project Management

857086 Contract and Project Management

Introduction to Processes - Closing a Project

David Sowden, The University of Hull

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 BASICS

Report on the project’s performance

Plan when and how to assess achievement of the expected

benefits

Document and later actions that should be taken by the

management and support groups

Check that all products have been delivered and approved by

the customers

Relationships of Processes

5

Starting a Project

Directing a Project

Initiating a Project

Managing a Stage

Boundary

Controlling a Stage

Managing ‘Product’ Delivery

End

Closing a Project

Icons

6

Guidelines - Rules, Policies,instructions that should be followed

Resources - tools, systemsor materials required to complete a task

Closing a Project (1a)

7

Prepare premature closeDirecting a Project

Create additional work estimatesUpdate Issue RegisterUpdate Project PlanPIDProject Plan

Premature close

Closing a Project (1b)

8

Prepare planned closureControlling a Stage

Update Project Plan

PIDProject Plan

Project end approaching

‘Product Status Account

Closing a Project (2)

9

Hand over ‘products’

Obtain acceptance recordUpdate Benefits Review PlanUpdate Configuration Item Records

PIDIssues register

Closure prepared

Configuration Management StrategyRisk Register

Create follow-on action recommendations

Closing a Project (3)

10

Evaluate the project

Create Lessons Report

Follow-on actions recommendationsIssues register

‘Products’ handed over

Lessons LogQuality Register

End Project Report

Closing a Project (4)

11

Recommend project closure

Close Daily Log

Project evaluated

PID

Prepare draft project closure notificationClose Issue RegisterClose Lessons LogClose Quality Register

Communication Management Strategy

Closing a Project (5)

12

Directing a ProjectClosure recommended

section 4

TASK

Review your project closure procedures

CHECKHave all products been completed and approved?

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?

Closing a Project