The Post-Mortem HandbookLessons learned from the trenches and how you can conduct better post-mortems
No major incident is ever truly resolved without a post-mortem. Post-Mortems are a great way for development teams to identify and analyse elements of a project that were successful or unsuccessful. It’s a way to look back and review the incident in detail to determine exactly what went wrong, why it went wrong, and what can be done in the future to make sure it doesn’t happen again. This handbook provides lessons learned from the trenches to help you conduct better post-mortems (including a post-mortem template)
Report Snap Shot
A post-mortem can also be referred to as an after-action review, incident review, or follow-up review. While the name may be different, the process and goal is the same.
- Why are post-mortem's necessary?
- How to conduct a post-mortem