1. Post Implementation Review CSEM01 SE Evolution & Management Anne Comer Helen Edwards

2. Post Implementation Review Users and the Project Team should conduct a Post Implementation Review (PIR) on the areas listed below: to evaluate whether the system objectives have been fully achieved and the problems identified have been satisfactorily solved; to evaluate the utilization of resources and recommend adjustments to both non-recurrent and recurrent expenditure and costs if considered necessary; to evaluate the realization of benefits, including savings in posts, and recommend adjustments if considered necessary; to evaluate whether the implementation schedule as contained in the original funding submission has been adhered to; and to identify necessary improvements to the computer system and recommend a course of action to implement them.

3. Example Outline for a Post Implementation Review 1. Purpose of Post- Implementation Review 2. Summary of Project Being Reviewed 3. Project History 4. Project Objectives 5. Project Status 6. Software Evaluation 7. Hardware and Network Performance 8. System Setup and Administration 9. Training 10. Software Integration 11. System Performance Against Project Objectives 12. Areas of Improvement 13. Cost Assessment 14. Lessons Learned 15. Project Performance vs. Corporate Objectives 16. Project Performance vs. Information Technology Strategy 17. Project Performance vs. Environmental Management Strategy 18. Software Company’s Commitment to the Product (for purchased software) 19. Project Management Evaluation 20. Benefits Assessment 21. Next Steps for Project

4. Bibliography/ Further Reading Collier, B., De Marco, T., Feary, P., ‘A Defined Process for Project Postmortem Review’, IEEE Software, July 1996. Columbia University, Project Management Resource Center, http://www.columbia.edu/~jm2217/ http://www.columbia.edu/~jm2217/