Postmortem documentation

A project post-mortem is a process, usually performed at the conclusion of a project, to determine and analyze elements of the project that were successful or unsuccessful. The Project Management Body of Knowledge (PMBOK) refers to the process as lessons learned.[1] Project post-mortems are intended to inform process improvements which mitigate future risks and to promote iterative best practices. Post-mortems are often considered a key component of, and ongoing precursor to, effective risk management.[2]

Elements of a project post-mortem

Post-mortems can encompass both quantitative data and qualitative data. Quantitative data include the variance between the hours estimated for a project and the actual hours incurred. Qualitative data will often include stakeholder satisfaction, end-user satisfaction, team satisfaction, potential reusability and perceived quality of end-deliverables.

Role of time tracking

Successful analysis of project estimate variance is dependent on accurate time tracking. The greater the granularity with which time is tracked, the more detailed an analysis can be performed during the project post-mortem.

See also


  1. Lessons Learned on the website of the Center for Disease Control, read 3. September 2015.
  2. IEEE: A defined process for project post mortem review
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.