Download as pdf or txt
Download as pdf or txt
You are on page 1of 6

Closing

 a  Project

You  move  into  the  Closing  stage  either  because:

All  work  has  been  completed  and  your

Sponsor  has  accepted  all  project  deliverables.

OR

The  project  is  cancelled  or  put  on-­‐hold.


Closing  a  Project

• Finishing  the  work


• Produce  checklist  of  outstanding  work  –  loose  ends.
• Have  all  project  objec;ves  been  met?
• More  frequent  mee;ngs  to  resolve  final  issues.
• Inform  all  stakeholders.

• Moving  into  producEon  (e.g.  deploying  new  computer  system)


• Ensuring  users  have  been  trained.
• Ensuring  all  required  documenta;on  is  in  place.
• Micro-­‐planning  the  cutover  process.
• Agreeing  remaining  issues  (if  any)  to  be  handled  as  B-­‐A-­‐U.
• Short-­‐term,  post-­‐live  support
• Agreeing  support  roles  /  responsibili;es
• Technical,  Func;onal,  User.
Closing  a  Project

• Final  OperaEonal  Handover


• Formal  acceptance  by  Users
• Criteria
• Func;onal,  Usability,  Stability  etc.

• Technical  acceptance
• As-­‐Built.

• Formal  acceptance  by  Opera;ons


• Removing  project-­‐supplied  support.
• U;lize  standard  checklist.

• Formal  acceptance  by  Steering  Group.


Closing  a  Project

• Closing  contracts  with  suppliers,  sub-­‐contractors  etc.


• Verifying  that  supplier  work  has  been  completed  in  accordance  
with  the  Statement-­‐of-­‐Work  (SOW).
• Disbanding  the  team
• Releasing  members  as  project  draws  to  close.
• Advise  Resource  Managers  in  advance.
• Post-­‐project  review  meeEng
• Project  team,  other  key  stakeholders.
• Ideally  a  neutral  facilitator.
• Prepared  agenda  and  checklist.
• Project  Management  Plan  is  the  key  document.
• Baseline  Objec;ves  vs.  Actual.
• Lessons  learned,  Recommenda;ons.
• Project  closure  report
Closing  a  Project

• Closing  project  accounts.

• Archiving  of  project  documentaEon


• Project  Management  Plan.
• Contract  documents.
• Training  documents.
• Technical  architecture  documents  etc.

• You  need  to  decide  what  to  keep,  and  where  it  will  be  kept.

• End-­‐of-­‐project  party!
Closing  a  Project

• Finally…

Realizing  the  benefits…

Responsibility  generally  rests  with  Sponsor,  Champion  to  measure  


against  benefits  stated  in  the  Business  Case.

You might also like