基于构件的敏捷软件开发方法

软件在规模、复杂度、功能上的极大扩展和提高,以及在需求和技术上不断变化的过程中实现快速软件开发的要求,使得众多现有的软件开发方法不能很好地满足实际的开发需要,该文有效地结合了基于构件的软件开发和敏捷开发方法,提出了软件开发的一种新方法一基于构件的敏捷软件开发方法,并成功地进行了实践。     

敏捷需求建模的研究与设计

文章综合研究了敏捷方法与极限编程开发过程,结合需求工程方法,设计提出了基于敏捷思想的敏捷需求建模（Agile Requiremenb Modeling。简称ARM）。敏捷需求建模作为各种敏捷方法在软件需求中的实践补充,能够满足CMMI的目标。可以为中小型软件开发组织的行动指南提供参考。     

基于敏捷化统一过程需求建模的研究及实践

敏捷建模(AM)是适应需求变化、提高软件开发效率的新型建模思想,而RUP是Rational公司提出的一个通用的软件开发过程框架。本文分析了当前RUP实践的缺点及敏捷建模实践特点,在此基础上总结了敏捷化统一过程(AM-RUP),并提出了一种AM-RUP的需求建模过程——“总体概要需求获取,按需求优先级进行计划,小增量迭代式简单需求建模”。以社会保险系统的开发为背景,探索了基于AM-RUP的需求建模过程及技术。     

试议软件敏捷项目中的需求开发

软件产品开发中,需求管理是决定成败的前提和关键。在敏捷开发模型中,传统软件开发过程中的需求开发和管理实践,会因为不能很好适应快速交付等敏捷原则,反而会对开发过程造成困惑和障碍。根据实际项目操作经验,参考敏捷开发模型,提出需求开发的迭代开发方法。     

极限编程在进销存管理系统开发中的应用

极限编程是敏捷方法中最著名的一种基于实践的软件开发方法.通过介绍极限编程的特点以及在进销存管理系统项目开发中的实践,探讨研究了极限编程对于需求易变的小型信息管理软件开发项目应用的优势.     

极限编程在职工培训管理信息系统开发中的应用

极限编程是敏捷方法中最著名的一种基于实践的软件开发方法。通过介绍极限编程的特点以及在职工培训管理信息系统项目开发中的实践．探讨研究极限编程对于需求易变的小型信息管理软件开发项目的优势。     

敏捷方法在软件项目开发中的实践

目前很多企业内中小型软件项目面临开发时间紧迫、人手不足、需求不断变化的困难,传统重量级的软件开发方法无法应对这样的挑战.敏捷方法是基于实践的软件开发方法学,为解决这类轻量级项目管理和开发所碰到的问题提供了新的思路.通过分析敏捷方法的主要目标、观点和原则,并结合一个实际的管理信息系统项目开发,从项目计划、项目文档、重构的改进和项目维护的4个方面探讨了敏捷方法的实践应用.实践证明,采用敏捷方法的观点和原则进行必要的改进,能取得项目开发的成功.     

基于敏捷思想的iOS平台软件的设计与实现

软件的开发过程与最初的计划保持一致已经不再是当今软件开发的主要目标了,如何应对客户对于需求的不断变化,快速地交付高质量的软件并做到让客户满意,已经成为了一个软件开发公司能否在当今竞争激烈的软件行业中得以生存的关键。文中在对统一软件过程以及敏捷方法的优势和局限性研究与分析的基础上,利用敏捷思想对统一过程进行适当裁剪并利用统一思想对敏捷开发进行合理扩充,提出了一种基于统一过程和敏捷方法的软件开发过程,成功地将敏捷过程应用到iOS智能手机操作系统开发这一实际的项目中。实践证明,敏捷开发方法在应对需求频繁变化和提高软件开发效率方面均起到了很好的效果。     

敏捷型软件开发方法与极限编程概述

在当前需求快速变动的背景下，传统的软件工程方法显得难以适应。近年来出现了一类新的轻量级的软件开发方法，它们被统称为敏捷型软件开发方法。介绍了敏捷型软件开发方法的背景、原则和特点，将其与传统软件工程方法作了比较；还重点介绍了当前国外流行的敏捷型软件开发方法：XP(eXtreme Programming——极限编程)的开发流程和实践准则。     

