Closing a Project
In This Chapter
Appreciating the two triggers: planned close and ‘crash stop’
Understanding follow-on action recommendations
Making sure that you’re clear on the key content of the closure process
So, to the last of the PRINCE2 processes: Closing a Project. Closure is easy to follow in PRINCE2 if you keep in mind that it’s an orderly shut down. The closure will usually be the planned one at the end of the project, but it may also be a ‘crash stop’ (premature close) if, for example, something goes badly wrong or someone in authority decides that the project isn’t needed any more. Either way, planned close or premature close, it’s an orderly and conscious process, not a fizzling out of the project.
The Project Board will make the final decision as to whether the project can be closed, and the process Closing a Project is where the Project Manager does the shut-down work and prepares for that final board decision.