正在翻页。
正在呈现下一章……
此阅读内容目前仅有英语版。界面使用你选择的语言。
阅读英语原文 →A project post-mortem is a process used to identify the causes of a project failure (or significant business-impairing downtime), and how to prevent them in the future. This is different from a Retrospective, in which both positive and negative things are reviewed for a project.
The Project Management Body of Knowledge (PMBOK) refers to the process as lessons learned. 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.
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.
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.
选编并重新排版自 Postmortem documentation,由其贡献者编写,采用 CC BY-SA 4.0. 修订版 1314822468。 章节和格式经过精简;链接中的修订版提供完整背景与贡献历史。此参考文本继续遵循原许可证。其附加引用链接来自该修订版,尚未在此独立核查。