|
IT Bites > Services >
Project Management > Closing
Defined by the Project Managers Institute as:
| |
"formalizing acceptance of the project or
phase and bringing it to an orderly end" |
|
Closure involves, usually, the handover from project status to operational.
The Business is asked to accept that the products have been delivered as
required, and Users that they can operate and support them.
ALL TOO OFTEN, INSUFFICIENT ATTENTION IS PAID TO PROJECT CLOSURE.
IT Bites would expect to deliver a Follow-on Actions report to its client.
This would identify:
 | Gaps from the original project scope that have not been delivered |
| New requirements that have arisen as the project progresses |
| Any 'run off' processes that can be managed by, say, the operational team
or, even, a separate project team |
Finally, if required, a client may like to see a Lessons Learned Report, a
Project Evaluation report or other specific reports. A formal Project Review
event may also be organised. IT Bites are happy to meet client expectations.
In Prince 2 terms, Closing corresponds to the Close a Project (CP) process.
| 
