Post-Project Review

From apppm
Revision as of 17:36, 22 February 2018 by Kxviinth (Talk | contribs)

Jump to: navigation, search

When finalizing a project and providing a deliverable, a project manager does not necessarily know if the project can be considered a success. Thus, a methodology to gain tacit-knowledge can be done by using Post-Project Reviews. Post-Project Review is a tool to "evaluate project results in order to improve future projects methods and practises"[1]. It is arguably a tool within the uncertainty perspective, as the purpose of the tool is to analyze potential failures and successes of a project- The knowledge gained can lead to minimized risk by possibly optimizing and/or preventing mistakes in subsequent projects.

Despite the usefulness of the tool, there is no fixed framework of how to conduct it. Organizations operate differently and do have a tailored methodology for execution of the review [2]. Different studies depict recommendations of measures to apply before closing a project and conducting a post-project review, as well as the methodology on how to conduct it. A project manager follows a set of interrelated actions in order to provide the desired deliverable, and do mainly follow the five categories known as Project Management Process Groups: Initiating, Planning, Executing, Monitoring/Controlling and Closing [3]. Simultaneously, a successful application of Post-Project Review must follow these steps. If a project manager defines the different criteria for success or failure of a project, as well as applying strict quality management during the project; An easier application of Post-Project review can be assessed [4]. Furthermore, the review can be conducted by a combination of team-members and external facilitator. Lastly, there are two recommended debriefing methods which are process-based and documentation-based. Process-based methods are debriefing methods that address the key learnings experienced during a project, and documentation-based methods"are methods on logging the knowledge obtained [1].

This article focuses on the purpose fo the tool, as well presenting a methodology of applying post-project review considering a new product development project. Furthermore, the article argues who are responsible for applying the tool and depict the many barriers towards against it.


Big Idea

Post-Project Review to improve organizational learning

Figure 1: Double loop learning through post-project reviews in R&D projects [1]

Post-Project Review is a formal review or a meeting of an ended project, examining the lessons that may be learned and used to the benefit of future projects [1][5]


Cite error: <ref> tags exist, but no <references/> tag was found
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox