...
首页> 外文期刊>Information and software technology >Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering
【24h】

Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering

机译:你咬的东西比你咀嚼的还多吗?大型软件工程中超范围的因果关系案例研究

获取原文
获取原文并翻译 | 示例
           

摘要

Context: Scope management is a core part of software release management and often a key factor in releasing successful software products to the market. In a market-driven case, when only a few requirements are known a priori, the risk of overscoping may increase. Objective: This paper reports on findings from a case study aimed at understanding overscoping in large-scale, market-driven software development projects, and how agile requirements engineering practices may affect this situation. Method: Based on a hypothesis of which factors that may be involved in an overscoping situation, semi-structured interviews were performed with nine practitioners at a large, market-driven software company. The results from the interviews were validated by six (other) practitioners at the case company via a questionnaire. Results: The results provide a detailed picture of overscoping as a phenomenon including a number of causes, root causes and effects, and indicate that overscoping is mainly caused by operating in a fast-moving market-driven domain and how this ever-changing inflow of requirements is managed. Weak awareness of overall goals, in combination with low development involvement in early phases, may contribute to 'biting off more than a project can 'chew'. Furthermore, overscoping may lead to a number of potentially serious and expensive consequences, including quality issues, delays and failure to meet customer expectations. Finally, the study indicates that overscoping occurs also when applying agile requirements engineering practices, though the overload is more manageable and perceived to result in less wasted effort when applying a continuous scope prioritization, in combination with gradual requirements detailing and a close cooperation within cross-functional teams. Conclusion: The results provide an increased understanding of scoping as a complex and continuous activity, including an analysis of the causes, effects, and a discussion on possible impact of agile requirements engineering practices to the issue of overscoping. The results presented in this paper can be used to identify potential factors to address in order to achieve a more realistic project scope.
机译:背景:范围管理是软件发布管理的核心部分,并且通常是将成功的软件产品发布到市场的关键因素。在以市场为导向的情况下,如果先验条件只有很少的要求,则划定范围的风险可能会增加。目标:本文报告了一个案例研究的结果,该案例旨在了解大规模的,市场驱动的软件开发项目中的过分界定,以及敏捷需求工程实践如何影响这种情况。方法:基于一个假设,即哪些因素可能与超范围情况有关,在一家大型,市场驱动的软件公司中,对九名从业人员进行了半结构化访谈。访谈的结果由案例公司的六名(其他)执业者通过问卷调查进行了验证。结果:结果提供了对超额划定现象的详细描述,这种现象包括许多原因,根本原因和结果,并表明超额划定主要是由于在快速发展的市场驱动领域中运作以及这种不断变化的资金流入造成的。需求得到管理。对总体目标的意识不足,再加上早期阶段的低开发投入,可能会导致“咬掉比项目可以“咀嚼”的更多东西”。此外,划界可能导致许多潜在的严重和昂贵后果,包括质量问题,延误和未能满足客户期望。最后,该研究表明,在应用敏捷需求工程实践时,也会出现超范围划分,尽管重载更易于管理,并且在应用连续范围优先级时结合渐进的需求详细说明和跨部门内部的紧密合作,可以减少浪费的工作量。职能团队。结论:结果使人们对范围界定作为一个复杂而连续的活动有了更多的了解,包括对原因,结果的分析,以及对敏捷需求工程实践对范围界定的可能影响的讨论。本文提出的结果可用于确定潜在的因素,以实现更现实的项目范围。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号