• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>British HCI Group Annual Conference >Brainstorming Under Constraints: Why Software Developers Brainstorm in Groups
【24h】

Brainstorming Under Constraints: Why Software Developers Brainstorm in Groups

机译：在约束下头脑风暴：为什么软件开发人员在群体中进行头脑风暴

获取原文
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

Group brainstorming is widely adopted as a design method in the domain of software development. However, existing brainstorming literature has consistently proven group brainstorming to be ineffective under the controlled laboratory settings. Yet, electronic brainstorming systems informed by the results of these prior laboratory studies have failed to gain adoption in the field because of the lack of support for group well-being and member support. Therefore, there is a need to better understand brainstorming in the field. In this work, we seek to understand why and how brainstorming is actually practiced, rather than how brainstorming practices deviate from formal brainstorming rules, by observing brainstorming meetings at Microsoft. The results of this work show that, contrary to the conventional brainstorming practices, software teams at Microsoft engage heavily in the constraint discovery process in their brainstorming meetings. We identified two types of constraints that occur in brainstorming meetings. Functional constraints are requirements and criteria that define the idea space, whereas practical constraints are limitations that prioritize the proposed solutions.
机译：集团头脑风暴被广泛采用作为软件开发领域的设计方法。然而，现有的头脑风暴文献一直在受控实验室环境下始终如一地证明群体头脑风暴无效。然而，由于这些先前实验室研究的结果而告知这些现有实验室研究的结果未能在该领域采用，因为缺乏对集团福祉和成员支持的支持。因此，需要更好地理解在该领域的头脑风暴。在这项工作中，我们寻求理解为什么实际上实践头脑风暴，而不是如何通过观察微软的头脑风暴会议来偏离正式的头脑风暴规则的头脑风暴的惯例。这项工作的结果表明，与传统的头脑风暴实践相反，微软的软件团队在其头脑风暴会议中大量参与约束发现过程。我们确定了在头脑风暴会议中发生的两种限制。功能约束是定义思想空间的要求和标准，而实际限制是优先考虑所提出的解决方案的限制。

著录项

相似文献

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

客服邮箱：kefu@zhangqiaokeyan.com

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

  • 客服微信

  • 服务号