PIR_checklist2.doc - Project Post-Implementation Review Checklist Confidentiality Statement This <document title> along with all attachments hereto

PIR_checklist2.doc - Project Post-Implementation Review...

This preview shows page 1 - 3 out of 6 pages.

Project Post-Implementation Review Checklist Confidentiality Statement This <document title> along with all attachments hereto shall be considered <company> ’s Proprietary/Confidential Information
Image of page 1
gantthead.com Project Post-Implementation Review Checklist The Post Implementation Review (PIR) is conducted after completion of the project, but prior to making final improvements. Ideally, it should happen after the system has been in place long enough to allow for judgments to be made about how it will perform long- term. Its purpose is to evaluate how successfully the project objectives were met and how effective project management practices were. Document the results of the PIR in a close-out report called the post implementation review report. Conducting a timely and thorough PIR will help identify lessons learned and previously unidentified shortfalls. These, in turn, will assist in making final improvements to the system being implemented. Elements of lessons learned will also assist in planning, managing and meeting the objectives of future projects. The checklist below is meant to be fairly comprehensive and can be pared down to suit your needs and the scale of the project. Focus on the project results So in terms of project results, you want to be sure that you: Understand how technically successful the project really was in terms of satisfying all requirements and the project’s main goal. Understand the business benefits delivered and whether they satisfied the actual intent of sponsors and stakeholders. Gather lessons learned that can be used to improve the future performance of projects and individuals in the organization. Who should you involve? Take a two-pronged approach to who drives the review process, by allowing both an internal team to drive one version of the review and an independent team to drive another version of it. The internal/project team has a deep understanding of the project and will uncover insider issues that are technically complex. An independent/audit team can be more objective and will pick up on issues that the project team has dismissed as a group. You can use elements of this checklist to outline a common structure that both can adhere to.
Image of page 2
Image of page 3

You've reached the end of your free preview.

Want to read all 6 pages?

  • Fall '19
  • Project Management,  Understand, Project Post-Implementation Review Checklist

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture