mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Dec 17th, 2009

 

From a software testing standpoint, a post-mortem meeting is a good place to reexamine. In the meeting, care should be taken to reexamine:

    * Testing estimates versus actual execution in many metric areas such as number of test cases executed, functional areas tested, and platforms tested, etc.
    * Estimated test schedule time versus the actual or realized test schedule.
    * Requirements stability to see how many requirement changes were made, when in the process they occurred, and what impact these changes had on the test effort?
    * Metrics about what priority level bugs were found in what phases. Were you finding too many high priority bugs too late? Why?

This reexamination process can help to identify both things that are working well, as well as problem areas.