Post-Project Review

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

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Abstract

When finalizing a project and providing a certain 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 a project results in order to improve future projects methods and practises. It is a a process to analyze potential failures and successes, wherein a knowledge gained from it can be beneficial for future projects.

A project manager follows a set of interrelated actions in order to provide the desired deliverable, and do mainly follow the five categories know as Project Management Process Groups: Initiating, Planning, Executing, Monitoring/Controlling and Closing. Simultaneously, a successful application of Post-Project Review must follow these steps. If a project manager considers carefully analyses 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. Post-Project review are conducted by a small internal team after closing, and the two different types of assessing it are: Process-Based and Documentation-Based methods.

This article focuses on the method of applying Post-Project Review, based on research \& development and new product development-projects through publications from PMI and Project Managers. Furthermore, a case analysis regarding new-modern use of Post-Project Review conducted by PMI will be discussed.

Big Idea

Application

Limitations

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox