正在翻頁。
正在呈現下一章……
此閱讀內容目前僅有英語版。界面使用你選擇的語言。
閱讀英語原文 →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。 章節和格式經過精簡;連結中的修訂版提供完整背景與貢獻歷史。此參考文本繼續遵循原許可證。其附加引用連結來自該修訂版,尚未在此獨立核查。