【24h】

Does every inspection need a meeting?

机译:每次检查都需要开会吗?

获取原文

摘要

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.
机译:在大型软件开发的每个步骤中,审阅者都会进行检查以发现故障。在进行这些检查之后,通常会召开会议以收集已发现的故障。但是,我们发现这些检查会议没有经理和开发人员认为的那样有益。更糟糕的是,它们在产品开发间隔和开发人员时间方面的成本比任何人都意识到的要高。对检查和收集过程的分析使我们提出以下建议。首先,至少应最小化每次检查会议所需的参与者数量。其次,我们提出了两种可供选择的故障收集方法,两种方法都可以完全消除检查会议:(a)通过沉积收集故障(由两人或三人组成的小型面对面会议),或(b)使用口头收集故障或书面媒体(电话,电子邮件或便笺)。我们相信,这种程序更改将通过减少生产时间而不牺牲产品质量来提高效率。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号