敏捷方法在企业应用系统开发中的应用与改进

面对传统方法在适应需求变化方面的不足，近年来出现了一些敏捷型软件开发方法，它灵活的开发机制能有效控制需求变化带来的风险。本文以极限编程为例介绍了敏捷方法的思想、价值观和过程实践规则。另外，本文还分析了企业应用系统开发的特点和难点，并结合ERP项目开发的实践经验，介绍了敏捷方法在企业应用系统开发中的应用和改进过程。     

软件开发生命周期法比较之敏捷与传统

敏捷开发是近十年来兴起的软件开发模式,2012年11月第七届中国敏捷软件开发大会在北京、深圳、上海三地举办,为国内外敏捷实践者提供了开放的交流平台。从软件开发生命周期的角度分析比较了敏捷方法与传统方法的优劣,并提出敏捷方法在实践中的改进建议。     

Using metrics in Agile and Lean Software Development – A systematic literature review of industrial studies

ContextSoftware industry has widely adopted Agile software development methods. Agile literature proposes a few key metrics but little is known of the actual metrics use in Agile teams.ObjectiveThe objective of this paper is to increase knowledge of the reasons for and effects of using metrics in industrial Agile development. We focus on the metrics that Agile teams use, rather than the ones used from outside by software engineering researchers. In addition, we analyse the influence of the used metrics.MethodThis paper presents a systematic literature review (SLR) on using metrics in industrial Agile software development. We identified 774 papers, which we reduced to 30 primary studies through our paper selection process.ResultsThe results indicate that the reasons for and the effects of using metrics are focused on the following areas: sprint planning, progress tracking, software quality measurement, fixing software process problems, and motivating people. Additionally, we show that although Agile teams use many metrics suggested in the Agile literature, they also use many custom metrics. Finally, the most influential metrics in the primary studies are Velocity and Effort estimate.ConclusionThe use of metrics in Agile software development is similar to Traditional software development. Projects and sprints need to be planned and tracked. Quality needs to be measured. Problems in the process need to be identified and fixed. Future work should focus on metrics that had high importance but low prevalence in our study, as they can offer the largest impact to the software industry.     

A framework to support the evaluation, adoption and improvement of agile methods in practice

Agile methods are often seen as providing ways to avoid overheads typically perceived as being imposed by traditional software development environments. However, few organizations are psychologically or technically able to take on an agile approach rapidly and effectively. Here, we describe a number of approaches to assist in such a transition. The Agile Software Solution Framework (ASSF) provides an overall context for the exploration of agile methods, knowledge and governance and contains an Agile Toolkit for quantifying part of the agile process. These link to the business aspects of software development so that the business value and agile process are well aligned. Finally, we describe how these theories are applied in practice with two industry case studies using the Agile Adoption and Improvement Model (AAIM).     

The impact of inadequate customer collaboration on self-organizing Agile teams

Context

Customer collaboration is a vital feature of Agile software development.

Objective

This article addresses the importance of adequate customer involvement on Agile projects, and the impact of different levels of customer involvement on real-life Agile projects.

Method

We conducted a Grounded Theory study involving 30 Agile practitioners from 16 software development organizations in New Zealand and India, over a period of 3 years.

Results

We discovered that Lack of Customer Involvement was one of the biggest challenges faced by Agile teams. Customers were not as involved on these Agile projects as Agile methods demand. We describe the causes of inadequate customer collaboration, its adverse consequences on self-organizing Agile teams, and Agile Undercover — a set of strategies used by the teams to practice Agile despite insufficient or ineffective customer involvement.

Conclusion

Customer involvement is important on Agile projects. Inadequate customer involvement causes adverse problems for Agile teams. The Agile Undercover strategies we’ve identified can assist Agile teams facing similar lack of customer involvement.     

Extreme programming. Rapid development for Web-based applications

Agile processes like extreme programming (XP), Scrum, Crystal, and adaptive software development aim to increase a software organization's responsiveness while decreasing development overhead. They focus on delivering executable code and see people as the strongest ingredient of software development. We offer an overview of the philosophy and practice behind XP, which is currently the most popular agile methodology     

