• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>Agile processes in software engineering and extreme programming >Stress in Agile Software Development: Practices and Outcomes
【24h】

Stress in Agile Software Development: Practices and Outcomes

机译：敏捷软件开发中的压力：实践和结果

获取原文
获取原文并翻译 | 示例
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

Stress is an important workplace issue, affecting both the health of individuals, and the health of organizations. Early advocacy for Agile Software Development suggested it might help avoid stress, with practices that emphasize a sustainable pace, and self-organizing teams. Our analysis of a 2014 survey, however, suggested that stress might still be commonplace in Agile teams, especially for those with less experience. We also noticed that newcomers to Agile emphasized technical, rather than collaborative, practices, and speculated this might explain the stress. We explored this in our analysis of a follow-up survey conducted in 2016, and report our findings in this paper. We show that there are a variety of factors involved, and that avoiding stress is associated with both collaborative and technical practices, and a range of outcomes.
机译：压力是一个重要的工作场所问题，既影响个人的健康，也影响组织的健康。敏捷软件开发的早期倡导者认为，这可能有助于避免压力，强调可持续步伐的实践和自组团队。然而，我们对2014年调查的分析表明，在敏捷团队中压力仍然很常见，尤其是对于经验不足的团队。我们还注意到，敏捷新手强调技术实践而非协作实践，并推测这可能解释了压力。我们在对2016年进行的后续调查的分析中对此进行了探索，并在本文中报告了我们的发现。我们表明涉及多种因素，而避免压力与协作和技术实践以及一系列结果相关。

著录项

相似文献

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

客服邮箱：kefu@zhangqiaokeyan.com

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

  • 客服微信

  • 服务号