Closing a Project

Closing a Project

Purpose

Providing a fixed point to confirm acceptance.

Objectives

  • Verifying customer acceptance or products.
  • Ensuring that the user side can maintain the product.
  • Reviewing the performance of the project
  • Assessing the Benefits.
  • Addressing all open issues and risks.
  • Addressing all open issues and risks.

Roles and Responsibilities

Corp. Or Prog. Mgmt:
Approve Benefits Review Plan, Lessons Report.
Executive:
Approves Follow-on Action Recommendations, Acceptance Records, End Project Report, Draft Project Closure Notification; Review Benefits Review Plan, Lessons Report.
Senior User:
Approves FAR, AR, EPR, DPCN; Review BRP, LR.
Senior Supplier:
Approves FAR, AR, EPR, DPCN; Review BRP, LR.
Project Manager:
Creates FAR, EPR, LR, DPCN; Obtain AR.
Team Manager:
Project Assurance:
Review documents; advise PM
Project Support:
Create Product Status Account, Update Configuration Item Records.

Applying the Themes

Business Case (Why):
Business Case and Benefits Review Plan are updated.
Organisation (Who):
Inform the stakeholders, create Draft Project Closure Notification.
Quality (What):
Confirm that acceptance Criteria have been met. Close the Quality Register.
Plans (How, How much, When):
Review and update the Project Plan.
Risk (What if):
Close the Risk Register.
Change (What is the impact):
Update and close the Issue Register.
Progress (Where are we, direction, should we carry on):
Confirm the product is delivered as defined, create Follow-on Action Recommendations, Lessons Report, End Project Report; review Project Initiation Documentation; close Lessons Log.
×