What is the primary purpose of a post-mortem after milestones?

• A. To celebrate success and archive results without changes.
• B. To assign blame for failures.
• C. To delay future work and reduce scope.
• D. To analyze performance, identify improvements, and capture insights for future work.

Answer: (D)

The main idea here is learning and improvement. After milestones, a post-mortem is a reflective process where the team looks at what happened, why it happened, and how to do better next time. The goal is to analyze performance against plan, identify what went well and what didn’t, and capture concrete insights and action items that guide future work. This helps refine processes, tools, and collaboration, and makes upcoming milestones more predictable and efficient. It’s important for the reflection to be focused on systems and workflows rather than individuals, so problems are addressed at the process level and improvements are actually implemented with clear owners and deadlines. While sharing successes can be part of the discussion, the central aim is to capture knowledge that informs planning, estimates, testing, risk management, and coordination for future efforts.