Eventually all work is completed (or the (B.1) Project Board request abnormal termination) and the final specialist stage uses the sub-processes of Closing a Project (CP) rather than SB to perform some similar and some unique actions.
Both CP and SB update the (A.30) Project Plan with past stage’s results. SB creates an (A.10) End Stage Report for review at Authorising a Stage or Exception Plan (DP3) while CP creates an (A.9) End Project Report for consideration at Confirming Project Closure (DP5).
Closing a Project (CP) has unique aspects. CP checks all products have been accepted by the users and support staff and any configuration management handover is finalised, that all outstanding project issues are ready to be handed on to someone post project in the form of a (A.13) Follow-on Action Recommendations, and a (A.19) Post-Project Review Plan has been prepared for benefits review by the (B.2) Executive or delegated representative after the project.
CP also reviews all project records and in particular the (A.16) Lessons Learned Log to produce the (A.17) Lessons Learned Report for use by “some relevant authority”.
Decommissioning a Project (CP1) 'looks down' at what the project has done to confirm that the project has satisfied all handover criteria.
Identifying Follow-on-Actions (CP2) 'looks forward' by preparing for the activities that follow post-project.
Evaluating a Project (CP3) 'looks backward' to summarises how well the project performed versus its (A.27) Project Initiation Document.