Post Implementation Review

Post Implementation Review Guide

A guide to completing the Project Review

Strategic Capital, Infrastructure and Projects

Prepared by:
Andrew Segrott / Strategic Capital, Infrastructure and Projects
Version 1.0 – 17 December 2010

CRICOS Provider No. 00103D Post Implementation Review l Page 1 of 15

Post Implementation Review

Overview
This document lays out guidelines for the post implementation review of a project. The Post Implementation
Review (PIR) is used to supply information about the outcomes and success of a project. The PIR lists the
expected outcomes as specified in the Project Management Plan, reports on variances from that plan and
then asks for recommendations and how they will be used, as well as lessons learned.
All projects require a Project Review report to be completed.
Additionally, for all major projects a PIR is required. A PIR is completed by the Strategic Capital,
Infrastructure and Projects following the closure of projects and submission of a Project Review by the
Project Manager.

Project Information
Project Information will be supplied by Strategic Capital, Infrastructure and Projects

Version Control
Document all changes to the document from the initial draft version (Version 0.1).
Minor alterations result in an increment of the minor identifier (e.g. 0.1 to 0.2).
Approved versions of the document result in an increment of the major identifier (e.g. 0.3 to 1.0).

Summary of Project
This section consists of a history of the project with key highlights.

Members of PIR Team

The panel should be arranged through the project sponsor and consist of a Chair, 2 independent client
representative and 2 project team members.

Outcomes in Key Project Areas

A table of key project areas; include a reference for evidence where appropriate.

Objective Outcomes
A table showing information about project objectives outlined in Project Management Plan.

Benefits Realisation
A table of information about the benefits realised. Include a reference for evidence, where appropriate.

Business Requirements
A table of the applicable business requirements from the project specifications; include a reference for
evidence where appropriate.

CRICOS Provider No. 00103D Post Implementation Review Page 2 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
Post Implementation Review

Lessons Learned
List the lessons learned from your project. The idea is to be positive. How can these lessons be applied to
other projects?

Recommendations Arising from the Project

List the recommendations derived from your project. The idea is to be positive. What could have been
improved? How will these lessons/recommendations be applied to other projects?

Methods Used to Gather Information for PIR

Provide information on how information for PPIR was gathered, e.g. focus groups, individual interviews, log
reports, status reports. List the details for focus groups and interviews. Designated stakeholders, business
clients, steering committee members, impacted areas, etc., should be consulted as necessary for the project.

Appendices and Supporting Documentation (optional)

List attached appendices and supporting documentation. This information is optional, depending on the
project size and outcomes. For example, appropriate records from a project that encountered significant
problems could well be useful. Similarly, information that demonstrates a lesson to be learned from a project
could be included. Logs of changes and incidents should be included here. Original documentation may also
be included, eg, a report on lower level specification success.

CRICOS Provider No. 00103D Post Implementation Review Page 3 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
Post Implementation Review

1 Project Information
Project Information will be supplied by Strategic Capital, Infrastructure and Projects

1.1. Project Number

1.2. Project Name

1.3. Date

1.4. Project Ownership

1.5. Project Contacts

Name Position Phone Email

Primary

Other

Other

1.6. Project Approval

1.7. Document Path

CRICOS Provider No. 00103D Post Implementation Review Page 4 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
Post Implementation Review

2 Version Control
Version Date Reason/Comments/Approval
Number

Document all changes to the document from the initial draft version (Version 0.1).
Minor alterations result in an increment of the minor identifier (e.g. 0.1 to 0.2).
Approved versions of the document result in an increment of the major identifier (e.g. 0.3 to 1.0).

CRICOS Provider No. 00103D Post Implementation Review Page 5 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
Post Implementation Review

3 Summary of Project
This section consists of a history of the project with key highlights.

CRICOS Provider No. 00103D Post Implementation Review Page 6 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
Post Implementation Review

4 Members of PIR Team

Name FedU Position Role in Project Phone

The panel should be arranged through the project sponsor and consist of a Chair, 2 independent client
representative and 2 project team members.

CRICOS Provider No. 00103D Post Implementation Review Page 7 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

5 Outcomes in Key Project Areas

Key Project Area Planned Expectation Actual Outcome Reference for Reason for Variance from
(as in Project Management Evidence Project Management Plan
Plan)

Scope

Time

Cost

Quality

Risk Management

Communication

A table of key project areas; include a reference for evidence where appropriate.

CRICOS Provider No. 00103D Post Implementation Review Page 8 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

6 Objective Outcomes
Objective Objective Met? Outcome Reference for Reason for Variance from
(as in Project (Score 1-5 Evidence Project Management Plan
Management Plan) 1=Not at all
5=Completely)

A table showing information about project objectives outlined in Project Management Plan.

CRICOS Provider No. 00103D Post Implementation Review Page 9 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

7 Benefits Realisation
Benefits Realised Benefit Realised? Outcome Reference for Reason for Variance from
(as in Project (Score 1-5, 1=Not at all Evidence Project Management Plan
Management Plan) 5=Completely)

A table of information about the benefits realised. Include a reference for evidence, where appropriate.

CRICOS Provider No. 00103D Post Implementation Review Page 10 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

8 Business Requirements
Top Level Business Requirement Met? Outcome Reference for Reason for Variance from
Requirements (Score 1-5, 1=Not at all Evidence Specifications
(as in Specifications) 5=Completely)

A table of the applicable business requirements from the project specifications; include a reference for evidence where appropriate.

CRICOS Provider No. 00103D Post Implementation Review Page 11 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

9 Lessons Learned
No. Lesson Where/How to be Used

List the lessons learned from your project. The idea is to be positive. How can these lessons be
applied to other projects?

CRICOS Provider No. 00103D Post Implementation Review Page 12 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

10 Recommendations Arising from the Project

No. Recommendation Where/How to be Used

List the recommendations derived from your project. The idea is to be positive. What could have
been improved? How will these lessons/recommendations be applied to other projects?

CRICOS Provider No. 00103D Post Implementation Review Page 13 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

11 Methods Used to Gather Information for PIR

Information Gathering Method All Names Position at FedU Interest or
(eg focus group, interview) Role in Project

Provide information on how information for PPIR was gathered, e.g. focus groups, individual
interviews, log reports, status reports. List the details for focus groups and interviews. Designated
stakeholders, business clients, steering committee members, impacted areas, etc., should be
consulted as necessary for the project.

CRICOS Provider No. 00103D Post Implementation Review Page 14 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx
 Post Implementation Review

12 Appendices and Supporting Documentation (optional)

List attached appendices and supporting documentation. This information is optional, depending
on the project size and outcomes. For example, appropriate records from a project that
encountered significant problems could well be useful. Similarly, information that demonstrates
a lesson to be learned from a project could be included. Logs of changes and incidents should
be included here. Original documentation may also be included, eg, a report on lower level
specification success.

CRICOS Provider No. 00103D Post Implementation Review Page 15 of 15

K:\SCIP\Timetabling\PMF Fed Uni\04 Guides\Word Masters Fed Uni\18.1 Post Implementation Review Guide_FedU.docx