A Post-Implementation Review (PIR) is an assessment and review of the completed working solution. It will be performed after a period of live running, some time after the project is completed.
There are three purposes for a Post-Implementation Review:
In some cases, the first of these objectives can be a contractual issue. Where that is the case, it may be safer to run separate reviews - one focused on contractual compliance and the other seeking to derive further benefit from a no-blame review.
A Post-Implementation Review should be scheduled
some time after the solution has been deployed. Typical
periods range from 6 weeks to 6 months, depending on the
type of solution and its environment.
The PIR is intended to be an assessment and review of the final working solution. There should have been at least one full processing and reporting cycle completed.
It should not be performed while the initial snags are still being dealt with or while users are still being trained, coached and generally getting used to its operation.
The PIR should be timed to allow the final improvements to be made in order to generate optimum benefit from the solution. There is no point in waiting too long as the results are intended to generate that final benefit for the organisation and team.
There is often a difference of opinion as to who should perform the Post-Implementation Review. Usually, members of the project team will want to complete the review as a natural extension of their responsibility to deliver optimum benefit from the solution. They understand what was required, what was changed, how it was achieved, how things are supposed to work, how to fix problems, etc.
There is a converse argument that the review should be performed by an independent team. This reduces the risk that any errors or omissions of the project team might equally be overlooked in their review.
A solution is to do both. An independent audit team, working in consultation with the business users and project team, could examine whether the results are satisfactory. The project team might then reconvene to consider that input and also to examine how to generate further value from the solution.
A list of points should be drawn up to cover all elements of the operational solution. They should include such things as:
These questions will be investigated through a combination of investigative techniques including interviews, examination of documentation, performance statistics, hands-on tests and checks, etc. Implications and potential remedial options would then be assessed and evaluated. The findings and recommended actions would be prepared, normally in the form of a report or presentation.
The findings and recommendations will be presented to:
Specific actions should be proposed to address any further work that is recommended. This might be handled in several different ways, for example: