What is a post-mortem analysis?

What is a post-mortem analysis?

A post-mortem analysis is a process in which you summarize what went wrong (and should be fixed) in a project, as well as what went well and should be repeated.

How do you structure a post-mortem?

How to Conduct a Post-Mortem Meeting

1. Schedule the post-mortem when you start the project.
2. Set a meeting time-limit.
3. Compile a guest list.
4. Assign a notetaker.
5. Start the meeting with an introduction.
6. Create a timeline of milestones.
7. Start listing action items.
8. Explore the issues.

What are the key areas to review or include to ensure a successful post-mortem meeting?

9 Tips for Getting the Most Out of Post-Mortem Meetings

• What is a post-mortem meeting?
• Run a post-mortem for every project.
• Share an agenda before the meeting.
• Prepare by circulating a questionnaire.
• Include your clients in the post-mortem.
• Start by focusing on what went well.
• Don’t play the blame game.

Why is it called post-mortem?

The term post-mortem literally means “after death.” In medicine, the term is used to describe an examination of a dead body in order to discover the cause of death.

What is the difference between postmortem and posthumous?

In other words: postmortem = after one’s own death; posthumous = after the death of someone else.

What should be included in a post mortem analysis?

The analysis also produces action items and who is responsible for each. The data being analyzed during the post-mortem will include inputs from a number of sources, including feedback from the project team and an evaluation of the project’s results.

Why is post mortem important in risk management?

The post-mortem is also a key part of risk management. A company can lower or mitigate risk in future projects by analyzing what went wrong in past projects and making changes to processes and procedures. There are two main situations where post-mortem meetings occur. The first (as mentioned above) is project related.

What does post mortem mean in agile project management?

In a small survey of project managers, 100 percent of the respondents said they had led post-mortem meetings after their projects: In Agile project management, the term retrospective is used to refer to a similar activity, which occurs after each software development iteration. Here’s how the two differ:

When to have a post mortem meeting for a project?

Your team will learn that these meetings are all about improvement; they’re not only for when things go wrong. To streamline this process so it actually becomes part of every project, you’ll need to get in the habit of holding post-mortem meetings shortly after your project’s end.