Membuka halaman berikutnya.
Menampilkan bab berikutnya…
Psst… sesuaikan cara membaca Anda.
Font dan tema ada di Tampilan. Mata Anda juga berhak memilih.
Menampilkan bab berikutnya…
A public write-up of what failed after an incident. Quality varies. Demand one.
Memeriksa dukungan baca nyaring pada peramban ini…
Bacaan ini saat ini tersedia dalam bahasa Inggris. Antarmuka menggunakan bahasa pilihan Anda.
Baca teks asli bahasa Inggris →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 dari Postmortem documentation, oleh para kontributornya, dengan lisensi CC BY-SA 4.0. Revisi 1314822468. Bagian dan format telah diringkas; revisi tertaut menyediakan konteks lengkap dan riwayat kontributor. Teks referensi ini tetap menggunakan lisensi yang sama. Tautan kutipan tambahannya diimpor dari revisi tersebut dan belum diperiksa secara independen di sini.