PRINCE2 Project Closure – the final act!
A very important point needs to be made here. If the project, within any management stage, needs to be brought to a premature close and hence project closure, then the closing a project process (CP) is used. Let us suppose that a given project has three delivery stages after the initiation stage. In the final delivery stage, work packages containing information on the specialist products to be created will be issued and managed as described above.
However, once the final specialist product within the final work package has been approved, then the project manager will trigger the closing a project (CP) processes to shut the project down in a controlled manner and perform project closure. A final management stage is not used to merely to use the Closing a Project process and project closure. In summary, the final stage of a project will use the Controlling a Stage, Managing Product Delivery, and Closing a Project processes.
Assuming a natural project closure, then the prepare planned closure activity will be used. The project manager would use Project Support as they provide Configuration Management, and request a product status account to ensure that all products within the project would have been approved and that the project acceptance criteria have been met. The Project Plan should be updated with the ‘actuals’ of this final stage prior to project closure.
The projects products must now be handed over to the operational and maintenance environment, where they will be used to ultimately realise the benefits contained as stated within the Business Case.
The project manager would updates relevant configuration item records to show that such products have the status of ‘operational’, any acceptance records should be created or obtained, and the Benefits Review Plan updated to reflect any products that have already realized benefits and to include any post project activities for such benefits that have yet to be realized at project closure.
The Evaluate the project activity will create the end of project report to capture actual progress and aspects such as project performance metrics, and will include the Lessons Report based upon the information contained within the Lessons Log as part of project closure.
project closure for a premature close
In the case of premature close, then the reasons for this should be entered and updated on the Issue Register, and if necessary any additional work may be needed to buy the complete unfinished products or to make them safe. Once the project manager has determined that the project should and can perform project closure, then a recommendation of such should be raised to the project board in the form of a project closure recommendation.
The final activity in any project, is the authorize project closure within the Directing a Project process. The project board would need to review original and updated versions of the PID, review and approve the End Project Report, confirm any follow-on actions or loose ends, verify that the projects products have been handed over in an appropriate manner, ensure that the Business Case remains viable, advise that project closure can now be implemented, and advise those supplier resources that these can now be withdrawn.
For more information on passing your PRINCE Exams – CLICK HERE!
