Membuka halaman seterusnya.
Memaparkan bab seterusnya…
Psst… sesuaikan cara membaca Anda.
Fon dan tema tersedia di Tampilan. Keselesaan mata anda juga penting.
Memaparkan bab seterusnya…
A public write-up of what failed after an incident. Quality varies. Demand one.
Menyemak sokongan bacaan suara pada pelayar ini…
Bacaan ini kini tersedia dalam bahasa Inggeris. Antara muka menggunakan bahasa pilihan anda.
Baca teks asal bahasa Inggeris →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.
Dipilih dan diformat ulang daripada Postmortem documentation, oleh para kontributornya, dengan lesen CC BY-SA 4.0. Semakan 1314822468. Bahagian dan format telah diringkas; semakan berpaut menyediakan konteks lengkap dan sejarah penyumbang. Teks rujukan ini tetap menggunakan lesen yang sama. Pautan rujukan tambahannya diimport daripada semakan tersebut dan belum disemak secara bebas di sini.