Conducted Progress Postmortems: Continuous Improvement During Project Life Cycle

PMBOK v8 Definition

An in-progress postmortem is a structured process conducted at various stages of the project life cycle to analyze current performance, identify issues, and implement improvements. Unlike traditional postmortems held at the end of a project, these reviews are conducted periodically to ensure continuous improvement and timely problem-solving. This concept belongs to the Executing and Monitoring and Controlling performance domains.

Why It Matters for the Exam

The PMI exam frequently tests the distinction between in-progress postmortems and traditional end-of-project retrospectives, as this reflects modern agile and adaptive project management approaches. Questions often appear in scenario-based items where a project manager needs to decide when to conduct performance reviews or how to implement continuous improvement during the project life cycle.

Key Points to Remember (for the exam)

• Primary Purpose: Analyze current performance, identify issues, and implement improvements during the project life cycle (not after project completion)
• Timing: Conducted at various stages/periodically throughout the project, not only at the end
• Key Difference from Traditional Postmortems: Traditional postmortems occur at project end; in-progress postmortems occur continuously during execution
• Main Output: Actionable improvements and timely problem-solving for current project phases
• Key Tool: Information radiator (Figure 5-9) to visualize findings and promote awareness
• Common Confusion: Do not confuse in-progress postmortems with inspections—inspections examine work product conformance to standards; postmortems analyze overall performance and processes
• Relationship to Retrospectives: In-progress postmortems align with iteration retrospectives but are broader, covering the entire project life cycle

Typical PMI Exam Example

A project manager is halfway through a 12-month software development project. The team has noticed recurring delays in testing phases. The project manager decides to conduct a structured review of current performance to identify root causes and implement corrective actions immediately. This is an example of an in-progress postmortem.

PMI Exam Traps

• Trap: Confusing in-progress postmortems with end-of-project retrospectives

• Reality: In-progress postmortems occur during the project; retrospectives can occur at iteration/release end or project close

• Trap: Believing postmortems only happen at project closure

• Reality: PMBOK v8 explicitly describes in-progress postmortems conducted at various stages for continuous improvement

• Trap: Mixing up inspections with in-progress postmortems

• Reality: Inspections examine work product conformance to documented standards; postmortems analyze performance and processes

• Trap: Thinking in-progress postmortems are only for agile projects

• Reality: PMBOK v8 describes them as applicable across the project life cycle, regardless of methodology

Important PMI Connections

Quick Review Questions

1. What is the primary difference between an in-progress postmortem and a traditional postmortem?

2. During which performance domain(s) would a project manager typically conduct an in-progress postmortem?

3. A project team is examining a completed deliverable to verify it meets documented standards. Is this an in-progress postmortem or an inspection?

4. What tool, referenced in Figure 5-9, helps visualize in-progress postmortem findings?

5. How do in-progress postmortems support continuous improvement during the project life cycle?

PMBOK v8 Reference

Section 5.2.2 - Information Radiator (Figure 5-9) Section 2.1 - Performance Domain Processes (Table 2-1) Section 2.1.6 - Close Project or Phase (knowledge transfer and retrospectives)