Post-Implementation Review (PIR)
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
Author: Jakob Kehler, February 2022 | Author: Jakob Kehler, February 2022 | ||
| − | |||
| − | |||
| − | + | The ''Post-Implementation Review (PIR)'' (also known as Business Review, Project Audit or Post-Project Review) is a methodology that can be applied to evaluate the success of a project after it has been undertaken based on 1. the key deliverables of the project, 2. the process itself going through all life cycles of a project and 3. the delivery of the business case. <ref name="Post Implementation Reviews - A means of Applying Knowledge: Lessons from a failed project"> Jewels, Tony; Baker, Jason; Underwood, Alan, ''Post Implementation Reviews - A means of Applying Knowledge: Lessons from a failed project'', 14th Australasian Conference on Information Systems (Perth, 2003)</ref> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | In ''ISO 21502'', the project life cycle is defined as a "defined set of phases from the start to the end of the project". This includes the initiation of the project up to all activities including the closure of the project. Pre- and post-project activities are not include in the project life cycle. <ref name="ISO21502"> ISO 21502</ref> Nevertheless, a project itself may have only minimal impact on the economy, environment and society, the deliverables itself have bigger impacts and consequences. Taking this into account, a PIR is useful to review the projects with its temporary characteristics "within a broader framework of organisational objectives and given contexts and environments". <ref name="Post Implementation Reviews - A means of Applying Knowledge: Lessons from a failed project"></ref> | |
| − | + | ==References== | |
| − | + | <references /> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 22:16, 13 February 2022
Author: Jakob Kehler, February 2022
The Post-Implementation Review (PIR) (also known as Business Review, Project Audit or Post-Project Review) is a methodology that can be applied to evaluate the success of a project after it has been undertaken based on 1. the key deliverables of the project, 2. the process itself going through all life cycles of a project and 3. the delivery of the business case. [1]
In ISO 21502, the project life cycle is defined as a "defined set of phases from the start to the end of the project". This includes the initiation of the project up to all activities including the closure of the project. Pre- and post-project activities are not include in the project life cycle. [2] Nevertheless, a project itself may have only minimal impact on the economy, environment and society, the deliverables itself have bigger impacts and consequences. Taking this into account, a PIR is useful to review the projects with its temporary characteristics "within a broader framework of organisational objectives and given contexts and environments". [1]
