Postmortem Documentation: Difference between revisions
Jump to navigation
Jump to search
(ContinuousReplacement) Tag: continuous replacement |
No edit summary |
||
| Line 1: | Line 1: | ||
A [[Postmortem Documentation]] is an [[analysis document]] for a [[concluded project]]. | |||
A [[Postmortem Documentation]] is a [[ | * <B>Context:</B> | ||
* <B>See:</B> [[Lessons Learned]], [[Risk Management]], [[Project Management Body of Knowledge]]. | ** It can (typically) be produced by a [[Post-Mortem Task]]. | ||
* <B>See:</B> [[Lessons Learned]], [[Risk Management]], [[Project Management Body of Knowledge]], [[Pre-Mortem]]. | |||
---- | ---- | ||
---- | ---- | ||
Revision as of 19:04, 14 February 2020
A Postmortem Documentation is an analysis document for a concluded project.
- Context:
- It can (typically) be produced by a Post-Mortem Task.
- See: Lessons Learned, Risk Management, Project Management Body of Knowledge, Pre-Mortem.
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Postmortem_documentation Retrieved:2020-2-13.
- 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]
- ↑ Lessons Learned on the website of the Center for Disease Control, read 3. September 2015.
- ↑ IEEE: A defined process for project post mortem review