[论文解读] Comparative Study on Agile software development methodologies

A B M Moniruzzaman, Syed Akhter Hossain|arXiv (Cornell University)|Jul 12, 2013

Software Engineering Techniques and Practices参考文献 45被引用 69

一句话总结

本文对敏捷软件开发方法（ASDM）与传统软件开发方法（TSDM）进行了比较分析，突出展示了敏捷方法在动态商业环境中通过迭代、协作和以客户为中心的方式提升软件交付效率的优势。研究识别出诸多关键优势，如更快的交付速度、对需求变更的适应能力以及团队生产力的提升，最终得出结论：对于现代软件开发面临的挑战，敏捷方法优于计划驱动型方法。

ABSTRACT

Today-s business environment is very much dynamic, and organisations are constantly changing their software requirements to adjust with new environment. They also demand for fast delivery of software products as well as for accepting changing requirements. In this aspect, traditional plan-driven developments fail to meet up these requirements. Though traditional software development methodologies, such as life cycle-based structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It is a set of software development methods based on iterative and incremental development process, where requirements and development evolve through collaboration between self-organizing, cross-functional teams that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements. In this paper, we significantly identify and describe the major factors, that Agile development approach improves software development process to meet the rapid changing business environments. We also provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss current state of adopting agile methodologies. We speculate that from the need to satisfy the customer through early and continuous delivery of the valuable software, Agile software development is emerged as an alternative to traditional plan-based software development methods. The purpose of this paper, is to provide an in-depth understanding, the major benefits of agile development approach to software development industry, as well as provide a comparison study report of ASDM over TSDM.

研究动机与目标

• 探讨传统、计划驱动型软件开发方法在应对快速变化的业务需求时的局限性。
• 识别并分析使敏捷方法在快速且适应性地交付高质量软件方面更有效的核心因素。
• 从流程、协作和成果等方面，对敏捷软件开发方法（ASDM）与传统软件开发方法（TSDM）进行全面比较。
• 评估敏捷方法在软件行业中的当前采纳状况与实际实施情况。
• 提供关于敏捷实践如何通过早期和持续交付有价值软件来提升客户满意度的见解。

提出的方法

• 开展对敏捷与传统软件开发方法的比较文献综述，重点关注流程模型、团队结构和开发周期。
• 分析敏捷核心原则，如迭代开发、跨职能的自组织团队以及持续的干系人协作。
• 利用行业实践中的案例研究和实证证据，说明敏捷在动态环境中的优势。
• 评估敏捷实践对软件质量、交付速度和需求适应能力的影响。
• 对主要敏捷方法（如Scrum、XP、Kanban）进行分类与描述，并与传统模型（如Waterfall和RUP）进行对比。
• 将研究发现整合为一份结构化比较报告，突出ASDM与TSDM在流程、团队动态和成果方面的差异。

实验结果

研究问题

• RQ1 与传统方法相比，敏捷软件开发方法在应对不断变化的业务需求方面有何改进？
• RQ2 在软件开发中，哪些关键的流程和组织因素促成了敏捷方法的成功？
• RQ3 敏捷方法在哪些方面支持早期和持续交付有价值软件，这种做法如何影响客户满意度？
• RQ4 在团队结构、规划和交付周期方面，敏捷与传统软件开发的主要差异是什么？
• RQ5 当前软件开发行业中敏捷方法采纳的主要趋势与挑战是什么？

主要发现

• 敏捷方法在快速交付软件并适应需求变化方面，显著优于传统计划驱动型方法。
• 敏捷方法的迭代和增量特性能够实现早期和持续交付可运行的软件，从而提升客户满意度。
• 敏捷环境中跨职能的自组织团队相比层级化、阶段式管理模型，展现出更高的生产力和响应能力。
• 通过持续集成、测试和反馈循环，敏捷开发可缩短上市时间并提高软件质量。
• 本研究证实，敏捷方法更适合于需求频繁演变的动态商业环境。
• 尽管具有诸多优势，本文也指出，敏捷方法的采纳仍面临组织文化、培训以及在大型企业中可扩展性等方面的挑战。