Agile MERODE: a model-driven software engineering method for user-centric and value-based development

Agile is often associated with a lack of architectural thinking causing technical debt but has the advantage of user centricity and a strong focus on value. Model-driven software engineering (MDSE) strongly performs for building a quality architecture and code, but lacks focus on user requirements and tends to consider development as a monolithic whole. The combination of Agile and MDSE has been explored, but a convincing integrated method has not been proposed yet. This paper addresses this gap by exploring the specific combination of MERODE—as an example of a proven MDSE method—with Scrum, a reference agile method offering a concrete (sprint-based) life cycle management on the basis of user stories. The method resulting of this integration is called Agile MERODE; it is driven by user stories, themselves associated with behavior-driven development scenarios. It allows for domain-driven design and permits fast development from domain models by means of code generation. An illustrative example further clarifies the practical application of Agile MERODE, while a case study shows the planning game application in the case’s context. While the approach, in its entirety, allows reducing technical debt by building the architecture in a logical, consistent and complete manner, introducing MDSE involves a trade-off with pure value-driven development. Agile MERODE contributes to the state of the art by showing how to increase user centricity in MDSE, how to align model-driven engineering with the Scrum cycle, and how to reduce the technical debt of agile developments yet remaining value-focused.

     

Agile transition and adoption human-related challenges and issues: A Grounded Theory approach

Agile methods in software development have been introduced to cope with the inherent problems of the traditional methods. The increasing prevalence of using these methods reflects their important role in the future of software development. However, leaving traditional approach and adapting to Agile approach has been a central attention of the researchers. Indeed, Agile transition needs enough time and effort and most often is subject to several challenges and barriers, mainly because of its people-centric nature. Human-related challenges in several studies have been reported as the major transition challenges. However, exploring the primary origins and reasons of these challenges has received less effort in a large-scale research study. A Grounded Theory in context of Agile software development has been conducted involving 49 Agile practitioners across the 13 different countries. This study identified different aspects of human-related challenges throughout Agile transition process. The results of this study show that the root of the emerged issues is the people's perceptions about Agile transition. The main purpose of this paper is to describe the origins and reasons of these challenges and issues in order to help software companies and development teams. Considering the findings may help them to facilitate Agile transition process with less cost, time and effort and to get better results by considering these potential challenges.     

基于在线检测技术的敏捷软件开发方法的模型

针对敏捷软件开发方法尚未从本质上消除控制滞后性的问题,运用发酵调控学领域的在线检测技术和反馈控制技术,设定三个控制目标函数,设置若干检测参数及控制参数,建立基于在线检测技术以及反馈控制技术的敏捷软件开发方法的模型,研究控制变量、可测变量与控制目标变量三者之间的关系,从而解决控制滞后问题,实现敏捷软件过程的优化。     

Investigating the applicability of Agility assessment surveys: A case study

ContextAgile software development has become popular in the past decade without being sufficiently defined. The Agile principles can be instantiated differently which creates different perceptions of Agility. This has resulted in several frameworks being presented in the research literature to evaluate the level of Agility. However, the evidence of their actual use in practice is limited.ObjectiveThe objective is to identify online surveys that assess/profile Agility in practice, and to evaluate the surveys in an industrial setting.MethodThe Agility assessment surveys were identified through searching the web. Then, they were explored and two surveys were identified as most promising for our objective. The selected surveys were evaluated in a case study with three Agile teams in a software consultancy company.ResultsEach team and its customer separately judged the team's Agility. This outcome was compared with the two survey results in focus-group meetings, and finally one of the surveys was agreed to provide a more holistic assessment of Agility.ConclusionsDifferent surveys may judge Agility differently, which supports the viewpoint that Agile is not well defined. Therefore, practitioners must decide what Agile means to them and select the assessment survey that matches their definition.     

敏捷软件开发中的风险管理

敏捷软件开发的诞生源于对高失败率的传统软件开发方法的改进和探索,是一种处理软件开发过程中各个级别上风险的软件开发方法。但是敏捷软件开发很少明确地看到风险管理的内容,经常缺乏对风险的关注。本文根据敏捷软件开发的特点和项目风险管理理论,从人、过程、产品和技术四个纬度就如何防范和缓解敏捷软件开发风险进行了探析。