[comp.software-eng] How do you conduct Post-mortem reviews of software projects ?

sbhide@mentor.com (Sandhi Bhide) (10/19/89)

Hi Netters: 

I am working as a software process manager here at Mentor Graphics Corp.
and I am interested in finding out as to how you conduct post-mortems ?

I am NOT interested in the product post-mortems, but more process-mortems.
I would like to have a checklist, or a set of questions that can be used
to find out what changes could be made to the process of making software.
I believe that the key to better software quality lies in the quality of
development process that produces that software.  With that view, is there
anybody out there who performs those post-mortems at the end of each 
project and says to the troops: Hey, what can we do different next time
or improve upon in the process, so that we will get better quality
products next time ......  What specific things can we do to the process
to improve it ....

Can you mail me such a checklist ?  I am interested not only in the
contents (which questions to ask), but also the process of conducting,
recording the post-mortem reviews for future use and improvement (How
should those questions be asked to get the right answers).  Should they
be performed in the presence of the management or not(may affect their
review ??)  Should names be involved in this ?? (I mean the psychology
part of it too).   

I am planning to include this as a formal milestone in our product life
cycle process and I am calling it a "Learning Milestone" and that is
my motivation for this posting.

Bottom Line: I am interested in whole 9 yards of post-mortem that is 
process focused.               

Please let me know over the emaill or call me at (503) 626-7000 x2561
or write/send me some stuff at: Sandhi Bhide, Mentor Graphics Corp.,
8500 SW Creekside Place, Beaverton, OR 97005-7191.

Thx/Rgds: Sandhi