PulseExploreJournal ClubDebatesTrendingResearchersJournals
Instagram
HomeExploreJournal ClubTrending
Synapse
⌘+K
Synapse
December 1, 1993ACM SIGSOFT Software Engineering Notes237 citationsOpen Access

Does every inspection need a meeting?

LVLawrence G. Votta

Key Points

Key points are not available for this paper at this time.

Abstract

At each step in large software development, reviewers carry out inspections to detect faults. These inspections are usually followed by a meeting to collect the faults that have been discovered. However, we have found that these inspection meetings are not as beneficial as managers and developers think they are. Even worse, they cost much more in terms of products development interval and developer's time than anyone realizes.Analysis of the inspection and collection process leads us to make the following suggestions. First, at the least, the number of participants required at each inspection meeting should be minimized. Second, we propose two alternative fault collection methods, either of which would eliminate the inspection meetings altogether: (a) collect faults by deposition (small face-to-face meetings of two or three persons), or (b) collect faults using verbal or written media (telephone, electronic mail, or notes).We believe that such a change in procedure would increase efficiency by reducing production times without sacrificing product quality.

Ask AI
Helpful
Bookmark
Share
View Full Paper

Cite This Study

Lawrence G. Votta (1993) studied this question.

synapsesocial.com/papers/6a19d6ade7f8932c5eeac403https://doi.org/10.1145/167049.167070
Ask AI
Helpful
Bookmark
Share
View Full Paper