DocumentCode
1007283
Title
Post-mortems-methodology and experiences
Author
Tiedeman, Mark J.
Author_Institution
AT&T Bell Lab., Naperville, IL, USA
Volume
8
Issue
2
fYear
1990
fDate
2/1/1990 12:00:00 AM
Firstpage
176
Lastpage
180
Abstract
A methodology for preparing and conducting post-mortems for software development projects is presented. Based on the continuous process improvement concept, post-mortems are systematic reviews of a product´s quality and the quality of the associated processes that produce it. The intent is to learn both what worked well and what could be improved. Three types of postmortem have evolved, each focusing on particular aspects of the software development process. The planning postmortem covers requirements specification and work program definition. The design verification postmortem includes design, unit test, system verification, and first office application activities. The field post-mortem focuses on actual field experience. The post-mortem methodology has been in use for several years and has been found to be a very effective organizational learning tool and source for many software quality improvement ideas. Specific examples of what has been and can be learned are included. The evolution of the post-mortem is discussed, along with possible metrics for evaluating the effectiveness of postmortems
Keywords
quality control; software reliability; continuous process improvement concept; design verification; field experience; planning; post-mortems; processes quality; product quality; requirements specification; software development projects; software quality improvement; system verification; unit test; work program definition; Application software; Electrical capacitance tomography; Electronic switching systems; Feedback; Programming; Software quality; Spine; Switches; Switching systems; System testing;
fLanguage
English
Journal_Title
Selected Areas in Communications, IEEE Journal on
Publisher
ieee
ISSN
0733-8716
Type
jour
DOI
10.1109/49.46869
Filename
46869
Link To Document