From my experience all projects need to have an exit strategy as more often than not a project brings about a change to business-as-usual functions - once a project has been completed (or abandoned!) you need to embed the products or change that it's achieved. For example, if you are managing the migration to a new ILS your exit strategy would contain a training and support programme for cataloguers, educating the user on how to use the new catalogue etc. It is also important to document any lessons learned when you finish off a project so that they are available for future projects - what worked well? - what didn't work so well?
|