| Process Overview |
| Plan a Project Review |
| Gather Project Data |
| Hold a Project History Day |
| Analyze the Findings |
| Synthesize 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 Checklist |
|
|
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
Tools for Gathering Data |
|
|||||||||
|
||||||||||
