Process Overview
Plan a Project Review
Gather Project Data
Hold a Project
History Day
Analyze the Findings
Lessons Learned
Create a Plan
for Change
Close the Loop

Postmortem Toolkit
Planning Tools
Data Gathering Tools
Tools for Anaylis
Tools for Synthesis
Plan of Action
Closing the Loop
IEEE Postmortem Article Resources & References New User Tour Products and Services About Us Join

Collect Objective and Subjective Data

The information you choose to collect should be specific to your project and should reveal underlying symptoms in your development process, such as, resource costs, boundary conditions, schedule predictability, defect counts, etc. Look for information that will reveal where the problems lay. For example, if the project suffered from scarce resources you might present the number of resources on the project, both planned and actual, by month. Suffering feature creep? Make a list of each time the features were revisited and list the changes made.

Examples of Objective Data
  • Event Timeline
  • Schedule Predictability
  • Number of times the feature set was defined and when it happened
  • Boundary conditions, planned and actual
  • Resources over time, planned and actual
  • 'Bugs' found over time compared to fixed over time
  • Number of changes to the software
  • Hours spent in meetings
  • Build dates, predicted and actual
  • Subjective scales
  • Configurations/ platforms supported

Tools for Gathering Data
What is it? What is it?
Steps Steps
Tips and Tricks Tips and
Event Timeline Survey
Schedule Predictability Debriefing Meeting