We Value Your Privacy

We use technology such as cookies on our website, and through our partners, to personalize content and ads, provide social media features, and analyse our traffic. To find out more, read our privacy policy and Cookie Policy. Please also see our Terms and Conditions of Use. By accepting these terms you agree to your information being processed by Inbox Insight, its Partners or future partners, that you are over 18, and may receive relevant communications through this website, phone, email and digital marketing. For more information on how we process your data, or to opt out, please read our privacy policy. Our policies and partners are subject to change so please check back regularly to stay up to date with our terms of use and processing.

Accept Terms Settings
x

Please Sign-In to Access this Report

To access other reports on the platform please sign in with your username and password, or register for a free account to get unlimited access and insight customized for you.

Report PagerDuty The Post-Mortem Handbook

The Post-Mortem Handbook

Lessons 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

Related Content